Configuring DSO to work with BMC Service Level Management
Perform the the following steps to configure DSO to work with BMC Service Level Management:
Step | Description |
---|---|
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
Uncomment the following Distributed Server Option entry in the armonitor configuration file:
Platform
Java server
Windows or UNIX
ardsojversionNumber_buildNumber.jar
By default, the armonitorconfiguration file is in this location:
- (UNIX) /etc/arsystem/serverName/armonitor.conf
- (Windows) ARSystemServerInstallDir\Conf\armonitor.cfg
- Restart the AR System server.
For more information, see Enabling DSO on an AR System server 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 in the Action Request System online documentation.
To synchronize all forms
- 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.
- 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.
- 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.
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.
- 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 in the Action Request System online documentation.