D.3 JP1/AJS3 - View communication settings
The following describes example connections and communications settings when JP1/AJS3 - View is used in an environment where multiple LANs are connected (dissociated network).
- Supplementary note
-
When the JP1/AJS3 Console functionality is used, the same network configuration is supported. In this case, 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) Case where JP1/AJS3 - View is connected to multiple LANs to operate units
When JP1/AJS3 - View is connected to multiple LANs, you can operate units from the JP1/AJS3 - Managers on all connected LANs.
The following figure shows an example when JP1/AJS3 - View is connected to multiple LANs to operate units from JP1/AJS3 - Managers.
|
|
![[Figure]](GRAPHICS/ZH020110.GIF)
hostX, on which JP1/AJS3 - View is installed, is connected to multiple LANs. JP1/AJS3 - Manager is installed on each host connected to each LAN.
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 units.
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.
Note that hostX requires an OS environment capable of resolving the host names of host10, hostA, and hostB to IP addresses. Because JP1/AJS3 - View does not apply the settings in the jp1hosts file or the jp1hosts2 file, set the hosts file or DNS server so that the host names can be resolved.