H.6 Procedure for replicating a virtual machine after setup of JP1/AJS3 - Manager (on the replicated VM)
If you replicate a virtual machine after setting up JP1/AJS3 - Manager, the replication procedure varies depending on whether you change the IP address or host name after replication. If you change the IP address or host name, the procedure also varies depending on which item you change. The following subsections describe the procedure to be performed on the replicated virtual machine in each case:
- Organization of this subsection
(1) When changing neither the IP address nor the host name
This subsection describes the procedure for replicating a virtual machine (after setting up JP1/AJS3 - Manager) that must be performed on the replicated virtual machine when neither the IP address nor the host name is to be changed.
-
Perform the tasks that are required in JP1/Base after the virtual machine is replicated by performing disk copy installation.
For the tasks that must be performed in JP1/Base during disk copy installation, see the Release Notes for JP1/Base.
-
To use the manager connection permission configuration file, edit it based on the replication-destination environment.
For details about the manager connection permission configuration file, see 2.3.8 Restricting access to JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
-
To connect to the replicated virtual machine from JP1/AJS3 - Web Operation Assistant, in a text editor, open the system configuration file for the embedded database, and then specify the replication-destination host name.
The location of the system configuration file for the embedded database is given below.
- In Windows:
-
embedded-database-practical-directory\conf\pdsys
- In UNIX:
-
embedded-database-practical-directory/conf/pdsys
An example of editing the file is given below.
- Before the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1
- After the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1,destination_host_name
-
Enable automatic startup of the JP1/Base and JP1/AJS3 services again based on the operational requirements.
For details about how to enable automatic startup of the JP1/Base service, see the Job Management Partner 1/Base User's Guide.
For details about how to enable automatic startup of the JP1/AJS3 service, see 4.2.4 Settings for starting and stopping JP1/AJS3 services automatically in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
(2) When changing the IP address only
-
Perform the tasks required in JP1/Base when the IP address is changed.
For details about the tasks required in JP1/Base when the IP address is changed, see the Job Management Partner 1/Base User's Guide.
-
Perform the tasks that are required in JP1/Base after the virtual machine is replicated by performing disk copy installation.
For the tasks that must be performed in JP1/Base during disk copy installation, see the Release Notes for JP1/Base.
-
To use the manager connection permission configuration file, edit it based on the replication-destination environment.
For details about the manager connection permission configuration file, see 2.3.8 Restricting access to JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
-
To connect to the replicated virtual machine from JP1/AJS3 - Web Operation Assistant, in a text editor, open the system configuration file for the embedded database, and then specify the replication-destination host name.
The location of the system configuration file for the embedded database is given below.
- In Windows:
-
embedded-database-practical-directory\conf\pdsys
- In UNIX:
-
embedded-database-practical-directory/conf/pdsys
An example of editing the file is given below.
- Before the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1
- After the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1,destination_host_name
-
Enable automatic startup of the JP1/Base and JP1/AJS3 services again based on the operational requirements.
For details about how to enable automatic startup of the JP1/Base service, see the Job Management Partner 1/Base User's Guide.
For details about how to enable automatic startup of the JP1/AJS3 service, see 4.2.4 Settings for starting and stopping JP1/AJS3 services automatically in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
(3) When changing the host name only
This subsection describes the procedure for replicating a virtual machine (after setting up JP1/AJS3 - Manager) that must be performed on the replicated virtual machine when only the host name is to be changed.
-
Perform the tasks required in JP1/Base when the host name is changed.
For details about the tasks required in JP1/Base when the host name is changed, see the Job Management Partner 1/Base User's Guide.
-
Perform the tasks that are required in JP1/Base after the virtual machine is replicated by performing disk copy installation.
For the tasks that must be performed in JP1/Base during disk copy installation, see the Release Notes for JP1/Base.
-
To use the manager connection permission configuration file, edit it based on the replication-destination environment.
For details about the manager connection permission configuration file, see 2.3.8 Restricting access to JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
-
Restore the execution environment for queue jobs and submit jobs.
You can skip this step if the system is in the standard configuration (without ISAM).
On the replication-destination host, delete the execution environment for queue jobs and submit jobs, and then use the command jpqimport to re-create the execution environments. After executing the command jpqimport, make sure the return value is 0 (normal termination).
For details about the command jpqimport, see jpqimport in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
-
To connect to the replicated virtual machine from JP1/AJS3 - Web Operation Assistant, in a text editor, open the system configuration file for the embedded database, and then specify the replication-destination host name.
The location of the system configuration file for the embedded database is given below.
- In Windows:
-
embedded-database-practical-directory\conf\pdsys
- In UNIX:
-
embedded-database-practical-directory/conf/pdsys
An example of editing the file is given below.
- Before the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1
- After the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1,destination_host_name
-
Enable automatic startup of the JP1/Base and JP1/AJS3 services again based on the operational requirements.
For details about how to enable automatic startup of the JP1/Base service, see the Job Management Partner 1/Base User's Guide.
For details about how to enable automatic startup of the JP1/AJS3 service, see 4.2.4 Settings for starting and stopping JP1/AJS3 services automatically in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
(4) When changing both the IP address and the host name
This subsection describes the procedure for replicating a virtual machine (after setting up JP1/AJS3 - Manager) that must be performed on the replicated virtual machine when both the IP address and host name are to be changed.
-
Perform the tasks required in JP1/Base when the IP address is changed.
For details about the tasks required in JP1/Base when the IP address is changed, see the Job Management Partner 1/Base User's Guide.
-
Perform the tasks required in JP1/Base when the host name is changed.
For details about the tasks required in JP1/Base when the host name is changed, see the Job Management Partner 1/Base User's Guide.
-
Perform the tasks that are required in JP1/Base after the virtual machine is replicated by performing disk copy installation.
For the tasks that must be performed in JP1/Base during disk copy installation, see the Release Notes for JP1/Base.
-
To use the manager connection permission configuration file, edit it based on the replication-destination environment.
For details about the manager connection permission configuration file, see 2.3.8 Restricting access to JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
-
Restore the execution environment for queue jobs and submit jobs.
You can skip this step if the system is in the standard configuration (without ISAM).
On the replication-destination host, delete the execution environment for queue jobs and submit jobs, and then use the command jpqimport to re-create the execution environments. After executing the command jpqimport, make sure the return value is 0 (normal termination).
For details about the command jpqimport, see jpqimport in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
-
To connect to the replicated virtual machine from JP1/AJS3 - Web Operation Assistant, in a text editor, open the system configuration file for the embedded database, and then specify the replication-destination host name.
The location of the system configuration file for the embedded database is given below.
- In Windows:
-
embedded-database-practical-directory\conf\pdsys
- In UNIX:
-
embedded-database-practical-directory/conf/pdsys
An example of editing the file is given below.
- Before the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1
- After the change:
-
pdstart -t SDS -s ajs2 -u unt1 -m 127.0.0.1,destination_host_name
-
Enable automatic startup of the JP1/Base and JP1/AJS3 services again based on the operational requirements.
For details about how to enable automatic startup of the JP1/Base service, see the Job Management Partner 1/Base User's Guide.
For details about how to enable automatic startup of the JP1/AJS3 service, see 4.2.4 Settings for starting and stopping JP1/AJS3 services automatically in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.