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)
When configuring with the different settings of the database and Reliable Messaging, in the test environment and the production environment, the repository used in the test environment cannot be migrated to the production environment as it is in the following cases:
-
When both database and Reliable Messaging are used in the test environment and not in the production environment
-
When both database and Reliable Messaging are used in the test environment, and when database is used and Reliable Messaging is not used in the production environment
-
When database is used and Reliable Messaging is not used in the test environment, and both database and Reliable Messaging are not used in the production environment
In this case, reset the system configuration definition set in the test environment to the system configuration definition used in the production environment, and then create a repository.
The following figure shows the procedure of migration when re-creating a repository used in the production environment from the repository of the test environment when configuring with different settings of the database and Reliable Messaging, in the test environment and in the production environment:
|
|
![[Figure]](GRAPHICS/ZC010096.GIF)
For details about specific procedures for migrating, see "3.4.2 Procedure of migration from an environment where both database and Reliable Messaging are used to an environment where both are not used" and "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".