Running processes remotely

If you want Network Manager processes on one server to be managed by ncp_ctrl on another server, you must configure both instances of ncp_ctrl.

1. Install Network Manager on both servers.
2. Configure Really Small Message Broker to allow communication between the master server and slave server.
3. On the master server, configure the CtrlServices.DOMAIN.cfg file.
   1. Back up and edit the CtrlServices.DOMAIN.cfg file.
   2. For each process that you want to run on the remote server, set the hostName parameter to the host name of the remote server. Make sure the host name is the name as defined on the remote server.

   The following example configures the ncp_store process to run on the remote server called example.com in domain TARA.

   insert into services.inTray
   (
       serviceName,
       binaryName,
       servicePath,
       domainName,
       hostName,
       argList,
       retryCount
   )
   values
   (
       "ncp_store",
       "ncp_store",
       "/opt/IBM/netcool/core/precision/platform/linux2x86/bin",
       "TARA",
       "example.com",
       [ "-domain" , "<DOMAIN>" , "-latency" , "100000", "-debug", "0" ],
       5
   );
   

4. On the remote server, ensure that the CtrlServices.DOMAIN.cfg file is empty of content. Then, start the ncp_ctrl process on the remote server in slave mode.
   The following example starts the ncp_ctrl process in slave mode in the TARA domain .

   ncp_ctrl -domain TARA -slave

5. Start the ncp_ctrl process on the local server in master mode using the normal command line options. The following example starts the ncp_ctrl process in master mode domain TARA.

   ncp_ctrl -domain TARA