Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

[Contents][Glossary][Index][Back][Next]

2.3 Determining the network configuration

JP1/AJS3 supports the following network configurations:

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

MediaSense (in Windows)
We recommend that you disable the Windows MediaSense feature. This feature detects network problems such as the disconnection of a computer's network cable, and disables IP addresses. If MediaSense is enabled, IP addresses might be rendered inaccessible by what is only a temporary network problem, which will disrupt JP1 communication.

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.

The concept for the JP1/AJS3 communication settings is based on the communication settings of JP1/Base, which is a prerequisite program for running JP1/AJS3. You can change the communication settings of JP1/Base to suit various network configurations, by using the jp1hosts definition file and the communication method settings file. For details about the communication settings of JP1/Base, see the chapters that cover the communication protocols and network configurations in the Job Management Partner 1/Base User's Guide. For details about the communication settings in JP1/AJS3, see 2.3.3 Example configurations with multiple LANs and their communications settings or 2.3.4 Example of configurations that include a firewall, and their communications settings.

Cautionary notes
  1. The functionality explained in this section is based on the functionality for changing the communications method setting provided by JP1/Base, which is adapted so that it can also be used with JP1/AJS3. The behavior in JP1/AJS3-related programs is not guaranteed.
    For particulars about the behavior of related programs in the configuration described in this section, contact the developer.
  2. Note that when the settings for the communication method supported by JP1/Base Version 06-71 have been changed using the event/action control functionality or job execution control functionality, the communication method with an OS that can resolve multiple IP addresses from a single host name will differ from that of Version 06-51 and earlier.
    Version 06-51 and earlier
    Attempts to connect are made sequentially from the beginning of the hosts file until connection with the resolved IP address is successful.
    Changing the communications method with version 06-71 and earlier
    Among the resolved IP addresses, connection is attempted only with the IP address at the beginning of the jp1hosts 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.

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 Communication method settings file
JP1/AJS3 - View (job/jobnet operation) Y#1 Y#1
Job execution Y Y
Job execution (queueless jobs) Y --
Job submission Y Y
Judgment jobs NC NC
OR jobs NC NC
Event jobs#2 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#3 Send JP1 Event job -- Y#4
Send Mail job -- --
Send MQ job -- --
Send MSMQ message job -- --
OpenView Status Report -- --
Local Power Control job NC NC
Remote Power Control job -- Y#4
Remote jobnets Y Y
Schedule execution NC NC
Remote execution of commands Y Y
JP1/AJS3 Console Y#5 Y#5

Legend:
Y: Supported
--: Not supported
NC: No communication

#1
Supported for the settings at the manager host.

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

#3
This indicates the support status for the communication settings for the linked program, when each action job is executed. The communication settings between the manager and agent follow the statuses shown in the table for the job execution functionality and job execution (queueless job) functionality.

#4
Depends on the communication settings of the event service. Change them using the event server setting (conf) file. For details, see the description of the communication settings of JP1/Base according to different network configurations in the Job Management Partner 1/Base User's Guide.

#5
Supported for JP1/AJS3 Console Manager and JP1/AJS3 Console Agent. JP1/AJS3 Console View does not use the functionality of JP1/Base, so is not applicable.
Organization of this section
2.3.1 Connecting multiple LANs
2.3.2 Working through a firewall
2.3.3 Example configurations with multiple LANs and their communications settings
2.3.4 Example of configurations that include a firewall, and their communications settings
2.3.5 Communications used in a WAN
2.3.6 Checking operation in a DNS environment

[Contents][Back][Next]

[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.