uCosminexus Service Platform, Basic Development Guide

[Contents][Glossary][Index][Back][Next]

3.2.3 Importing a Repository

In importing the repository, you can read the repository which was consolidated to ZIP file during export. You can import the definition information such as service definition and system configuration definition saved in the repository. You can import a repository, when SOAP mode of the exported repository match with SOAP mode of the import destination repository.

Following are the 2 methods to import a repository.

Following figure shows the example of different usages of the 2 methods of importing.

Figure 3-1 Different usages of the 2 methods of importing (example)

[Figure]

As shown in the example in the above figure, when developing HCSC components concurrently in multiple development environments, export the repositories of respective development environments and import in the master repository. At that time, import only the information required in the service definition. Also, when importing the information of a repository exported in operation environment, to the repository (master) of development environment, import service definition and system configuration definition.

You can also receive the exported information through network, without using media.

Note
When importing repository, close all the editors such as service adapter definition or business process definition. Also, set such that lib directory or src directory of HCSCTE project is not accessed. If error occurs, check the following points.
  • Whether the editor (including external editor) in which file under src directory of HCSCTE project is opened, is closed
  • Whether program in which library under lib directory of HCSCTE project is used, is executed

Details of the 2 methods of importing are as follows:

Organization of this subsection
(1) Importing the service definition and the system configuration definition
(2) Importing only a part of the service definitions

(1) Importing the service definition and the system configuration definition

(a) Procedure of importing

Procedure for importing service definition and system configuration definition in the repository is as follows:

  1. From the Eclipse menu, select [HCSC-Definer]-[Definition information management]-[Import entire definition information].
    Dialog for confirming the importing is displayed.
  2. Click [Yes] button.
    Dialog [Import repository] for selecting the ZIP file of repository information is displayed.
  3. Specify ZIP file to be read.
  4. Click [Open] button.
    Dialog [Import repository] for selecting the definition information to be imported is displayed.

    [Figure]

  5. Insert check mark in the check box of definition to be imported.
    When importing for the first time, insert check mark in [Service definition] and [System configuration definition] both.
  6. Click [OK] button.
    Repository is read in the directory specified in "3.2.1(1) Specifying a repository".
(b) Notes

(2) Importing only a part of the service definitions

When importing only a part of service definitions, you can select following information as import target:

You can select multiple sets of information for importing. Service adapters and business processes invoked from business processes that are selected for importing are imported simultaneously as needed. User-defined reception related to the business process to be imported is also imported simultaneously.

While importing, you can specify any service ID or reception ID to import the service and user-defined reception.

(a) Procedure for importing

Procedure for importing only a part of service definition is as follows:

  1. From the Eclipse menu, select [HCSC-Definer]-[Definition information management]-[Import service].
    Dialog for selecting archive file (ZIP file) is displayed.
  2. Select the archive file that includes the information to be imported and click [Open] button.
    [Import service] dialog (service selection) is displayed.

    [Figure]

  3. Check the checkbox of the service to be imported.
  4. Change the [Post-incorporation ID] of the service to be imported, as and when required.
    Specify ID by taking note of the following points:
    • Specify with 8 or less alphanumeric characters and underscore (_).
    • You cannot specify an ID that is already used in import destination.
      However, even if it is ID used in import destination, if that ID is no longer used depending on the concurrently imported services, you can specify that ID.
    • You cannot specify ID same as other services or user-defined reception.
    • When integrating services distributed and developed across multiple repositories, interface inconsistency occurs till all the services are imported and warming message might be displayed in Remarks column. If inconsistency occurring till service integration is anticipated, there is no problem even if warning message is displayed in Remarks column.
      However, when inconsistency occurs in interfaces, correct design information is not output and hence do not output the design information.
  5. Click the [OK] button.
    Existence of user-defined Java class is checked.
    When user-defined Java class exists, [Import service] dialog (selection of user-defined Java class) is displayed. Proceed with the following steps:
    When user-defined Java class does not exist, contents of the selected repository are read in the directory specified in "3.2.1(1) Specifying a repository".
  6. Check the checkbox of user-defined Java class to be imported and its pre-requisite library files.

    [Figure]

  7. Click the [OK] button.
    Existence of user-defined class is checked.
    When user-defined Java class exists, [Import service] dialog (selection of user-defined Java class) is displayed.
    Contents of selected repository are read in the directory specified in "3.2.1(1) Specifying a repository".
    Hint
    • If you cannot select an import target such as in case where HCSC component of same name is publicized in the repository, the display of service in [Import service] dialog (service selection) becomes inactive. Eliminate the cause with reference to contents in [Remarks] column and import again.
    • Always perform packaging of the imported HCSC component (service adapter, business process). For details on the method of packaging, see "7.2 Packaging".
    • When you import user-defined Java class or pre-requisite library of user-defined java class to be used in Java calling activity, build HCSCTE project.
(b) Notes