Job Management Partner 1/Base User's Guide
Various problems might occur if you use the default event server in a system that has multiple domains. This subsection describes how to set up the event servers in a system that uses DNS services, based on the following example. Note that the following example assumes that the DNS returns the FQDN name as the local host name.
The following figure shows a system that contains two domains, d1.hitachi.co.jp and d2.hitachi.co.jp.
Figure 8-1 Example system containing two domains
In this example, a JP1 event indicating insufficient disk space occurs in the hostX.d1.hitachi.co.jp domain. A JP1 event is forwarded to host3.d2.hitachi.co.jp and displayed in JP1/IM - View on host4. The registered host name appears as hostX. Since hostX also exists in domain d2.hitachi.co.jp in the above figure, the system administrator cannot tell whether the JP1 event occurred at hostX.d1.hitachi.co.jp or at hostX.d2.hitachi.co.jp. JP1/IM - View has a window for monitoring from which programs it receives JP1 events. However, if the host running JP1/IM - View belongs to domain d2.hitachi.co.jp, it interprets hostX to be hostX.d2.hitachi.co.jp and displays the wrong information.
To avoid these sorts of problems with multiple domains, instead of the default event server, define an event server with a Fully Qualified Domain Name (FQDN-format event server).
- Notes
- When you use an FQDN-format event server, the JP1/SES compatibility function or collection and distribution of event service definition information described in J. Linking with Products That Use JP1/SES Events might not be possible. Keep this in mind when using the JP1/SES compatibility function or collecting and distributing event service definition information.
- While using an FQDN-format event server, a JP1/AJS log file monitoring job on the physical host is not available. To use a JP1/AJS log file monitoring job, do not configure an FQDN-format event server as described in (1), and specify the local host name (the host name that is returned by the hostname command) in FQDN-format.
The following describes the procedure for setting up an FQDN-format event server. The procedure differs in Windows and UNIX. The procedures for Windows and UNIX are described below.
- Organization of this subsection
- (1) Setting up an FQDN-format event server (Windows)
- (2) Setting up an FQDN-format event server (UNIX)
(1) Setting up an FQDN-format event server (Windows)
Follow these steps to set up an FQDN-format event server in Windows. The specified event server here is assumed to be hostX.d1.hitachi.co.jp.
- Register the FQDN-format event server as a service by using the jevregsvc command.
The jevregsvc command has the following format:
jevregsvc -r hostX.d1.hitachi.co.jp
- Note
- If JP1/IM - Manager or JP1/AJS has been installed, dependencies exist with the default services. In Windows, to set up an FQDN-format event server, release the dependencies between JP1/IM - Manager or JP1/AJS and the default event services.
- Open the event server index file (index) in a text editor. Change the event server name in the server parameter from * (default) to @ or hostX.d1.hitachi.co.jp.
If you change the parameter to @, you can use the JP1/SES compatibility function or collect and distribute event service definition information. If you change the parameter to hostX.d1.hitachi.co.jp, you can no longer use the JP1/SES compatibility function nor collect and distribute event service definition information. Choose whichever setting suits your system.
- Open the start sequence definition (JP1SVPRM.DAT) file in a text editor. Edit the file to start the FQDN-format event server instead of the default event server.
The entry in the edited start sequence definition (JP1SVPRM.DAT) file (only the part pertaining to the event server) is as follows:
(2) Setting up an FQDN-format event server (UNIX)
Follow these steps to set up an FQDN-format event server in UNIX. The specified event server here is assumed to be hostX.d1.hitachi.co.jp.
- Open the event server index file (index) in a text editor. Change the event server name in the server parameter from * (default) to @ or hostX.d1.hitachi.co.jp.
If you change the parameter to @, you can use the JP1/SES compatibility function or collect and distribute event service definition information. If you change the parameter to hostX.d1.hitachi.co.jp, you can no longer use the JP1/SES compatibility function nor collect and distribute event service definition information. Choose whichever setting suits your system. The entry in the event server index file (index) when the event server name is changed to @ is as follows:
- Open the jbs_start and jbs_stop scripts in a text editor. Edit the scripts to start and stop the FQDN-format event server instead of the default event server.
The entries in the edited scripts (only the part pertaining to the event server) are as follows:
- Entry in the jbs_start script:
- Entry in the jbs_stop script:
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.