3.4.4 Procedure of migration from an environment where both database and Reliable Messaging are used to an environment where database is used and Reliable Messaging is not used
The following figure shows the migration procedure when both database and Reliable Messaging are used in the test environment, and database is used and Reliable Messaging is not used in the production environment. For an overview of migration, see "1.3.3 Case 3: When configuring with the different settings of the database and Reliable Messaging, in the test environment and in the production environment (When re-creating a repository)".
|
|
![[Figure]](GRAPHICS/ZC030800.GIF)
-
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. When setting up the HCSC server by using the HCSC Easy Setup functionality, select the model with DB/RM. When the execution log is not used, you can also select the model without DB/RM. For the migration procedure when the model without DB/RM is selected, see "3.4.5 Procedure of migration from an environment where both database and Reliable Messaging are not used to an environment where database is used and Reliable Messaging is not used".
-
Export the repository from the operating environment, and import the system configuration definition, specified in the test environment, into the development environment.
-
Create the HCSC components in the development environment.
-
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).
At this time, the system configuration definition that forms the base of the deployment definition specifies settings for using both database and Reliable Messaging.
-
Export the repository containing the deployment definition, specified in the development environment, and import the repository into the operating environment.
-
Based on the deployment definition specified in the development environment, deploy the HCSC components into the test environment.
-
Set up the HCSC server in the production environment, and define the system configuration.
In the HCSC server setup definition file, specify "ON" for the db-use property and "OFF" for the rm-use property.
Also, specify the same SOAP mode in the test environment and production environment.
-
Import the system configuration definition and service definition specified in the test environment into the development environment.
-
Export the repository from the operating environment of the production environment, and import the system configuration definition specified in the production environment into the development environment.
-
Based on the system configuration definition specified in the production environment, define and update where to deploy the system configuration definition in the system configuration (deployment definition).
At this time, the system configuration definition that forms the base of the deployment definition specifies settings for using the database and not using Reliable Messaging.
Note that an error occurs if a deployment definition is specified for the asynchronous receptions, asynchronous service adapters, and persistent business processes.
-
Export the repository containing the deployment definition, specified in the development environment, and import the repository into the operating environment.
For the test environment repository (repository imported in 8.), migrate the repository (repository imported in 9.) in which the system configuration definition for the production environment is specified, into the production environment.
-
Based on the deployment definition specified in the development environment, deploy the HCSC components into the production environment.
The HCSC components are deployed in the production environment with a configuration for using the database and not using Reliable Messaging.