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 (import/export) " in "Service Platform Reference Guide".

(a) Import method

2 types of the import method are as follows:

Standard import

Generally use standard import. Import HCSC components of another repository in the HCSC server configuration information of the current operating environment. The HCSC components existing prior to the import operation are destroyed.

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".

(b) 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

Only the changed HCSC components are to be expanded in the repository of an operating environment. The HCSC components, which are not changed, are not expanded in the repository of an operating environment. The HCSC components of the current repository of the operating environment remain as are.

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.

(c) Restrictions on import

You cannot import the repository information in any one of the following cases:

1. If the HCSC server is not set up (in case of standard import)
2. If the HCSC server configuration is different in the current repository information of the operating environment and the repository information to be imported
3. If the currently deployed business process or the service adapter is deleted in the repository information to be imported
4. If information of the currently deployed business process or the service adapter is updated in the repository information to be imported
5. 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^#
6. 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 TableSettings 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.

When importing a repository, auto-backup of the repository information prior to import is to be performed in ZIP file format. The backup file is output to the following directory with cscimport.zip as the file name.

<Installation directory of Service Platform>\CSC\spool\manager

You can change the output destination directory of the backup file using cscmng.envbackup.dir parameter or cscmng.envbackup.dir.import parameter of HCSC-Manager definition file.

Moreover, you can set the option of whether to perform auto-backup using cscmng.envbackup.autoget parameter or cscmng.envbackup.autoget.off parameter of HCSC-Manager definition file.

For details on HCSC-Manager definition file, see "HCSC-Manager definition file" in "Service Platform Reference Guide".

For details on how to restore an operating environment from the backup file, see "7.9.3(2) Restoring the operating environment".

If you import repository information whose version is newer than the current repository information, the version of the repository is automatically upgraded at the time of import.

If the business process or the service adapter, which is currently deployed, is deleted in the repository information to be imported, an error occurs in the import operation at the time of version upgrade. If an error occurs, export the current repository from the operating environment and import it in the development environment. After that, export the repository whose version is upgraded in the development environment from the development environment and import it in the operating environment.

For details on version upgrade, see "Appendix G. Migration from an Old Version".