BMC Remedy server integration artifacts
This topic contains the BMC Remedy artifacts installed by the BMC Atrium Orchestrator content installer program for the Continuous Compliance for Network Automation solution.
BMC Remedy administrator workflow objects
The following table lists the BMC Remedy administrator workflow objects for this solution.
Remedy administrator workflow object | Type | Description |
---|---|---|
INT:BCAN:TMS:EnableLaunchButton | Active Link | If LaunchCommand = TMS_OUT_BCAN (that is, Network Task template), keeps the Launch button enabled after the Task has Closed so that the Job Details can still be viewed. |
INT:BCAN:TMS:Launch | Active Link | If LaunchCommand = TMS_OUT_BCAN (that is, Network Task template), launches into the Job Details when the Task Launch button is clicked. |
INT:BCAN:TMS:LaunchConflictResolution | Active Link | If LaunchCommand = TMS_OUT_BCAN (that is, Network Task template), launches into the Job Details when Task Launch button is clicked. |
INT:BCAN:TMS:MultiSiteUpdate | Active Link | When the Task Save button is selected, displays the BMC Network Automation Application Registry selection if the Task.Character 02 field is empty. This enables Change requests that originate at Remedy to be directed to a specific BMC Network Automation application server when multiple application servers are deployed. |
INT:BCAN:CHG:ApprovalNotification | Filter | Filter used by BMC Atrium Orchestrator to receive Remedy approval/rejection notifications for change requests submitted by BMC Network Automation. |
INT:BCAN:TMS:UpdateServerFromCAI | Filter | Updates the Task.Character 02 field with BMC Network Automation application server information when a single Application Registry exists. Leaves the field empty if multiple BMC Network Automation Application Registries are found as user will select a server when the Task is saved. |
INT:BCAN:CMDBFederatedInterfaceUpdate | Filter | Updates the FederationAccessString (URL) with server information from the BMC Network Automation Application Registry to support Federated report launching. |
BMC Remedy user objects
The following table lists the Remedy user objects for this solution.
Remedy user object | Object name(s) | Description |
---|---|---|
CAI Application Registry | BMC Network Automation | Registers BMC Network Automation and defines the application server connectivity information. |
Commands | TMS_OUT_BCAN | Command assigned to the Network Task Launch button. Enables the Remedy user to display the Jobs associated with a Change ticket by Task when approving and verifying configuration changes. |
Change Template | Network Change | The Change Template used by BMC Network Automation to create a Change ticket. |
Task Template | Network Task | The Task Template assigned to Change tickets for network configuration changes. There is a one-to-one mapping of a Network Task to a Job. |
Incident Template | Network Incident | The Incident Template used by BMC Network Automation to create an Incident ticket. |
BMC.CORE.CONFIG:BMC_FederatedProductLink | BMC Network Automation | Provides the Owner Product name that appears on the Federated Interfaces page. |
BMC.CORE.CONFIG:BMC_FederatedProduct | BMC Network Automation | Defines BMC Network Automation as a federated product. |
BMC.CORE.CONFIG:BMC_FederatedInterface | View Change History, View Compliance Summary, View Device Inventory Report, View Device Discrepancy Report, View Detailed Configuration | The federated report launches for network CIs. |
BMC.CORE.CONFIG:BMC_FederatedInterfaceLink | Links network CIs to the federated report launches. The links are qualified to only display in the CI Relationship Viewer for network devices. |
Remedy ITSM task, change and incident templates
BMC Network Automation relies on templates named Network Change, Network Incident, and Network Task. These templates are installed as part of the BMC Atrium Orchestrator Content installer when Continuous Compliance for Network Automation is selected.
If you choose not to follow the template naming convention, you must see Changing BMC Atrium Orchestrator Workflow Defaults for additional setup instructions.
- The Support Group assigned to the BMC Atrium Orchestrator Remedy user account named orchestrationuser must match the Authoring Group assigned to the Network Change and Network Incident templates. The default is Change Management. See the following diagram.
- The Assignee Group in the Network Task template must match the group assigned in the BMC Atrium Orchestrator Task query. The Task query populates the Remedy Inbox with Incident related Changes and Remedy initiated Changes pending service by BMC Network Automation users.
The default Assignee Group is Change Management. Most likely you will define a unique Assignee Group for BMC Network Automation (for example, Network Engineering). If you elect to change the Assignee Group, you must see Changing BMC Atrium Orchestrator Workflow Defaults for additional setup instructions.
Comments
Log in or register to comment.