9.3.1 Setup procedure for linking JP1/IM2
The following figure shows an example of a system configuration for linking with JP1/IM2.
|
In the preceding example, JP1/IM2 is used to monitor three JP1/AJS3 hosts. In response to a request from JP1/IM2 - Manager, JP1/AJS3 - Manager on each manager host returns the configuration information of jobnets to JP1/IM2 - Manager. The events issued by all instances of JP1/AJS3 - Manager are collected by JP1/IM2 - Manager. All such communications are performed via JP1/Base.
A user who is logged in to JP1/IM2 - Manager from a web browser can view the following information: jobnet configuration information collected from the JP1/AJS3 manager hosts, jobnet statuses updated by events, and links between jobnets that use JP1 event linkage.
The following figure shows the setup procedures for linking JP1/IM2.
|
- #1
-
For details about how to set up the JP1/AJS3 plugin settings file, see (1) Setting up linkage with JP1/IM2 (procedure to be performed on the JP1/IM2 manager host).
For details about other settings, see the JP1/Integrated Management 3 - Manager Configuration Guide.
- #2
-
For details, see (2) Setting up linkage with JP1/IM2 (procedure to be performed on the JP1/AJS3 manager host).
- #3
-
This procedure is unnecessary if Web GUI (Job Portal) is not used.
- Organization of this subsection
(1) Setting up linkage with JP1/IM2 (procedure to be performed on the JP1/IM2 manager host)
Set up the JP1/AJS3 plugin settings file on the manager host.
-
Open the JP1/AJS3 plugin settings file by using a text editor.
Open the following file:
-
In Windows
JP1/IM2-Manager-installation-folder\conf\imdd\plugin\jp1ajs\settings.conf
or
shared-folder\jp1imm\conf\imdd\plugin\jp1ajs\settings.conf
-
In UNIX
/etc/opt/jp1imm/conf/imdd/plugin/jp1ajs/settings.conf
or
shared-directory/jp1imm/conf/imdd/plugin/jp1ajs/settings.conf
-
-
Modify the definitions to be changed.
Specify definitions in the following format.
{ "ajswebconUrl":"value", "linkValueLimit":value, "prewaitLink":"{y|n}", "netcnLink":"{y|n}", "evRegexLink":"{y|n}", "evMacroLink":"{y|n}", "evotherLink":"{y|n}", "evIpLink":"{y|n}" }
The following table shows the items to be set.
Table 9‒2: Items to be set in the JP1/AJS3 plugin settings file Item name
Value
Description of values
ajswebconUrl
communication-protocol://server-name:port-number/ajs/login.html
- communication-protocol
-
Specify http or https as the communication protocol.
- server-name
-
Specify the host name or IP address of the JP1/AJS3 - Web Console server.
- port-number
-
Specify the port number to be used for communication with the JP1/AJS3 - Web Console server. If SSL communication is disabled, the default port number is 22252. If SSL communication is enabled, the default port number is 22253.
linkValueLimit
1 to 2,000
Specify a maximum number for connections among root jobnets that obtain the impact on subsequent jobs and the scheduled date and time for linkage.
64 is assumed in the following cases.
-
If the value is omitted
-
If a value out of range or a value that is not a number is specified as the setting
prewaitLink#1
y|n
Specify whether to create associations with wait conditions.
-
y: Creates associations.
-
n: Does not create associations.
The value to be specified (y or n) is case-sensitive.
The value y is assumed in the following cases:
-
If the value is omitted
-
If a value that is neither y nor n is specified
netcnLink
y|n
Specify whether to create associations with jobnet connectors.
-
y: Creates associations.
-
n: Does not create associations.
The value to be specified (y or n) is case-sensitive.
The value y is assumed in the following cases:
-
If the value is omitted
-
If a value that is neither y nor n is specified
evRegexLink
y|n
Specify whether to apply the regular expression when creating associations with JP1 events.
-
y: Creates associations assuming that the specified values are regular expressions.
-
n: Creates associations assuming that the specified values are ordinary character strings rather than regular expressions.
The value to be specified (y or n) is case-sensitive.
The value n is assumed in the following cases:
-
If the value is omitted
-
If a value that is neither y nor n is specified
evMacroLink
y|n
For macro variables used for JP1 event linkage, specify whether associations are created by using simple string matches, or whether associations with JP1 events that use macro variables are not created.
-
y: Creates associations by using simple string matches.
-
n: Does not create associations with JP1 events that use macro variables.
The value to be specified (y or n) is case-sensitive.
The value y is assumed in the following cases:
-
If the value is omitted
-
If a value that is neither y nor n is specified
evotherLink
y|n
Specify whether to create associations if a unit definition#2 that is not used as an association condition for JP1 event linkage is used.
-
y: Creates associations.
-
n: Does not create associations.
If you specify y, you can use the evIpLink setting to specify whether comparison is made with the IP address of the event issuer host.
The value to be specified (y or n) is case-sensitive.
The value n is assumed in the following cases:
-
If the value is omitted
-
If a value that is neither y nor n is specified
evIpLink
y|n
Specify whether comparison is made with the IP address of the event issuer host for the JP1 event reception monitoring job.
This item takes effect only if y is specified for evotherLink.
If n is specified for evotherLink, the specification of this item is ignored.
-
y: Performs comparison with the IP address. If the comparison results in a match, an association is created. In other cases, no association is created.
-
n: Creates an association without performing comparison with the IP address. The IP address is ignored even if it is defined.
The value to be specified (y or n) is case-sensitive.
The value n is assumed in the following cases:
-
If the value is omitted
-
If a value that is neither y nor n is specified
- #1
-
When you set this item, see (2)(c) Settings according to the operation.
- #2
-
The following unit definitions are not used as association conditions for JP1 event linkage:
evusr="event-issue-source-user-name"
Define the user name of the event issue source in the basic information on an event to be received.
evgrp="event-issue-source-group-name"
Define the group name of the event issue source in the basic information on an event to be received.
evipa=event-issue-source-IP-address
Define the IP address of the event issue source in the basic information about an event to be received.
evuid=event-issue-source-user-ID
Define the user ID of the event issue source in the basic information about an event to be received.
evgid=event-issue-source-group-ID
Define the group ID of the event issue source in the basic information about an event to be received.
evpid=event-issue-source-process-ID
Define the process ID of the event issue source in the basic information about an event to be received.
evdet="detailed-event-information"
Define a character string that is to be compared with the detailed information part of an event received.
-
Save the settings.conf file.
- Important
-
-
The settings in the JP1/AJS3 plugin settings file take effect immediately. If the file is saved at the same time that JP1/IM2 is operating, the file might not be read normally and an error might occur. In this case, save the file again.
-
If a new installation of JP1/IM2 was performed, the values of the settings in the JP1/AJS3 plugin settings file are as follows:
{
"prewaitLink":"y",
"netcnLink":"y",
"evRegexLink":"y",
"evMacroLink":"n",
"evotherLink":"y"
"evIpLink":"y"
}
-
If an overwrite installation or an upgrade installation of JP1/IM2 was performed, the JP1/AJS3 plugin settings file is not updated.
If no settings are specified in the JP1/AJS3 plugin settings file, assumptions are made for omitted values.
-
(2) Setting up linkage with JP1/IM2 (procedure to be performed on the JP1/AJS3 manager host)
To use trend information display function, make sure that the JP1/AJS3 manager host meets the following prerequisite conditions.
- Prerequisite conditions:
-
-
On the JP1/AJS3 manager host, to change the system time by using NTP (Network Time Protocol), etc., make sure the following conditions are met.
- Operate in slew mode, etc., and make adjustments in units of milliseconds so that the same time does not occur.
- Configure settings to output logs when the system time is adjusted, so that time adjustments can be checked after they are made.
-
If you move the system time backward, delete the performance log files.
For details, see 7.9.3 Changing the date and time of the system in the JP1/Automatic Job Management System 3 Administration Guide.
-
On the JP1/AJS3 manager host, perform the following procedure to set up linkage with JP1/IM2:
(a) Setting up the adapter command settings file
-
Copy the Adapter_HITACHI_JP1_AJS3_CONFINFO.conf.model file to the JP1/Base-installation-folder\plugin\conf folder.
The following shows the location of the Adapter_HITACHI_JP1_AJS3_CONFINFO.conf.model file.
JP1/AJS3 - Manager-installation-folder\tools\IMDDAdapter\conf
-
Rename the copied file.
Before the change
Adapter_HITACHI_JP1_AJS3_CONFINFO.conf.model
After the change
Adapter_HITACHI_JP1_AJS3_CONFINFO.conf
If JP1/AJS3 has been installed in a folder that is not the default installation folder in Windows, additionally perform the following procedure:
-
Open the Adapter_HITACHI_JP1_AJS3_CONFINFO.conf file by using a text editor.
-
Change the path specified for the cmdpath attribute in the file.
fileversion 12000000 cmdpath JP1/AJS3 - Manager-installation-folder\tools\IMDDAdapter\IMDDAdapter_HITACHI_JP1_AJS3.bat upperpp /HITACHI/JP1/IM/DD componenttype JDD_CONFINFO
(b) Configuring settings to detect factors that might stop job execution
By linking with JP1/IM2, JP1/AJS3 can monitor and report the following three items to prevent failures that stop the job execution of scheduler services:
-
Number of jobs in the Now queuing or Now running status
-
Number of execution generations in the Wait for start cond. status
-
Number of unreported information items managed by the event/action control manager
For details about the settings, see 21.7 Settings for detecting factors that might stop job execution in the JP1/Automatic Job Management System 3 Configuration Guide.
(c) Settings according to the operation
Specify the following settings according to the operation:
-
Change the value of the EXECREGISTRATIONNUMBER environment setting parameter to execution if either of the following conditions is met when you create a relation about waiting: 1) A time other than 0:00 is set as the base time of waiting-target units and units with wait conditions, or 2) dword:00000030 is set for the ROOTJOBNETSCHEDULERANGE environment setting parameter of the scheduler service for which the units are defined.