Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 System Design (Configuration) Guide

2.3.1 Network configurations that are supported by JP1/AJS3

JP1/AJS3 supports the following network configurations:

Check the following when setting up the network configuration of a server running JP1/AJS3:

NIC grouping

Many OSs provide the ability to group together two or more NICs, enabling you to fail over to a backup NIC when one NIC fails. Examples include NIC teaming in Windows, Multipath in Solaris, and EtherChannel in AIX. When you use these NIC grouping features on servers running JP1, their operation must be transparent to JP1 and have no effect on its operation.

JP1/AJS3 communication settings are based on the JP1/Base communication settings. JP1/Base is the prerequisite program for JP1/AJS3, and its communication settings can be changed to accommodate a variety of network configurations. To change the communication settings, use the jp1hosts definition file or jp1hosts2 definition file, and the communication protocol settings file. Note that the network configurations of JP1/AJS3 - Manager and JP1/AJS3 - Agent are based on these communication settings.

For details about the JP1/Base communication settings, see the chapter on JP1/Base communication protocols and the chapter on JP1/Base communication settings based on network configurations in the JP1/Base User's Guide.

Cautionary notes

  1. JP1/AJS3 - View and JP1/AJS3 - Web Console do not support the functionality for changing JP1/Base communication protocol settings. To enable communication from JP1/AJS3 - View or JP1/AJS3 - Web Console to JP1/AJS3 - Manager by specifying the host name of the manager host, use the hosts file or DNS information.

  2. Note that when an OS allows multiple IP addresses to be resolved from a single host name, the event/action control function and the job execution control function operate differently depending on whether the communication protocol for multiple LAN connections has been set for JP1/Base.

    When the communication protocol for multiple LAN connections has not been set for JP1/Base

    Resolved IP addresses are used one after another until a connection is successfully established.

    When the communication protocol for multiple LAN connections has been set for JP1/Base

    A connection is attempted only to the resolved IP address at the beginning of the jp1hosts definition file or the jp1hosts2 definition file.

  3. JP1/AJS3 does not perform correctly in an environment where IP addresses are changed dynamically and the destination host changes. Run JP1/AJS3 in an environment where a unique host name and IP address can be determined. However, if the host is used as the destination agent for a flexible job, JP1/AJS3 can run in an environment where IP addresses are changed dynamically.

  4. Because embedded databases do not conform to the JP1/Base communication settings, you will need to use OS functionality to resolve the physical host name or logical host name to an IP address.

  5. If JP1/AJS3 - Manager version 10-00 or later was used to set up the embedded database, use the loopback address (127.0.0.1) for communication within the embedded database and between the JP1/AJS3 - Manager and the embedded database.

  6. JP1/AJS3 does not work properly in an environment where the same destination host name is duplicated on hosts that are connected to multiple networks. Make sure that the host names used for communication are unique, and that unique IP addresses can be obtained from the host names.

    The following figure shows an example of an environment where the same destination host name is duplicated on hosts that are connected to multiple networks.

    Figure 2‒14: Example of a host name being duplicated on hosts that are connected to multiple networks

    [Figure]

    In the example above, the same host name, HostA, is used in LAN_A and in LAN_B. As a result, HostB is unable to determine whether HostA corresponds to LAN_A or LAN_B.

  7. If you want to disable NIC (Network Interface Card) to resolve a network failure or some other issue, stop the JP1/AJS3 service before disabling NIC.

    Problems occur if you disable NIC without stopping the JP1/AJS3 service. For example, jobs do not start, or job statuses are not updated.

The following table shows the support status of communication settings for the functionalities provided by JP1/AJS3.

Table 2‒4: Support status of communication settings for the functionality provided by JP1/AJS3

Functionality

Communication settings

jp1hosts definition file or jp1hosts2 definition file

Communication protocol settings file

PC jobs

Unix jobs

QUEUE jobs

Passing information setting jobs

Submit jobs

Y

Y

Custom jobs

Y#2

Y#2

Queueless jobs

Y

--#3

Flexible jobs

Y#4

Y#4

HTTP connection jobs

Y#5

Y#5

Judgment jobs

NC

NC

OR jobs

NC

NC

Event jobs#1

Receive JP1 Event job

Y (NC)

Y (NC)

Monitoring Files job

Y (NC)

Y (NC)

Receive Mail job

Y (--)

Y (--)

Receive MQ Message job

Y (NC)

Y (NC)

Receive MSMQ Message job

Y (--)

Y (--)

Monitoring Log Files job

Y (NC)

Y (NC)

Monitoring Event Log job

Y (NC)

Y (NC)

Interval Control job

Y (NC)

Y (NC)

Action jobs#1

Send JP1 Event job

Y (Y#6, #7)

Y (Y#6)

Send Mail job

Y (--)

Y (--)

Send MQ job

Y (--)

Y (--)

Send MSMQ message job

Y (--)

Y (--)

OpenView Status Report job

Y (--)

Y (--)

Local Power Control job

Y (Y#8, #9)

Y (--)

Remote Power Control job

Y (Y#6, #7, #8, #9)

Y# (Y#6, #8)

Jobnet connector

Y#10

Y#10

Remote jobnets

Y

Y

Schedule execution

NC

NC

Remote execution of commands

Y

Y
Legend:

Y: Supported

--: Not supported

NC: No communication

#1

Y, --, and NC indicate whether the communication setting applies for communication between manager and agent hosts. Y (Y), Y (--), and Y (NC) indicate whether the communication setting with the linked program applies when an event job or an action job is executed.

#2

Supported for communication between the manager hosts and the agent hosts, but the status of support for the communication settings of a program to which a custom job links depends on that program.

#3

ANY binding is set for the receive setting. The Communication protocol settings file is supported for the send setting.

#4

Supported for communication between the manager host and the relay agent, but not supported for communication with the destination agent, the broadcast agent, and the destination agent at the broadcast destination.

#5

Supported for communication between the manager hosts and the agent hosts, but not supported for communication between the agent hosts and the web server.

#6

The support status is based on the event server settings file (conf) of JP1/Base. For details, see the description of Definition Files in the JP1/Base User's Guide.

#7

The support status is based on the API settings file (api) of JP1/Base. For details, see the description of Definition Files in the JP1/Base User's Guide.

#8

Not supported for communication with the power control.

#9

JP1/Power Monitor for UNIX does not support the jp1hosts definition file or the jp1hosts2 definition file. JP1/Power Monitor for Windows supports the jp1hosts definition file and the jp1hosts2 definition file. Note that the communication functionality of JP1/Power Monitor for Windows depends on the JP1PW_USE_JP1HOSTS environment setting parameter.

#10

This indicates whether communication settings can be specified when the execution order of root jobnets of different scheduler services is to be controlled. The jobnet connector does not communicate to control the execution order of root jobnets of the same scheduler services.

To Page Top

Copyright (C) 2019, 2022, Hitachi, Ltd.

Copyright (C) 2019, 2022, Hitachi Solutions, Ltd.