Relationship between Test Environment and Production Environment

On the Service Platform, you first configure a test environment, and then test and debug. You can use the HCSC Easy Setup functionality for configuring the test environment.

When developing a real system, you must configure a production environment other than the test environment. For this reason, you must move the repository used in the test environment to the production environment.

The following are the three cases to move the repository used in the test environment to the production environment:

Case 1: When configuring with the same settings of the database and Reliable Messaging, in the test environment and production environment

Case 2: When configuring with the different settings of the database and Reliable Messaging, in the test environment and in the production environment, the repository used in the test environment can be moved to the production environment as it is^#

Case 3: When you re-create a repository of the production environment from the repository used in the test environment because the environments are configured with the different settings of the database and Reliable Messaging in the test environment and production environment^#

Note:: For details about whether the repository used in the test environment can be moved to the production environment as it is, see 4.3 Importing a repository.

The following table describes the settings used for databases and Reliable Messaging corresponding to the above cases. For details about configuration types depending on the usage of databases and Reliable Messaging, see 2.2 Selecting configuration types and SOAP modes.

Table 1-2 Cases corresponding to the settings used for a database and Reliable Messaging

Test environment settings	Production environment settings
Test environment settings	Both database and Reliable Messaging are used	Database is used and Reliable Messaging is not used	Both database and Reliable Messaging is not used
Both database and Reliable Messaging are used	Case 1^#	Case 3	Case 3
Database is used and Reliable Messaging is not used	Case 2	Case 1^#	Case 3
Both database and Reliable Messaging is not used	Case 2	Case 2^#	Case 1^#

#: Setting to which a user corresponds with the settings of the test environment and the production environment.

An overview of migration in each case is as follows:

Organization of this section: (1) Case 1: When configuring with the same settings of the database and Reliable Messaging, in the test environment and the production environment; (2) Case 2: When configuring with different settings of the database and Reliable Messaging, in the test environment and the production environment (When repository can be moved as it is); (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)

(1) Case 1: When configuring with the same settings of the database and Reliable Messaging, in the test environment and the production environment

When configuring with the same settings of the database and Reliable Messaging in the following test environment and production environments, the repository used in the test environment can be migrated to the production environment as it is:

When both database and Reliable Messaging are used in the test environment and in the production environment
When both database and Reliable Messaging are not used in the test environment and in the production environment
When database is used and Reliable Messaging is not used in the test environment and in the production environment

The following figure shows the procedure of migration when configuring with same settings of the database and Reliable Messaging, in the test environment and production environments:

Figure 1-6 Procedure of migration when configuring with the same settings of the database and Reliable Messaging

[Figure]

For details about specific procedures for migrating, see "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".

(2) Case 2: When configuring with different settings of the database and Reliable Messaging, in the test environment and the production environment (When repository can be moved as it is)

Even 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 can be moved to the production environment as it is in the following cases:

When both database and Reliable Messaging are not used in the test environment, but used in the production environment
When both database and Reliable Messaging are not 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 used in the production environment

The following figure shows the procedure of migration when the repository used in the test environment can be migrated to the production environment as it is when you configure with different settings of the database and Reliable Messaging, in the test environment and in the production environment:

Figure 1-7 Procedure of migration when configuring with the different settings of the database and Reliable Messaging (When repository can be migrated as it is)

[Figure]

For details about specific procedures for moving, see 3.4.3 Procedure of migration from an environment where both database and Reliable Messaging are not used to an environment where both are used and 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.

(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 1-8 Procedure of migration when configuring with the different settings of the database and Reliable Messaging (When re-creating a repository)

[Figure]

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

1.3 Relationship between Test Environment and Production Environment

(1) Case 1: When configuring with the same settings of the database and Reliable Messaging, in the test environment and the production environment

(2) Case 2: When configuring with different settings of the database and Reliable Messaging, in the test environment and the production environment (When repository can be moved as it is)

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