3.4.1 Procedure of migration when the existence of usage of the database and Reliable Messaging in the test and production environments is the same

The following figure shows the migration procedure when the existence of usage of the database and Reliable Messaging in the test environment and production environment are the same. For an overview of migration, see "1.3.1 Case 1: When configuring with the same settings of the database and Reliable Messaging, in the test environment and the production environment".

Figure 3‒9: Procedure of migration (When the existence of usage of database and Reliable Messaging is the same in the test environment and production environment)

1. Set up the HCSC server in the test environment, and define the system configuration.

   You can set up the HCSC server and define the system configuration by using the HCSC Easy Setup functionality.

2. Export the repository from the operating environment, and import the system configuration definition, specified in the test environment, into the development environment.

3. Create the HCSC components in the development environment.

4. Based on the system configuration definition specified in the test environment, define and update where to deploy the HCSC components in the system configuration (deployment definition).

5. Export the repository containing the deployment definition, specified in the development environment, and import the repository into the operating environment.

6. Based on the deployment definition specified in the development environment, deploy the HCSC components into the test environment.

7. Set up the HCSC server in the production environment, and define the system configuration.

   Specify the same settings for the existence of usage of the database and Reliable Messaging in the test environment and production environment.

   Also, specify the same SOAP mode in the test environment and production environment.

8. Export the repository containing the deployment definition, specified in the development environment, and import the repository into the operating environment.

   If standard import is used, you can migrate the test environment repository into the production environment as is, even if the HCSC server name or IP address are different.

9. Based on the deployment definition specified in the development environment, deploy the HCSC components into the production environment.

To Page Top