Skip to Content
Information
This documentation supports the 20.02 version of BMC Service Level Management. To view an earlier version, select the version from the Product version menu.

DSO and actions

The following items describe how to work various types of actions.

Related topics

Administering
Working-with-BMC-SLM-in-a-distributed-environment

  • If you are running BMC Service Level Management on two servers and data is shared between them, the escalation triggers actions stored in the SLM:EventSchedule form on both servers. As a result, you see two sets of actions. If you disable the escalation on one of the servers, only one set of actions will trigger.
  • When you copy a record, it triggers workflow that is set to execute on Merge. In SLM-generated workflow, filters named zSLMGe do not execute on Merge, therefore the same SLM workflow must exist on all servers. Even though SLM measurement information is copied across the servers, only one server triggers the milestones stored in the SLM:EventSchedule form.
Warning

Important

You must disable the escalation SLM:EventSchedule:TAD_Polling Escalation on the other servers. The only exception is for milestones that are not time-dependent and trigger on a user-defined qualification. These milestones do not execute on Merge and will trigger on the server where the request is updated.

  • When setting up an agreement or service target with a notification action for a milestone, add the qualification AND $\USER$ != "Distributed Server " to the Execute If field on the milestone to prevent multiple notifications.
  • DSO transfers perform Modify operations in some cases. To avoid problems, modify the filter SLA:Shared:Check for License 01 by adding AND $USER$ != "Distributed Server " to the Run If qualification.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Service Level Management 20.02