This documentation supports the 21.3 version of BMC Service Level Management.

To view an earlier version, select the version from the Product version menu.

Configuring DSO to work with BMC Service Level Management

Perform the the following steps to configure DSO to work with BMC Service Level Management:


Enable DSO on an AR System server

You must first enable DSO on a AR System server. For more information, see To enable DSO on an Action Request System server.

Add filters

To operate in the DSO environment, the Service Level Management forms requires some filters. For more information, see Forms that require filters for a DSO environment.

Synchronize all forms DSO enables you to transfer requests between servers. Synchronize all forms to keep copies of a request synchronized across multiple servers. For more information, see To synchronize all forms

To enable DSO on a AR System server

  1. Uncomment the following Distributed Server Option  entry in the armonitor configuration file:


    Java server

    Windows or UNIX


    By default, the armonitorconfiguration file is in this location:

    • (UNIX/etc/arsystem/serverName/armonitor.conf
    • (WindowsARSystemServerInstallDir\Conf\armonitor.cfg
  2. Restart the AR System server.

For more information, see  Enabling DSO on an AR System server Open link in the Action Request System online documentation.

Forms that require filters for a DSO environment

To operate in the DSO environment, the following Service Level Management forms require filters:

  • CTR:ContractBase
  • SLM:Association
  • SLM:Attachment
  • SLM:Category
  • SLM:CongfigDataSource
  • SLM:CongfigGoalType
  • SLM:CongfigPreferences
  • SLM:CongfigReviewPeriod
  • SLM:CongfigSLAGroup
  • SLM:CongfigSLAOwners
  • SLM:CongfigSLMComments
  • SLM:EventSchedule
  • SLM:GoalSchedule
  • SLM:Measurement
  • SLM:MeasurementChild
  • SLM:MeasurementCriteria
  • SLM:Milestone
  • SLM:PenaltyRewards
  • SLM:Object
  • SLM:Registerservice targetID
  • SLM:RegisterSLAID
  • SLM:RuleAction
  • SLM:RuleActionAlertDlg
  • SLM:RuleActionComponent
  • SLM:RuleActionProcess
  • SLM:RuleActionProcess_base
  • SLM:RuleActionSequence
  • SLM:RuleActionSetValue
  • SLM:RuleActionSetValueDlg
  • SLM:RuleActionSetValue_base
  • SLM:RuleActionSetValueItem
  • SLM:RuleCondition
  • SLM:ServiceTarget
  • SLM:SLAAssociation
  • SLM:SLADefinition
  • SLM:UDA_AttachmentAssociations

For more information on creating filters, see  Creating filters Open link  in the Action Request System online documentation.

To synchronize all forms

  1. Add a different default value between 1 and 5 characters in the Entry ID field on each form, located on each server. This ensures that there are no entry ID conflicts between the servers.
  2. For each form, create a DSO mapping on every server that maps the form from the current server to the corresponding form on the remote server.
  3. Use Match by Entry IDs to map all fields.
    • In the Transfer Mode field, select Independent Copy.
    • In the Duplicate Request ID Action fields, select Overwrite.
  4. Using the mappings created, create a filter that fires on both Submit and Modifyand attach it to each form that performs a DSO Distributed-Transfer.


    You can also trigger on Merge. Make sure to include the Run If qualification $USER$ != "Distributed Server " to prevent an infinite loop and to transfer updates back and forth between the systems.

  5. Create a filter that triggers on Delete and attach it to each of these forms that perform a DSO Distributed-Delete to the corresponding remote form. This is used when a service target or an agreement is deleted or when a Service Level Management measurement record is replaced in an Service Level Management Group. The operations synchronize the forms on all the servers. A Service Level Management definition created on one AR System server is copied to the DSO-specified destination server. You must open the service target or agreement and click Save so the zSLMGen filters are generated by the local Service Level Management engine. If you are connected to any of the servers, you can submit a request that triggers one set of actions.

For more information, see  Setting up DSO to synchronize data across multiple AR System servers Open link  in the Action Request System online documentation.

Was this page helpful? Yes No Submitting... Thank you