4.3.1 Import method
Enter the following command:
cscrepctl -user <Login-user ID> -pass <Login password> -import <File name>
When importing a repository, you must first confirm that any directory or file present in the directory, which is set in the repository, is not being referenced. Then execute the cscrepctl command.
For details on the cscrepctl command, see "cscrepctl (Importing/Exporting)" in "Service Platform Reference Guide".
- Organization of this subsection
(1) Import method
2 types of the import method are as follows:
- Standard import
-
In general, use the standard import method. This method imports the repository information compressed in ZIP format into the HCSC server configuration information in the current operating environment. The repository information existing before the import will be discarded.
If you want to check whether the configuration information of the HCSC server is same in the repository information of the current operating environment and the repository information to be imported, specify -check option in the cscrepctl command.
- Component import
-
Use this type of import method when you want to add HCSC components of the specified repository ZIP file to the repository of an operating environment. The HCSC components existing prior to the import operation remain. To perform component import, specify the -compo option in the cscrepctl command.
For details on the component import, see "4.6 Adding, updating, and deleting a repository using component as a unit".
(2) Method of expanding the repository information
From the following 2 expansion methods, you can select the contents to be expanded in a repository within the repository information saved in ZIP file format:
- Difference expansion
-
The information about the HCSC components that have been added or changed is expanded from the import-target ZIP file and imported into the repository in the operating environment. The existing information about the HCSC components that have not been changed remains as is in the repository in the operating environment.
- Whole expansion
-
All the ZIP files to be imported including the HCSC components, which are not changed, are to be extracted in the repository of an operating environment. To perform overall expansion, specify the-overwrite option in the cscrepctl command.
(3) Restrictions on import
You cannot import the repository information in any one of the following cases:
-
If the HCSC server is not set up (in case of standard import)
-
If the HCSC server configuration is different in the current repository information of the operating environment and the repository information to be imported
-
If the currently deployed business process or the service adapter is deleted in the repository information to be imported
-
If information of the currently deployed business process or the service adapter is updated in the repository information to be imported
-
If setting related to the option of whether to use database and Reliable Messaging is different in the current repository information of the operating environment and the repository information to be imported#
-
If SOAP mode of the current repository information of the operating environment and that of the repository information to be imported are different
For 3. and 4, import the repository after deleting the corresponding business process or the service adapter from the execution environment.
- Note#
-
Even if setting related to the option of whether to use database and Reliable Messaging is different in the current repository information of the operating environment and the repository information to be imported, you can perform the import operation for some cases. The following table describes the settings to be performed when import is possible and when import is not possible:
Table 4‒2: Settings to be performed when import is possible and when import is not possible Settings to be performed in the repository information to be imported
Settings to be performed in the current repository information of the operating environment
Use database as well as Reliable Messaging
Use database and do not use Reliable Messaging
Do not use database as well as Reliable Messaging
Use database as well as Reliable Messaging
Y
N
N
Use database and do not use Reliable Messaging
Y
Y
N
Do not use database as well as Reliable Messaging
Y
Y
Y
- Legend:
-
Y: Can be imported.
N: Cannot be imported.