Configuring BMC-SA-Event_Orchestration_Service_Down module

This topic describes the steps to configure the BMC-SA-Event_Orchestration_Service_Down module and lists the configuration items included in the module.

Use this topic to understand the module configuration items and the configuration items that you must update to use the runbook. See the Update required column to understand whether to update the values.

To configure BMC-SA-Event_Orchestration_Service_Down

On the Grid Manager, click Manage > Modules and click the BMC-SA-Event_Orchestration_Service_Down module.
Expand the configuration tree until you can navigate to the configuration item that you want to modify.
Click the configuration item that you want to modify, edit the value, and click OK to save changes.
After successfully configuring the module, click the Modules tab and from the Modules in Repository list, select the module and click Activate. Module with the updated changes is successfully activated on the grid.

Use this table to understand the module configuration items and the configuration items that you must update to use the runbook.

Configuration item Description Values Update required

Service_Actions_Aliasing > Aliases

Contains the following elements:

<domain>: Contains the domain name for the servers, where the event is generated. Default domain is designated by a "*". If an event does not contain any information about the domain, the default "*" domain information is used to search for the host specific information.
<host>: Each domain can have one or more configuration related to hosts. Default value is "*". If the event contains a host name that does not have a specific section in the configuration, default host, "*" is used. Hosts are categorized by the OS type – Windows or Unix.
<commands>: Contains the <command>element, which specifies the commands required for the triage and remediation actions.
For the service down event, <commands>contain the command to start or stop a service. While performing triage to determine if a service is running on Windows, sc status <service name> command is used. While performing remediation to start the service, a net start <service name> command is used.

The attribute use-name-string shall be set to false for default services so that service name from the event is used as opposed to '*' while invoking commands.

<domains>
  <domain name="*">
    <hosts>
      <host os-type="windows" name="*">
        <services>
          <service name="*" use-name-string="false">
            <start>
              <command>net start</command>
            </start>
            <stop>
              <command>net stop</command>
            </stop>
            <restart>
              <commands>
                <command>net stop</command>
                <command>net start</command>
              </commands>
            </restart>
          </service>
        </services>
      </host>
      <host os-type="unix" name="*">
        <services>
          <service name="repo">
            <search-string>/opt/bmc/BAO/REPO/jvm/bin/java</search-string>
            <start>
              <command>nohup /opt/bmc/BAO/REPO/bin/server.sh start</command>
            </start>
            <stop>
              <command>nohup /opt/bmc/BAO/REPO/bin/server.sh stop -force</command>
            </stop>
            <restart>
              <commands>
                <command>nohup /opt/bmc/BAO/REPO/bin/server.sh stop -force  </command>
                <command>nohup /opt/bmc/BAO/REPO/bin/server.sh start  </command>
              </commands>
            </restart>
          </service>
          <service name="cdp">
            <search-string>/opt/bmc/BAO/CDP/jvm/bin/java</search-string>
            <start>
              <command>nohup /opt/bmc/BAO/CDP/bin/server.sh start</command>
            </start>
            <stop>
              <command>nohup /opt/bmc/BAO/CDP/bin/server.sh stop -force</command>
            </stop>
            <restart>
              <commands>
                <command>nohup /opt/bmc/BAO/CDP/bin/server.sh stop -force</command>
                <command>nohup /opt/bmc/BAO/CDP/bin/server.sh start</command>
              </commands>
            </restart>
          </service>
          <service name="*" use-name-string="false">
            <start>
              <command>service</command>
            </start>
            <stop>
              <command>service</command>
            </stop>
            <restart>
              <commands>
                <command>service</command>
                <command>service</command>
              </commands>
            </restart>
          </service>
        </services>
      </host>
    </hosts>
  </domain>
  <domain name="acme.com">
    <hosts>
      <host os-type="windows" name="*">
        <services>
          <service name="*" use-name-string="false">
            <start>
              <command>net start</command>
            </start>
            <stop>
              <command>net stop</command>
            </stop>
            <restart>
              <commands>
                <command>net stop</command>
                <command>net start</command>
              </commands>
            </restart>
          </service>
        </services>
      </host>
      <host os-type="windows" name="w1">
        <services>
          <service name="*" use-name-string="false">
            <start>
              <command>net start</command>
            </start>
            <stop>
              <command>net stop</command>
            </stop>
            <restart>
              <commands>
                <command>net stop</command>
                <command>net start</command>
              </commands>
            </restart>
          </service>
        </services>
      </host>
      <host os-type="unix" name="*">
        <services>
          <service name="repo">
            <search-string>/opt/bmc/BAO/REPO/jvm/bin/java</search-string>
            <start>
              <command>nohup /opt/bmc/BAO/REPO/bin/server.sh start  </command>
            </start>
            <stop>
              <command>nohup /opt/bmc/BAO/REPO/bin/server.sh stop -force  </command>
            </stop>
            <restart>
              <commands>
                <command>nohup /opt/bmc/BAO/REPO/bin/server.sh stop -force  </command>
                <command>nohup /opt/bmc/BAO/REPO/bin/server.sh start  </command>
              </commands>
            </restart>
          </service>
          <service name="cdp">
            <search-string>nohup /opt/bmc/BAO/CDP/jvm/bin/java</search-string>
            <start>
              <command>nohup /opt/bmc/BAO/CDP/bin/server.sh start</command>
            </start>
            <stop>
              <command>nohup /opt/bmc/BAO/CDP/bin/server.sh stop -force</command>
            </stop>
            <restart>
              <commands>
                <command>nohup /opt/bmc/BAO/CDP/bin/server.sh stop -force</command>
                <command>nohup /opt/bmc/BAO/CDP/bin/server.sh start</command>
              </commands>
            </restart>
          </service>
        </services>
      </host>
    </hosts>
  </domain>
</domains>

No

Service_Actions_Aliasing > ServiceNameMappings

Contains the mapping for BladeApp Server service so that the service name in the event is accurately mapped with the actual service name to start the service.

<service-name-mappings>
  <service-name name="BladeAppServer">BladeApp Server</service-name>
</service-name-mappings>

No

Configuring BMC-SA-Event_Orchestration_Service_Down module

To configure BMC-SA-Event_Orchestration_Service_Down

Comments