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

2.3.3 Example configurations with multiple LANs and their communications settings

When connecting a host to multiple LANs in a non-cluster environment, you can use versions 06-51 and later of JP1/Base, and JP1/AJS2 at this host since you can use ANY bind as the communication method for both sending and receiving.

When a host is connected to multiple LANs in a cluster environment, you must use JP1/Base version 06-71 or later, and either JP1/AJS3 or JP1/AJS2 version 06-71 or later. You must also set IP bind for receiving and ANY bind for sending in the communication method settings, and map multiple IP addresses with the logical host name using jp1hosts.

When connecting a host to another host that is connected to multiple LANs, you must convert the destination host name to an IP address in advance. For example, in the configuration shown in Figure 2-18, you must ensure that when LANB_C attempts to obtain the IP address of LANA_B, it receives IP address LANB_B.

If this arrangement is not possible, for example when common hosts files are distributed or DNS is used, use JP1/Base Version 06-71 or later, and JP1/AJS, at LANB_C. You must also map the IP address of LANA_B with LANB_B using jp1hosts.

Figure 2-18 Example system configuration with connection to a computer that is connected to multiple LANs

The following shows example connections for cluster and non-cluster operations in environments providing connections to multiple LANs (dissociated networks), and the communications settings for these examples.

Organization of this subsection

(1) Example connections and communications settings for non-cluster operation

(2) Example connections and communications settings for cluster operation

(1) Example connections and communications settings for non-cluster operation

The following explains connection examples for non-cluster operation in environments where multiple LANs are connected (dissociated network environments), and their communications settings. We deal in turn with cases where JP1/AJS3 - Manager, JP1/AJS3 - Agent, and JP1/AJS3 - View are connected to multiple LANs.

Supplementary note

The JP1/AJS3 Console functionality also supports the same kind of network configurations. These examples would also apply if you replaced JP1/AJS3 - View with JP1/AJS3 Console View, JP1/AJS3 - Manager with JP1/AJS3 Console Manager, and JP1/AJS3 - Agent with JP1/AJS3 Console Agent.

(a) Cases where JP1/AJS3 - Manager is connected to multiple LANs for non-cluster operation

When JP1/AJS3 - Manager is connected to multiple LANs, you can connect JP1/AJS3 to JP1/AJS3 - Agent, JP1/AJS3 - View, or JP1/AJS3 - Manager on a LAN.

n Case where JP1/AJS3 - Manager is connected to multiple LANs and linked to JP1/AJS3 - Agents on the LANs

In a case where JP1/AJS3 - Manager is connected to multiple LANs to work with JP1/AJS3 - Agents on the LANs, you can execute jobs with JP1/AJS3 - Agents on the LANs. Such a system is shown below.

Figure 2-19 JP1/AJS3 - Manager connected to multiple LANs (connection to JP1/AJS3 - Agents)

Here, the host hostX, where JP1/AJS3 - Manager is installed, is connected to multiple LANs. JP1/AJS3 - Agent is installed on each of these LANs.

In this system configuration, hostX serves as the manager host and jobs can be executed at the agent host host10 in the Management LAN, and the agent hosts HostA and hostB in the Work task LAN.

Regarding the communications settings at each host, follow the example communications settings for non-cluster operation in the Job Management Partner 1/Base User's Guide.

The hosts host10, hostA, and hostB require an OS environment that can resolve the host name of hostX.

n Case where JP1/AJS3 - Manager is connected to multiple LANs and linked to JP1/AJS3 - Views on the LANs

In a case where JP1/AJS3 - Manager is connected to multiple LANs to work with JP1/AJS3 - Views on the LANs, jobs and jobnets can be operated from JP1/AJS3 - Views. Such a system is shown below.

Figure 2-20 JP1/AJS3 - Manager connected to multiple LANs (connection to JP1/AJS3 - Views)

Here, the host hostX, where JP1/AJS3 - Manager is installed, is connected to multiple LANs. JP1/AJS3 - View is installed on each of these LANs.

In this system configuration, jobnets and jobs at the manager host hostX can be operated from JP1/AJS3 - View at host10 on the Management LAN, and from JP1/AJS3 - Views at hostA and hostB on the Work task LAN.

Regarding the communications settings at host hostX, follow the example communications settings for non-cluster operation described in the Job Management Partner 1/Base User's Guide.

The hosts host10, hostA, and hostB require an OS environment that can resolve the host name of hostX.

Cautionary note

You might have set the IP bind communication method for reception at hostX where JP1/AJS3 - Manager is installed. In this case, in jp1hosts, you must set both the IP addresses on the Management LAN and Work task LAN for the host name of hostX.

n Case where JP1/AJS3 - Manager is connected to multiple LANs and linked to JP1/AJS3 - Managers on the LANs

In a case where JP1/AJS3 - Manager is connected to multiple LANs to work with JP1/AJS3 - Managers on the LANs, from the JP1/AJS3 - Managers, you can execute remote jobnets, and remotely execute scheduler commands. Such a system is shown below.

Figure 2-21 JP1/AJS3 - Manager connected to multiple LANs (connection to JP1/AJS3 - Managers)

Here, the host hostX, where JP1/AJS3 - Manager is installed, is connected to multiple LANs. JP1/AJS3 - Manager is installed on each of these LANs.

In this system configuration, the manager host, hostX, is connected to the manager host host10 on the Management LAN, and to the manager hosts hostA and hostB on the Work task LAN. hostX executes remote jobnets and remotely executes scheduler commands.

Regarding the communications settings at the hosts host10, hostA, and hostB, follow the example communications settings for non-cluster operation described in the Job Management Partner 1/Base User's Guide.

The host hostX requires an OS environment that can resolve the host names of host10, hostA, and hostB.

(b) Cases where JP1/AJS3 - Agent is connected to multiple LANs for non-cluster operation

When JP1/AJS3 - Agent is connected to multiple LANs, you can execute jobs from JP1/AJS3 - Managers on the LANs. Such a system is shown below.

Figure 2-22 JP1/AJS3 - Agent connected to multiple LANs (connection to JP1/AJS3 - Managers)

Here, the host hostX, where JP1/AJS3 - Agent is installed, is connected to multiple LANs. JP1/AJS3 - Manager is installed on each of these LANs.

In this system configuration, hostX is the agent host. Jobs can be executed from the manager host host10 on the Management LAN and from the manager hosts hostA and hostB on the Work task LAN.

Regarding the communications settings at each host, follow the example communications settings for non-cluster operation described in the Job Management Partner 1/Base User's Guide.

The hosts host10, hostA, and hostB require an OS environment that can resolve the host name of hostX.

(c) Cases where JP1/AJS3 - View is connected to multiple LANs to operate jobnets and jobs in non-cluster operation

When JP1/AJS3 - View is connected to multiple LANs, you can operate jobnets and jobs from JP1/AJS3 - Managers on the LANs. Such a system is shown below.

Figure 2-23 JP1/AJS3 - View connected to multiple LANs (connection to JP1/AJS3 - Managers)

The host hostX, where JP1/AJS3 - View is installed, is connected to multiple LANs. JP1/AJS3 - Manager is installed on each of these LANs.

In this system configuration, JP1/AJS3 - View on hostX can connect to the manager host host10 on the Management LAN, and to the manager hosts hostA and hostB on the Work task LAN to operate jobnets and jobs.

Regarding the communications settings at host10, hostA, and hostB, follow the example communications settings for non-cluster operation described in the Job Management Partner 1/Base User's Guide.

The host hostX requires an OS environment that can resolve the host names of host10, hostA, and hostB.

(2) Example connections and communications settings for cluster operation

The following describes example connections and communications settings for cluster operation in an environment where multiple LANs are connected (dissociated network). The explanations deal separately with cases where JP1/AJS3 - Manager is connected to multiple LANs and cases where JP1/AJS3 - Agent is connected to multiple LANs.

Supplementary note

The JP1/AJS3 Console functionality also supports the same kind of network configurations. These examples would also apply if you replaced JP1/AJS3 - View with JP1/AJS3 Console View, JP1/AJS3 - Manager with JP1/AJS3 Console Manager, and JP1/AJS3 - Agent with JP1/AJS3 Console Agent.

When you connect from JP1/AJS3 Console View to JP1/AJS3 Console Manager or from JP1/AJS3 Console Manager to JP1/AJS3 Console Agent, the operations are as follows depending on the bind communication method set for the receiving sides at the connection-destination hosts.

When there is a host with IP bind set for reception

The connections are made with the host that matches the IP address designated at the time of connection, regardless of whether it is a physical host or a logical host.

When ANY bind is set for reception at the physical host

A connection to the physical host is made only if the IP address cannot be resolved at any logical host.

(a) Cases where JP1/AJS3 - Manager is connected to multiple LANs in a cluster configuration

When JP1/AJS3 - Manager is connected to multiple LANs in a cluster configuration, you can connect JP1/AJS3 - Manager to JP1/AJS3 - Manager, JP1/AJS3 - Agent, or JP1/AJS3 - View on the LANs.

n Cluster system where JP1/AJS3 - Manager is connected to multiple LANs and linked to JP1/AJS3 - Agents on the LANs

In a cluster system where JP1/AJS3 - Manager is connected to multiple LANs, you can link the JP1/AJS3 - Manager with JP1/AJS3 - Agents on the LANs. In this configuration, you can execute jobs with the JP1/AJS3 - Agents from either the physical or logical host. Such a system is shown below.

Figure 2-24 JP1/AJS3 - Manager connected to multiple LANs for cluster operation (connection to JP1/AJS3 - Agents)

Here, the host hostX, where JP1/AJS3 - Manager is installed, is connected to multiple LANs and cluster operation is performed. JP1/AJS3 - Agent is installed on each of the LANs, and the agent hosts can be defined from either the physical host hostX, or the logical host hostL.

In this system configuration, hostX or HostL serves as the manager host and jobs can be executed at the agent host host10 on the Management LAN, and at the agent hosts HostA and hostB on the Work task LAN.

Regarding the communications settings at each host, follow the example communications settings for cluster operation in the Job Management Partner 1/Base User's Guide.

The hosts host10, hostA, and hostB require an OS environment that can resolve the host name of hostX.

n Cluster system where JP1/AJS3 - Manager is connected to multiple LANs and linked to JP1/AJS3 - View on the LANs

When JP1/AJS3 - Manager is connected to multiple LANs for cluster operation, you might be able to use the JP1/AJS3 - Manager with JP1/AJS3 - Views on the LANs. When JP1/AJS3 - Manager is working with JP1/AJS3 - Views on the LANs, from the JP1/AJS3 - Views, you can operate jobs and jobnets running on either the physical or logical host. Such a system is shown below.

Figure 2-25 Example of JP1/AJS3 - Manager connected to multiple LANs in a cluster system (connection with JP1/AJS3 - View)

Here, the host hostX, where JP1/AJS3 - Manager is installed, is connected to multiple LANs and cluster operation is performed. JP1/AJS3 - View is installed in each of the LANs.

In this system configuration, the physical host hostX or the logical host HostL serves as the manager host and jobs can be executed at the agent host host10 on the Management LAN, and at the agent hosts HostA and hostB on the Work task LAN.

Regarding the communications settings on each host, follow the example communications settings for cluster operation in the Job Management Partner 1/Base User's Guide.

host10, hostA, and hostB require an OS environment that can resolve the host name of hostX or hostL.

Cautionary note

JP1/AJS3 - View and JP1/AJS3 - Manager can be connected even if the JP1/AJS3 - Manager service has not started. Therefore, regardless of whether JP1/AJS3 service has started or not (for example, in an operation where the physical JP1/AJS3 service is not used), make connections under the following rules, governed by the hostX setting information:

When there is a host with IP bind set for reception

The connection is made with the host matching the IP address on login from JP1/AJS3 - View, regardless of whether it is the physical host or the logical host.

When ANY bind is set for reception at the physical host

A connection to the physical host is made only if the IP address cannot be resolved at any logical host.

n Cluster system where JP1/AJS3 - Manager is connected to multiple LANs and linked to JP1/AJS3 - Managers on the LANs

In a cluster system where JP1/AJS3 - Manager is connected to multiple LANs, you might be able to use JP1/AJS3 - Manager with other JP1/AJS3 - Managers on the LANs. When JP1/AJS3 - Manager is working with other JP1/AJS3 - Managers on the LANs, you can execute remote jobnets, and remotely execute scheduler commands on the physical or logical host. Such a system is shown below.

Figure 2-26 JP1/AJS3 - Manager connected to multiple LANs for cluster operation (connection to JP1/AJS3 - Managers)

Here, the host hostX, where JP1/AJS3 - Manager is installed, is connected to multiple LANs and cluster operation is performed. JP1/AJS3 - Manager is installed at each of the LANs.

In this system configuration, the physical host, hostX, or the logical host, hostL, serves as the manager host. Remote jobnets can be executed, and scheduler commands remotely executed, either from the manager host host10 on the Management LAN or from the host hostA or hostB on the Work task LAN.

Regarding the communications settings at hostX, follow the example settings for cluster operation in the Job Management Partner 1/Base User's Guide.

The hosts host10, hostA, and hostB require an OS environment that can resolve the host name of hostX or hostL.

Cautionary note

The same rules that apply to connections from JP1/AJS3 - View also apply to connections between JP1/AJS3 - Manager hosts when executing remote jobnets or remotely executing scheduler commands.

(b) Cases where JP1/AJS3 - Agent is connected to multiple LANs to execute jobs in a cluster configuration

In a cluster system where JP1/AJS3 - Agent is connected to multiple LANs to work with JP1/AJS3 - Managers on the LANs, from the JP1/AJS3 - Managers, jobs can be executed on the physical or logical host. Such a system is shown below.

Figure 2-27 JP1/AJS3 - Agent connected to multiple LANs for cluster operation (connection to JP1/AJS3 - Managers)

Here, the host hostX, where JP1/AJS3 - Manager is installed, is connected to multiple LANs for cluster operation. JP1/AJS3 - Manager is installed at each of these LANs, which can be defined as agent hosts in relation to the physical host hostX, or the logical host hostL.

In this system configuration, the physical host hostX, or the logical host hostL, serves as the agent host. Jobs can be executed either from the manager host host10 on the Management LAN or the manager host hostA or hostB on the Work task LAN.

Regarding the communications settings at each host, follow the example settings for cluster operation in the Job Management Partner 1/Base User's Guide.

The hosts host10, hostA, and hostB require an OS environment that can resolve the host name of hostX.

[Contents][Back][Next]

[Trademarks]