Best practices when trying to restart EM in APM Cluster

Products

• CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Is there any advice to take into account when trying to restart the EM on the MOM?

Is a common procedure or do we have to avoid it as much as possible because it can cause problems?

 

 

Environment

Release : 10.7.0

Component :EM

Cause

Documentation: Best Practice of starting / restarting of MOM and Collectors. 

Resolution

 

 Recommendations:

 

a) Use the available startup script

 

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/administrating/configure-enterprise-manager/start-or-stop-the-enterprise-manager.html#concept.dita_d194ce413da05973c6db187b4ea5b9ed8c39329e_ManagetheEnterpriseManagerUsingControlScriptsonUNIX

 

b) Allow the EM to gracefully stop. 

DO NOT try to stop and start the EMs (MOM and Collectors) immediately as the Java process can still be running.

It could end with 2 process running and 2nd reporting messages such as "port in use" and potentially a smartstor data corruption.

 

After running ./EMCtl stop, check that and ensure the java process is not running, you can also use ./EMCtl.sh status

 

c) It is always recommended to start the Collectors before the MOM to avoid overloading MOM, but there is also a risk of overloading Collector that were started first if the Agents were not restarted.

As a best practice, you should start all Collectors at the same time and then the MOM.