uCosminexus Service Platform, Basic Development Guide
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)
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.
Details of the 2 methods of importing are as follows:
Procedure for importing service definition and system configuration definition in the repository is as follows:
Table 3-1 Error conditions in consistency check performed while importing a repository (in case of importing only service definition 1)
No. | Error conditions |
---|---|
1 | Service IDs do not match |
2 | Service names do not match#1 |
3 | Types (service adapter or business process) do not match#1 |
4 | Versions of business process do not match#1#2 |
5 | Number of user-defined receptions defined in business process do not match#1 |
6 | IDs of user-defined reception defined in the business process do not match#1 |
7 | Names of the user-defined reception defined in business process do not match#1 |
8 | Packaging of service definition in ZIP file is not performed#1#2 |
Table 3-2 Error conditions in consistency check performed while importing a repository (in case of importing only system configuration definition 2)
No. | Information in repository | Error conditions (service definition in ZIP file for which service IDs match) |
||
---|---|---|---|---|
Server configuration defined in system configuration definition | Publicized service definition (types of service) | |||
Usage of database | Usage of Reliable Messaging | |||
1 | Used | Not used | All | -- |
2 | Not used | Not used | Business process | yes is set in persistence of status |
3 |
|
MDB_WSR or MDB_DBQ has been set in types of service | ||
4 | Used | Not used |
|
MDB_WSR or MDB_DBQ has been set in types of service |
Table 3-3 Error conditions in consistency check performed while importing a repository (in case of importing only the system configuration definition 1)
No. | Error conditions |
---|---|
1 | Service IDs do not match |
2 | Service names do not match#1 |
3 | Types (service adapter or business process) do not match#1 |
4 | Versions of business process do not match#1#2 |
5 | Number of user-defined receptions defined in business process do not match#1 |
6 | ID of user-defined reception defined in business process do not match#1 |
7 | Names of user-defined receptions defined in business process do not match#1 |
8 | Packaging is not performed of service definition in ZIP file#1#2 |
Table 3-4 Error conditions in consistency check performed while importing a repository (in case of importing only system configuration definition 2)
No. | Information in ZIP file | Error condition (service definition in ZIP file for which service IDs match) |
||
---|---|---|---|---|
Server configuration defined in system configuration definition | Publicized service definition (type of service) | |||
Usage of database | Usage of Reliable Messaging | |||
1 | Used | Used | All | -- |
2 | Not used | Not used | Business process | yes is set in persistency of status |
3 |
|
MDB_WSR or MDB_DBQ has been set in types of service | ||
4 | Used | Not used |
|
MDB_WSR or MDB_DBQ has been set in types of service |
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.
Procedure for importing only a part of service definition is as follows:
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.