Unlinking and stopping HCL Workload Automation

About this task

Before you perform an upgrade or uninstall, install a fix pack, or perform maintenance activities, ensure that all HCL Workload Automation processes and services are stopped. Follow these steps:


  1. If you have jobs that are currently running on the workstation, wait for them to finish. To determine which are not finished, check for jobs that are in the exec state. When there are no jobs in this state, and you have allowed sufficient time for all events to be distributed in your network, you can continue with the rest of the procedure.
  2. If the workstation that you want to stop is not the master domain manager, unlink the workstation by issuing the following command from the command line of the master domain manager:
    conman "unlink workstationname;noask"
  3. Stop WebSphere Application Server Liberty Base by using the conman stopappserver command (see Starting and stopping the application server and appservman).
  4. All HCL Workload Automation processes on the workstation must then be stopped manually. From the command line, while logged on as the <TWS_user>, enter the following command:
    conman “stop;wait”
  5. From the command line, stop the netman process as follows:
    Run the conman “shut" command.
    Note: Do not use the UNIX® kill command to stop HCL Workload Automation processes.
    From the HCL Workload Automation home directory, run the shutdown.cmd command.
  6. To stop dynamic agents, run the ShutDownLwa command.
  7. To stop the SSM agent, perform the following steps:
    • On Windows®, stop the service HCL Workload Automation SSM Agent (for <TWS_user>).
    • On UNIX®, run the stopmon command.

What to do next

To verify if there are services and processes still running:
Enter the command: ps -u <TWS_user>Verify that the following processes are not running: netman, mailman, batchman, writer, jobman, JOBMAN, stageman, logman, planman, monman, ssmagent.bin, and appservman.
Run Task Manager, and verify that the following processes are not running: netman, mailman, batchman, writer, jobman, stageman, JOBMON, tokensrv, batchup, logman, planman, monman, ssmagent, and appservman.

Also, ensure that no system programs are accessing the directory or its sub-directories, including the command prompt and Windows® Explorer.