2.3 Determining the network configuration

JP1/AJS3 supports the following network configurations:

Multiple LAN connections
Use of firewalls
IPv6 addresses (Windows Server 2012, Windows Server 2008 R2, and Linux only)

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.

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.

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 Job Management Partner 1/Base User's Guide.

Cautionary notes

The functions explained in this section are based on the functionality for changing the JP1/Base communication protocol settings, and allow JP1/AJS3 - Manager, JP1/AJS3 - Agent, and JP1/AJS3 - View to support that functionality. JP1/AJS3 - View cannot be used for communication using IPv6 addresses.
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.
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.
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.
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.

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

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.

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
Functionality		jp1hosts definition file or jp1hosts2 definition file	Communication protocol 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 job	--	--
	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

To Page Top