Configure a Standby SAM

To configure a Standby SAM:

1. For the Standby SAM with Notification Cache Publishing only, use sm_edit to open the <BASEDIR>/smarts/bin/local/runcmd_env.sh file and add the environment variables listed in Environment variables specified for Host B in the runcmd_env.sh file.

Table 1. Environment variables specified for Host B in the runcmd_env.sh file

Environment variable	Description
SM_TOMCAT_SERVER	Is the name of the host where Smarts EDAA is running which is the same host as SAM with Notification Cache Publishing. For example: SM_TOMCAT_SERVER=http://<smarts_tomcat_hostname>:8080

1. Install the service for the Standby SAM on a Standby server (host B).

   • For the Standby SAM without Notification Cache Publishing, use the sm_service install command provided in step 3 in the “Configure an Active SAM” on page 27.

     • For the Standby SAM with Notification Cache Publishing, specify host B for the --edaa option. For example:

       ./sm_service install --force  --unmanaged  --startmode=runonce 
       --name=ic-sam-server-pres 
       --description=”EMC Smarts Service Assurance Manager Server (notification cache publishing)” 
       /<BASEDIR>/SAM/smarts/bin/sm_server 
       -n INCHARGE-SA-PRES 
       --config=ics 
       --port=1751
       --edaa=sam-presentation/2.0
       --bootstrap=bootstrap-amqp.conf
       --ignore-restore-errors
       --output
       --noregister

2. For Standby SAM with Notification Cache Publishing only, if you did not install the services for smarts-tomcat, smarts-rabbitmq, and smarts-elasticsearch during the SAM installation, you need to manually install them. The Domain Managers Installation Guide describes how to manually install these services.

3. Start the Standby SAM service in Start the services for SAM, Adapter Platform, and BIM.

   For Standby SAM with Notification Cache Publishing, in addition to the SAM service, you need to start the services for smarts-tomcat, smarts-rabbitmq, and smarts-elasticsearch.

   At this point, additional manual configuration is no longer required.

   • Later, after you modify the failover.conf file and run the sm_configureFailover.pl script, the script automatically creates all necessary subscriptions to the counterparts.

   • Later, when you run the manual backup, the Failover Manager adds the underlying source Domain Managers from the Active location to the Standby location.