Job Management Partner 1/Base User's Guide

12.2.1 Effects and follow-up tasks when changing host names

This subsection describes the functionality that is affected by changing host names, and the tasks you must perform after the change.

Organization of this subsection

(1) User authentication

(2) User mapping

(3) Event service

(4) When using JP1/IM - Manager

(5) When using a cluster system

(6) Hitachi Network Objectplaza Trace Library (HNTRLib2)

(1) User authentication

If you change the host name of the authentication server in Windows, in the JP1/Base Environment Settings dialog box, display the Authentication Server page. Then, change the host name. For UNIX, use the jbssetusrsrv command to change the host name. The user authentication function is not affected unless the host name of the authentication server is changed.

(2) User mapping

For the user mapping function, perform the following carefully so that none of the host names remain unchanged.

(a) When the manager host name is changed

On every agent host for which remote command execution is issued from a manager, check the mapping definition file that is on the agent host.

The second field server-host-name in JP1-user-name:server-host-name:user-list in the mapping definition file needs to be changed when the manager host name is changed.

To change the information:

Execute the jbsgetumap command and acquire the text file.

Change the applicable server host name to the new server host name.
You do not need to change the server host name if the old server host name is *.

After you change the server host name, execute the jbsmkumap command and register the new definition.

For details on the commands, see jbsgetumap and jbsmkumap in 13. Commands.

Note

If you are using domain names for DNS operation, specify a host name in Fully Qualified Domain Name (FQDN) format in server-host-name.

(b) When the agent host name is changed

Changing an agent host name has no effect.

(3) Event service

If you have specified host names in the environment settings files (all in the text format) of the event service, you need to correct them completely. Only the host names set by users need to be corrected. Default names do not need to be corrected. Since the event service does not automatically store default host names, you need not worry about correcting them.

(4) When using JP1/IM - Manager

When you use Read from Selected Event for an event search, you need to set hosts so the machine that uses JP1/IM - Manager can reference the old host name (for example, to make ping old-host-name successful). If you do not need this type of operation, you do not need to change the settings regarding the event service.

For JP1/IM - Manager, the system is configured using the configuration definition file. Therefore, each time a host name is changed, the system configuration needs to be redistributed (by executing the jbsrt_distrib command). Unless the system configuration is redistributed, JP1 events might not be forwarded correctly. For details on how to redistribute the system configuration, see the manual Job Management Partner 1/Integrated Management - Manager Administration Guide.

Note

For a JP1 event that was issued while an old host name was still in use, JP1/IM - View displays the old host name as the registered host name even after the host name is changed. When you perform a search, the old host name is also used as the registered host name. You cannot use this type of JP1 event to display the monitor screen for JP1/AJS.

(5) When using a cluster system

If you change a logical host name in a cluster system environment, delete the previous logical host name. And then, complete the same setup for the new logical host name.

In Windows:

For details on deleting a logical host name, see 3.4.6 Deleting logical hosts. For details on setting up a cluster system, see 3.4.3 Setup.

In UNIX:

For details on deleting a logical host name, see 3.5.6 Deleting logical hosts. For details on setting up a cluster system, see 3.5.3 Setup.

(6) Hitachi Network Objectplaza Trace Library (HNTRLib2)

It is not necessary to restart Hitachi Network Objectplaza Trace Library (HNTRLib2) after changing the host name. However, if you do not so, the previous logical host name is output to the header of the integrated trace log.

[Contents][Back][Next]

[Trademarks]