7.9.1 Changing the name of the host that runs JP1/AJS3

This subsection explains the procedures for changing the names of hosts that run JP1/AJS3 (JP1/AJS3 - Manager, JP1/AJS3 - Agent, and JP1/AJS3 - Web Console).

Organization of this subsection

(1) Notes on changing the host name
(2) Procedure for changing the host name of JP1/AJS3 - Manager
(3) Procedure for changing the host name of JP1/AJS3 - Agent
(4) Procedure for changing the host name of JP1/AJS3 - Web Console

(1) Notes on changing the host name

There is no effect on operation of JP1/AJS3 even if the old host name is used in a message before it is changed. Pay special attention, however, if user programs reference log files.
After the host name is changed, if you display the detailed results of a job executed before the host name is changed, the old host name is displayed as the name of the host where the job was executed. This does not affect the operation of JP1/AJS3.
If you change only a domain name of the network environment without defining the host name in the FQDN format within JP1/AJS3, operation (for changing the host name) described in this subsection is not required. If the name of the Access Control Server of JP1/Base is specified in the FQDN format, you must change the user mapping setting according as described in Step 9 of (2) Procedure for changing the host name of JP1/AJS3 - Manager below.
If you change the host name when QUEUE jobs and submit jobs are used, you need to change the execution agent definition information and the definition information for the execution environment for QUEUE jobs and submit jobs.

To Page Top

(2) Procedure for changing the host name of JP1/AJS3 - Manager

Before you change the host name of JP1/AJS3 - Manager, you need to do the following:

Preparation

When you use a remote jobnet, before changing the host name, cancel the execution registration of the remote jobnet.
When you execute the event job, stop all programs of JP1/AJS3 of the agent host that executes the event job.
If the operation restriction function of the Web GUI is enabled, prepare a backup of the operating permission configuration file that has been applied on the JP1/AJS3 - Manager host whose name is to be changed.

To change the host name of JP1/AJS3 - Manager:

Log off JP1/AJS3 - View.
Use the ajsprint command to back up the jobnet definition.

You will use the backup you create here in step 11.

For details about the backup method, see 2.2.3(4) Backing up the unit definition.
Use the ajsagtprint command to back up the execution agent definition.

The backup created here will be used in step 12. For details about how to create the backup, see 2.2.3(2) Backing up the execution agent information.
If the following services are running on the manager host, stop them:
- JP1/AJS3 services on the physical host and all logical hosts on the manager host
- JP1/AJS3 Queueless Agent service
- JP1/AJS3 Queueless File Transfer service
- JP1/AJS3 Check Agent service
- JP1/AJS3 Check Manager service
When QUEUE jobs and submit jobs are used, use the jpqexport command to back up the execution environment definition for QUEUE jobs and submit jobs.

The backup created here will be used in step 7. For details about how to create the backup, see 2.2.3(3) Backing up the execution environment definition for QUEUE jobs and submit jobs.
Change the physical host name of the manager host, or the logical host name.

Change the host name of the manager host. Change the host name if the host is a physical host.

If you are running JP1/AJS3 in a cluster system, and you change a logical host name, delete the old logical host name and then set up the new logical host name for use in the cluster system.

In Windows:

For details about deleting logical host names, see 8.2.8 Deleting logical hosts in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about setting up a logical host to run in a cluster system, see 8. Setup for Operation in a Cluster System in the JP1/Automatic Job Management System 3 Configuration Guide.

In UNIX:

For details about deleting logical host names, see 17.2.8 Deleting logical hosts in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about setting up a logical host to run in a cluster system, see 17. Setup for Operation in a Cluster System in the JP1/Automatic Job Management System 3 Configuration Guide.
When QUEUE jobs and submit jobs are used, use the jpqimport command to re-create the execution environment for the QUEUE jobs and submit jobs.

For details about how to re-create the execution environment for the QUEUE jobs and submit jobs, see 2.3.4(6) Creating an execution environment for QUEUE jobs and submit jobs.

For a logical host, this step is unnecessary because the execution environment has already been re-created in step 6.
Set up the database environment.

If you change the name of the physical host, you will need to reconfigure the database environment of all embedded databases that are set up on the physical and logical hosts. For details about the procedure for performing setup again, see steps 3 to 7 in 23.4.1(6) Setting up an embedded database again in the JP1/Automatic Job Management System 3 Configuration Guide.

If you want to use a cluster configuration, set up the primary node and then, on the secondary node, perform the procedure in 23.5.2(6) Setting up an embedded database again in the JP1/Automatic Job Management System 3 Configuration Guide. In addition, this operation is unnecessary for a logical host because re-setup was already performed in step 6.

Perform the following procedure as required.

No.	Condition	Work performed
1	If the host whose name is to be changed is used as the authorization server (a function of JP1/Base)	Change the settings for user mapping. In Windows: In the JP1/Base Environment Settings dialog box, choose the User Mapping tab, and then change the host name defined in Server host of JP1 user to the changed name. In UNIX: Change the host name defined in the user mapping definition file (`jp1BsUmap.conf`) to the changed name. Then execute the `jbsmkumap` command. For details on user mapping, see the JP1/Base User's Guide.
2	If an event job is being used	On the manager and agent hosts (including the local host) is being used on which the event job is being executed, execute the `jpoagoec` command, and then cold-start the JP1/AJS3 services on the agent hosts. Execute the `jpoagoec` command on all the hosts that receive requests from the manager whose name is to be changed and that execute the event job. The procedure for executing the command is described below. An example procedure for when hostname `ManagerHostB` is to be changed to follows: Execute the `jpoagoec -p` command to check the name of the manager host that the event action agent function currently stores. Display example: `ManagerHostA` `ManagerHostB` Execute the `jpoagoec -d` `ManagerHostB` command to delete the pre-changed manager host name. Cold-start the JP1/AJS3 services on the agent hosts. Use the following procedure to perform a cold start: In Windows: In the Control Panel, double-click Administrative Tools. In the displayed Administrative Tool dialog box, double-click the Services icon. Select the service name of JP1/AJS3 to be started, and then select Operations and Properties. In the General tab in the `service-name` Properties dialog box, specify `-cold` as the start mode for Start Parameters. Then click the Start button. In UNIX: Execute the `jajs_spmd -cold [-h` `logical-host-name`] command.
3	If the communication encryption function is being used and you change the host name to one different from the CN or SAN in the server certificate	Acquire and deploy the server certificate again. To change the host name to one different from the CN or SAN in the server certificate, you need to acquire and deploy the server certificate again. If the CA of the issuer of the reacquired server certificate is different from that of the original certificate, you also need to acquire and deploy the root certificate. For details about how to acquire and deploy server certificates and root certificates, see 21.4 Setting up the communication using SSL in the JP1/Automatic Job Management System 3 Configuration Guide.

No.

Condition

Work performed

If the host whose name is to be changed is used as the authorization server (a function of JP1/Base)

Change the settings for user mapping.

In Windows:: In the JP1/Base Environment Settings dialog box, choose the User Mapping tab, and then change the host name defined in Server host of JP1 user to the changed name.
In UNIX:: Change the host name defined in the user mapping definition file (jp1BsUmap.conf) to the changed name. Then execute the jbsmkumap command.

For details on user mapping, see the JP1/Base User's Guide.

If an event job is being used

On the manager and agent hosts (including the local host) is being used on which the event job is being executed, execute the jpoagoec command, and then cold-start the JP1/AJS3 services on the agent hosts.

Execute the jpoagoec command on all the hosts that receive requests from the manager whose name is to be changed and that execute the event job. The procedure for executing the command is described below. An example procedure for when hostname ManagerHostB is to be changed to follows:

Execute the jpoagoec -p command to check the name of the manager host that the event action agent function currently stores.

Display example:

ManagerHostA

ManagerHostB
Execute the jpoagoec -d ManagerHostB command to delete the pre-changed manager host name.
Cold-start the JP1/AJS3 services on the agent hosts.

Use the following procedure to perform a cold start:

In Windows:

In the Control Panel, double-click Administrative Tools.

In the displayed Administrative Tool dialog box, double-click the Services icon.

Select the service name of JP1/AJS3 to be started, and then select Operations and Properties.

In the General tab in the service-name Properties dialog box, specify -cold as the start mode for Start Parameters.

Then click the Start button.

In UNIX:

Execute the jajs_spmd -cold [-h logical-host-name] command.

If the communication encryption function is being used and you change the host name to one different from the CN or SAN in the server certificate

Acquire and deploy the server certificate again.

To change the host name to one different from the CN or SAN in the server certificate, you need to acquire and deploy the server certificate again. If the CA of the issuer of the reacquired server certificate is different from that of the original certificate, you also need to acquire and deploy the root certificate.

For details about how to acquire and deploy server certificates and root certificates, see 21.4 Setting up the communication using SSL in the JP1/Automatic Job Management System 3 Configuration Guide.

Cold-start the JP1/AJS3 service on the manager host.

Perform a cold start of the physical host or logical host whose host name you changed.
Use the ajsdefine command to recover the jobnet definition you backed up in step 2.

For details about the recovery method, see 2.3.4(9) Recovering the unit definition.
Use the ajsagtadd command to recover the execution agent definition you backed up in step 3.

For details about the recovery method, see 2.3.4(8) Recovering the execution agent information.
If necessary, start the services you stopped in step 4.
On the manager host, re-register for execution the jobnets required for operation.

Since the manager host is started by a cold start in step 10, the execution registration of jobnets is all cancelled. Execute and register again the jobnets required for operation.

Perform the following procedure as required.

No.	Condition	Work performed
1	If JP1/AJS3 - Web Console is used	Change the name of the connection-destination manager host in the environment settings file (`ajs3web.conf`) for JP1/AJS3 - Web Console, and then restart the JP1/AJS3 Web Application Server service. For details about the environment settings file (`ajs3web.conf`) in Windows, see 3.4.3 Details on the settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For details about the environment settings file (`ajs3web.conf`) in Linux, see 13.3.3 Details on settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.
2	If JP1/AJS3 - Web Console is used, and JP1/AJS3 - Web Console is installed on the manager host	Specify the new host name in the HTTP server definition file (`httpsd.conf`), and then restart the JP1/AJS3 HTTP Server service. For details about the HTTP server definition file (`httpsd.conf`) in Windows, see 3.4.5 Details on the settings in the HTTP server definition file (httpsd.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For details about the HTTP server definition file (`httpsd.conf`) in UNIX, see 13.3.5 Details on settings in the HTTP server definition file (httpsd.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.
3	If JP1/AJS3 - Web Console is used, and the units on the manager host whose names are to be changed are set as monitoring targets in the Dashboard window of the Web GUI	Log in by using the new host name. Then, set the monitoring targets again. If you specify, at login, the IP address of the manager host for Host to connect, you do not need to set the monitoring targets again.
4	If you use JP1/AJS3 - Web Console installed on a manager host and linkage with JP1/IM is set up	Change the host name specified for the Web Console server that is called from JP1/IM. For details on setting up linkage with JP1/IM, see 10.2 Setup for linking JP1/IM in the JP1/Automatic Job Management System 3 Linkage Guide.
5	If JP1/AJS3 - Web Console is used and the operation restriction function of the Web GUI is enabled	Log in to the Web GUI by specifying a new host name, and then re-apply the operating permission configuration file that was applied before the host name was changed. For details about the operating permission configuration file, see 17.2.2 Customizing the operation restriction settings for each user in the JP1/Automatic Job Management System 3 Operator's Guide.
6	If JP1/AJS3 - Web Console is used and the host name of a manager host to which the Web Console server can connect is changed	Change the name of the connectible manager host in the environment settings file (`ajs3web.conf`) for JP1/AJS3 - Web Console. For details about the environment settings file (`ajs3web.conf`) in Windows, see 3.4.3 Details on the settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For details about the environment settings file (`ajs3web.conf`) in Linux, see 13.3.3 Details on settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.
7	If linkage with HP OpenView NNM or HP NNM is used and you change the name of the host that is used as the NNM monitoring host	Change the transfer destination of the SNMP trap on the Windows host on which the monitored JP1/AJS3 has been installed. For details on how to change the transfer destination of a SNMP trap, see A.2(3) Setting up SNMP trap destinations in the JP1/Automatic Job Management System 3 Linkage Guide. If JP1/AJS3 is installed on a UNIX host, it is not necessary to set the transfer destination of a SNMP trap.

To Page Top

(3) Procedure for changing the host name of JP1/AJS3 - Agent

To change the host name of JP1/AJS3 - Agent, use the command to be used for execution agent operation. When QUEUE jobs and submit jobs are used, also perform step 4.

To change the host name of JP1/AJS3 - Agent:

End the jobnets registered for execution on the agent host whose name is to be changed, and cancel their registration.
If the following services are running on the agent hosts whose names you want to change, stop those services:
- JP1/AJS3 services on the physical host and all logical hosts on the agent host
- JP1/AJS3 Queueless Agent service
- JP1/AJS3 Check Agent service
Execute the ajsagtalt command on the manager host to change the host name in the execution agent information that contains the definition of the agent host whose name is to be changed.

For details about the ajsagtalt command, see ajsagtalt in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
When QUEUE jobs and submit jobs are used, execute the jpqagtdel command on the manager host to delete the old agent host. Then execute the jpqagtadd command on the manager host to add the new agent host.

For details about the jpqagtdel command, see jpqagtdel in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

As soon as you add the agent host, the entrance of the default queue created when the agent was added is closed. Change the attributes of the default queue as required.

For details about the jpqagtadd command and how to change the default queue attributes, see jpqagtadd in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.
Change the host name of the agent host.

Change the name of the agent host.

If you are using JP1/AJS3 in a cluster system, and you are changing logical host names, first delete the old names and then perform setup again so that the cluster system will operate with the new logical host names.

In Windows:

For details about deleting logical host names, see 8.2.8 Deleting logical hosts in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about setting up a cluster system, see 8. Setup for Operation in a Cluster System in the JP1/Automatic Job Management System 3 Configuration Guide.

In UNIX:

For details about deleting logical host names, see 17.2.8 Deleting logical hosts in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about setting up a cluster system, see 17. Setup for Operation in a Cluster System in the JP1/Automatic Job Management System 3 Configuration Guide.
If you are using the communication encryption function and change the host name to one different from the CN or SAN in the server certificate, acquire and deploy the server certificate again.

To change the host name to one different from the CN or SAN in the server certificate, you need to acquire and deploy the server certificate again. If the CA of the issuer of the reacquired server certificate is different from that of the original certificate, you also need to acquire and deploy the root certificate.

For details about how to acquire and deploy server certificates and root certificates, see 21.4 Setting up the communication using SSL in the JP1/Automatic Job Management System 3 Configuration Guide.
Cold-start the JP1/AJS3 services on the agent host.

For details about performing a cold start, see 6.2.1 Temporarily changing the start mode of JP1/AJS3.

Cautionary note

Confirm that communication is possible between the new agent host and the manager host.
If necessary, start the services you stopped in step 2.
Re-register the jobnets and resume operation.

Re-register the jobnets you canceled in step 1 as required.

To Page Top

(4) Procedure for changing the host name of JP1/AJS3 - Web Console

The following explains the procedure for changing the host name of JP1/AJS3 - Web Console.

Note that, in the procedure explained here, JP1/AJS3 - Web Console and JP1/AJS3 - Manager are installed on different hosts. For details about how to change the host name when JP1/AJS3 - Web Console and JP1/AJS3 - Manager are installed on the same host, see (2) Procedure for changing the host name of JP1/AJS3 - Manager.

Stop the JP1/AJS3 HTTP Server service and the JP1/AJS3 Web Application Server service on the Web Console server.
Change the host name of the Web Console server.

Change the host name of the Web Console server.
If you are using the communication encryption function and change the host name to one different from the CN or SAN in the server certificate, acquire and deploy the server certificate again.

To change the host name to one different from the CN or SAN in the server certificate, you need to acquire and deploy the server certificate again. If the CA of the issuer of the reacquired server certificate is different from that of the original certificate, you also need to acquire and deploy the root certificate.

For details about how to acquire and deploy server certificates and root certificates, see 21.4 Setting up the communication using SSL in the JP1/Automatic Job Management System 3 Configuration Guide.
In the HTTP server definition file (httpsd.conf), set the new host name.

For details about the HTTP server definition file (httpsd.conf) in Windows, see 3.4.5 Details on the settings in the HTTP server definition file (httpsd.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For details about the HTTP server definition file (httpsd.conf) in UNIX, see 13.3.5 Details on settings in the HTTP server definition file (httpsd.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.
If linkage with JP1/IM is set up, change the host name specified for the Web Console server that is called from JP1/IM.

For details on setting up linkage with JP1/IM, see 10.2 Setup for linking JP1/IM in the JP1/Automatic Job Management System 3 Linkage Guide.
The system starts the JP1/AJS3 HTTP Server service and JP1/AJS3 Web Application Server service on the Web Console server.

To Page Top