Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference

3.8.3 Settings on JP1/AJS3 - Web Operation Assistant

When the database type for the scheduler service to be monitored is an embedded database or HiRDB, JP1/AJS3 - Web Operation Assistant uses an internal client to connect to the embedded database or HiRDB server used by the scheduler service. The connection is established during status acquisition.

You can customize the operating environment for the HiRDB client by using a client environment definition. The client environment definition to be referenced by the HiRDB client in JP1/AJS3 - Web Operation Assistant can be set in the RDB connection definition file (RDBINF.conf).

Organization of this subsection

(1) Setting up the RDB connection definition file

(2) RDB connection definition file

(3) Notes on defining the RDB connection definition file

(1) Setting up the RDB connection definition file

The following describes the procedure for setting up the RDB connection definition file for specification of communication-related information.

To set up the RDB connection definition file:
Stop the HTTP server.
From Windows Control Panel, choose Administrative Tools and Services, and then stop the following service:
JP1/AJS3 WOA HTTP Server

Stop the application server.
From Windows Control Panel, choose Administrative Tools and Services, and then stop the following service:
JP1/AJS3 WOA Web Application Server
Copy the following model file of an RDB connection definition file to the folder containing the original file.
 
JP1/AJS3 - Web-Operation-Assistant-installation-folder\conf\dbclient\RDBINF.conf.model
 
Rename the file you have copied in step 3 RDBINF.conf.

Use a text editor such as Notepad to open the files created in steps 3 and 4. Then, for each host to be monitored, set the value in the client environment definition according to the network configuration.
For details about the settings in the client environment definition when you use an embedded database for the scheduler service to be monitored, see 3.8.3(2) RDB connection definition file. If you use HiRDB, see the manual for your HiRDB.

Start the application server.
From Windows Control Panel, choose Administrative Tools and Services, and then start the following service you stopped in step 2:
JP1/AJS3 WOA Web Application Server

Start the HTTP server.
From Windows Control Panel, choose Administrative Tools and Services, and then start the following service you stopped in step 1:
JP1/AJS3 WOA HTTP Server

(2) RDB connection definition file

(a) Contents of RDBINF.conf.model

The following shows the contents of the model file of an RDB connection definition file:
 
[OBSERVE_HOSTNAME]
GETSTATUSMODE=
OBSERVESRVTYPE=
[OBSERVE_HOSTNAME:OBSERVE_SCHEDULERSERVICENAME]
PDSERVICEPORT=
PDSERVICEGRP=
PDFESHOST=
PDSRVTYPE=
PDCLTRCVPORT=
PDCLTRCVADDR=
 
(b) Format of the RDB connection definition file

Specify the parameters and client environment definition in the RDB connection definition file.

The format of the RDB connection definition file is shown below.

If you want JP1/AJS3 - Web Operation Assistant to connect to more than one monitoring target at the same time, set the RDB connection definition file for each monitoring target.

(c) List of environment settings parameters in the RDB connection definition file

The following describes the parameters for a scheduler service to be monitored.

Use the following parameters to specify the target scheduler service.

Table 3-4 Specifying the target scheduler service (in the RDBINF.conf file)

Parameter Description Remarks

OBSERVE_HOSTNAME Specifies the name of the host to be monitored. Specify the same value as the name of the host to be monitored that is specified in the frame for setting status acquisition conditions.
You can also use the FQDN format to specify the host name.

OBSERVE_SCHEDULERSERVICENAME Specifies the scheduler service name to be referenced during status acquisition. Specify the same value as the name of the service to be monitored that is specified in the frame for setting status acquisition conditions. Alphabetic characters are case sensitive.

The following lists the parameters to be specified in the client environment definition when the database type for the scheduler service to be monitored is an embedded database. If you use HiRDB as the database for the scheduler service to be monitored, see the manual for your HiRDB.

Table 3-5 List of parameters in the RDB connection definition file (RDBINF.conf)

Parameters Description

GETSTATUSMODE Specifies the status acquisition mode for the monitoring target.

OBSERVESRVTYPE Specifies the type of server (WS or PC) for the embedded database server or HiRDB server at the monitoring target.

PDSERVICEPORT Specifies the port number for connection with a client on the embedded database server to be monitored.

PDSERVICEGRP Specifies the single server name of the embedded database server to be monitored.

PDSRVTYPE Specifies the type of the embedded database server to be monitored.

PDCLTRCVPORT Specifies the port number for receiving data from a client on the JP1/AJS3 - Web Operation Assistant server.

PDCLTRCVADDR Specifies the IP address or host name of the JP1/AJS3 - Web Operation Assistant host.

(d) Settings in the RDB connection definition file

n Settings for the parameters

The settings for the parameters set in the RDB connection definition file are shown below.

GETSTATUSMODE={0|1}

Specifies the status acquisition mode.

0

Sets the conventional status acquisition mode (default).

1

Sets a status acquisition mode for large-scale operation in which a drop in performance can be suppressed, regardless of the overall size of the operation scale.

Make this setting when using an embedded database or HiRDB (version 7 or later) at the monitoring target.

If 1 is set for this parameter, be sure to set the OBSERVESRVTYPE parameter.

The default is 0.

OBSERVESRVTYPE={WS|PC}

Specifies the type of server for the embedded database server or HiRDB server at the monitoring target host. This parameter is enabled when 1 is set for the GETSTATUSMODE parameter.

WS

Set this value if the embedded database server or HiRDB server at the monitoring target is HP-UX, solaris, or AIX.

PC

Set this value if the embedded database server or HiRDB server at the monitoring target is Linux or Windows.

Note

If 1 is set for the GETSTATUSMODE parameter but no value is set for the OBSERVESRVTYPE parameter, an error will occur when the JP1/AJS3 WOA Web Application server service is started and you will be unable to perform status acquisition. Be sure to set a value for the OBSERVESRVTYPE parameter.

If the server type setting is different from the server type at the monitoring target host, the status of the unit will not be acquired correctly. Be sure to set the server type correctly.

n Settings for the client environment definition

The following describes in detail the client environment definition specified in the RDB connection definition file.

PDSERVICEPORT=client-connection-port-number[,secondary-node's-client-connection-port-number]

~<unsigned integer> ((5001-65535))

Specifies the port number on the embedded database server to be monitored. This port number is used to receive a search request for acquiring the status of JP1/AJS3 - Web Operation Assistant.

Specify this parameter when an environment for both of the following has been set up for the embedded database server to be monitored:

Packet filtering

NAT

Specify the value that is specified for the pd_service_port operand in the system definition for the embedded database server to be connected. For details on the pd_service_port operand when you are using JP1/AJS3 - Manager on the monitoring target, see the manual Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1. If you are using JP1/AJS2 - Manager Version 8, see the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide. If you are using JP1/AJS2 - Manager Version 7, see the manual Job Management Partner 1 Embedded Database Operator's Guide.

Note

If the monitoring target runs in a cluster configuration and different port numbers are specified for the pd_service_port operand in the system definition for the primary and secondary nodes, also specify the client connection port number for the secondary node. For details about port numbers, see Appendix C. List of Port Numbers.

PDSERVICEGRP=server-name

~<character string> ((30 or fewer bytes))

Specifies the single server name of the embedded database server to be monitored. Specify ajs2 if the server to be monitored uses an embedded database or if the HiRDB server to be monitored has been set up with the default setup script of JP1/AJS3 - Manager or JP1/AJS2 - Manager. For other cases, specify the single server name that was specified during setup.

Specify this parameter when an environment for both of the following has been set up for the embedded database server to be monitored:

Packet filtering

NAT

PDSRVTYPE={WS|PC}

Specifies the type of the embedded database server to be monitored.

WS

Specify this when the embedded database server to be monitored runs on HP-UX, Solaris, or AIX.

PC

Specify this when the embedded database server to be monitored runs on Linux or Windows.

PDCLTRCVPORT=receive-port-number-for-client

~<unsigned integer> ((5001-65535))

Specifies a port number on the JP1/AJS3 - Web Operation Assistant server. This port number is used to receive the search results from the embedded database server that the scheduler service to be monitored uses to acquire the status of JP1/AJS3 - Web Operation Assistant.

Specify this parameter when the following environment has been set up for JP1/AJS3 - Web Operation Assistant:

Packet filtering

Notes

When you want to concurrently acquire the status of more than one monitored scheduler service, specify a unique port number for each one of the scheduler services.

Specify a port number that is not included in the range of port numbers that the OS automatically assigns. This range differs depending on the OS.

Specify a port number that is not used by any other program.
For details about port numbers, see Appendix C. List of Port Numbers.

PDCLTRCVADDR={client-IP-address|client-host-name}

~<unsigned integer> or <identifier> ((256 or fewer bytes))

Specifies the IP address or host name of the JP1/AJS3 - Web Operation Assistant host. The IP address or host name is used to receive the search results from the embedded database server that the scheduler service to be monitored uses to acquire the status of JP1/AJS3 - Web Operation Assistant.

You can also use the FQDN format to specify the host name.

Specify this parameter when the following environment has been set up for JP1/AJS3 - Web Operation Assistant:

NAT

IP-address

Specify decimal numbers in dot notation.

Example: PDCLTRCVADDR=172.18.131.34

FQDN

FQDN is a name consisting of a host name and a domain name joined by a period.

Example: PDCLTRCVADDR=host1.soft.hitachi.co.jp

Note

If you specify an invalid IP address or host name in this environment variable, a response from the embedded database server cannot be received during status acquisition. As a result, a KAVI3250-E error message appears after five minutes of monitoring by a timer.

Parameter	Description	Remarks
OBSERVE_HOSTNAME	Specifies the name of the host to be monitored.	Specify the same value as the name of the host to be monitored that is specified in the frame for setting status acquisition conditions. You can also use the FQDN format to specify the host name.
OBSERVE_SCHEDULERSERVICENAME	Specifies the scheduler service name to be referenced during status acquisition.	Specify the same value as the name of the service to be monitored that is specified in the frame for setting status acquisition conditions. Alphabetic characters are case sensitive.

Parameters	Description
GETSTATUSMODE	Specifies the status acquisition mode for the monitoring target.
OBSERVESRVTYPE	Specifies the type of server (WS or PC) for the embedded database server or HiRDB server at the monitoring target.
PDSERVICEPORT	Specifies the port number for connection with a client on the embedded database server to be monitored.
PDSERVICEGRP	Specifies the single server name of the embedded database server to be monitored.
PDSRVTYPE	Specifies the type of the embedded database server to be monitored.
PDCLTRCVPORT	Specifies the port number for receiving data from a client on the JP1/AJS3 - Web Operation Assistant server.
PDCLTRCVADDR	Specifies the IP address or host name of the JP1/AJS3 - Web Operation Assistant host.

(3) Notes on defining the RDB connection definition file

Specify only one parameter on a line.

If the same monitoring target is entered more than once, the last entry takes effect.

If the same parameter is entered more than once, the last entry takes effect.

Lines that start with a semi-colon (;) are treated as comments.

Do not contain space characters in a line containing the monitoring target and parameter setting.

Blank lines are ignored.

[Contents][Back][Next]

[Trademarks]