HCL Workload Automation, Version 9.4

A sample network agent definition

The following example shows how to define a network agent workstation for a remote network, Network A, that allows local network, Network B, to use jobs and job streams in the remote network as internetwork dependencies.
Figure 1. Local and remote networks
The diagram shows a network agent workstation that connects a local network, Network B, to a remote network, Network A.
Assuming that:
  • MasterA is the master domain manager of the remote network, Network A, and that:
    • tws_masterA is the TWS_user defined on MasterA.
    • The TCP port number for MasterA as 12345.
    • The node where MasterA is defined is MasterA.rome.tivoli.com.
  • MasterB is the master domain manager of the local network, Network B, and that:
    • tws_masterB is the TWS_user defined on MasterB.
    • The node where MasterB is defined is MasterB.rome.tivoli.com.
A network agent workstation named NetAgt, defined on MasterB to manage internetwork dependencies on jobs or job streams defined in Network A can be the following: 
CPUNAME NETAGT
  DESCRIPTION "NETWORK AGENT"
  OS OTHER
  NODE MASTERA.ROME.TIVOLI.COM
  TCPADDR 12345
  FOR maestro
    HOST MASTERB
    ACCESS netmth
END
Important: Write the network access name netmth in lowercase on case-sensitive operating systems.
The options file, netmth.opts defined on MasterB can be: 
GSuser=tws_masterB
GStimeout=600
Note: The network agent can be defined on either the master domain manager or a fault-tolerant agent.