Restarting the Harvest Broker

Products

• CA Harvest Software Change Manager
• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

There are a variety of reasons why you might want to restart the broker, such as

• If the Harvest database's DBMS has been restarted you should restart the broker accordingly
• If you make certain configuration changes to the hbroker.arg, hserver.arg, or other argument files, you will need to restart the broker for the change to take effect
• If working on an issue with the Broadcom Support Team they may request that you restart the broker

In any of these situations, what is the best method to restart the Harvest broker?

Environment

Harvest Software Change Manager all versions, operating systems, and DBMS's

Resolution

To restart the CA Harvest SCM broker, the procedure depends on your operating system.

Windows

On Windows, the Harvest components are typically managed as services:

1. Open the Services window (Navigate to Control Panel > Administrative Tools > Services).
2. Locate the CA Harvest SCM Broker service.
3. Right-click the service and select Restart.
   • Note: If you need to do a clean restart, select Stop, ensure all hserver.exe and rtserver.exe processes have terminated in Task Manager, and then select Start.

Linux/Unix

On Linux/Unix platforms, you manage the processes via the command line:

1. Log in as the user who owns the Harvest software.
2. Shut down the following processes in order:
   • bkrd (Broker)
   • All hserver processes
   • rtserver (Enterprise Communicator)
3. Restart the broker by executing the bkrd command. The broker is designed to automatically start the rtserver process.

Additional Information

Important Considerations

• Database Connectivity: If you are restarting because of a database interruption (e.g., Oracle restart), ensure the database is fully up and running before starting the SCM Broker and HServers.
• Logging: If you need to troubleshoot why a broker won't start, you can increase the HServer logging level to 5 by adding -logging=5 to the HServer.arg file before restarting.
• Environment Variables: On Linux/Unix, ensure the RTHOME environment variable is correctly set to the PEC installation folder in the .profile of the user starting the broker to avoid "Fatal Error Assertion" failures during startup.