D.1 Example of connections and communication 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 and JP1/AJS3 - Agent are connected to multiple LANs.
When the JP1/AJS3 Console functionality is used, replace 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.
- Organization of this subsection
(1) Cases where JP1/AJS3 - Manager is connected to multiple LANs for non-cluster operation
When JP1/AJS3 - Manager is connected to multiple LANs, JP1/AJS3 can be connected to JP1/AJS3 - Agent, JP1/AJS3 - View, or JP1/AJS3 - Manager on all the connected LANs. The hosts require an OS environment in which they can mutually resolve the host name.
(a) Case where JP1/AJS3 - Manager is connected to multiple LANs and linked to their JP1/AJS3 - Agents
When JP1/AJS3 - Manager is connected to multiple LANs, jobs can be executed in the JP1/AJS3 - Agents on multiple LANs. The following figure shows an example when JP1/AJS3 - Manager is connected to multiple LANs to execute jobs in JP1/AJS3 - Agents on the LANs.
|
|
![[Figure]](GRAPHICS/ZH020090.GIF)
hostX, on which JP1/AJS3 - Manager is installed, is connected to multiple LANs. JP1/AJS3 - Agent is installed on the host connected to each LAN.
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.
(b) Case where JP1/AJS3 - Manager is connected to multiple LANs and linked to their JP1/AJS3 - Views
When JP1/AJS3 - Manager is connected to multiple LANs, units can be operated from JP1/AJS3 - Views on multiple LANs. The following figure shows an example when JP1/AJS3 - Manager is connected to multiple LANs to operate units from the JP1/AJS3 - Views.
|
|
![[Figure]](GRAPHICS/ZH020095.GIF)
hostX, on which JP1/AJS3 - Manager is installed, is connected to multiple LANs. JP1/AJS3 - View is installed on each host connected to each LAN.
In this system configuration, units 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.
(c) Case where JP1/AJS3 - Manager is connected to multiple LANs and linked to their JP1/AJS3 - Managers
When JP1/AJS3 - Manager is connected to multiple LANs, you can execute remote jobnets and remotely execute commands in the JP1/AJS3 - Managers on multiple LANs.
The following figure shows an example when JP1/AJS3 - Manager is connected to multiple LANs to execute remote jobnets on or remotely execute commands on JP1/AJS3 - Managers.
|
|
![[Figure]](GRAPHICS/ZH020100.GIF)
hostX, on which JP1/AJS3 - Manager is installed, is connected to multiple LANs. JP1/AJS3 - Manager is installed on each host connected to each LAN.
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 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.
(2) Case where JP1/AJS3 - Agent is connected to multiple LANs for executing jobs for non-cluster operation
When JP1/AJS3 - Agent is connected to multiple LANs, you can execute jobs from the JP1/AJS3 - Managers on all connected LANs. The hosts require an OS environment in which they can mutually resolve the host name.
The following figure shows an example when JP1/AJS3 - Agent is connected to multiple LANs to execute jobs from the JP1/AJS3 - Manager on each LAN.
|
|
![[Figure]](GRAPHICS/ZH020105.GIF)
hostX, on which JP1/AJS3 - Agent is installed, is connected to multiple LANs. JP1/AJS3 - Manager is installed on each host connected to each LAN.
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.
(3) Cautionary note
When you specify IP binding as the receive setting for hostX on which JP1/AJS3 - Manager or JP1/AJS3 - Agent is installed, you need to specify both the IP address of the management LAN and the IP address of the work task LAN in jp1hosts or jp1hosts2 on hostX. If you do not, communication between hosts might not be performed as intended. For example, if only the IP address of the management LAN is written in jp1hosts or jp1hosts2 on hostX, communication from the work task LAN (hostA and hostB) to hostX might result in an error.