Introduction

BMC Remedy operates on a Software-as-a-Service (SaaS) delivery model that uses third-party cloud vendors to deliver services. BMC Remedy with OpsRamp is a one-way integration.

Install the Integration

  1. From All Clients, select a client.
  2. Go to Setup > Account.
  3. Select the Integrations and Apps tab.
  4. The Installed Integrations page, where all the installed applications are displayed. Note: If there are no installed applications, it will navigate to the Available Integrations and Apps page.
  5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
  6. Search for BMC Remedy using the search option available.
    Note: Alternatively, you can use the All Categories option to search.
  7. Click ADD on the BMC Remedy tile. The Inbound tab is displayed.

Configure the Integration

Based on your requirements, you can configure Inbound, Outbound or both.

Configure the Inbound (From BMC Remedy to OpsRamp)

BMC Remedy Inbound and Outbound configuration

To configure the inbound, follow these steps:

  • Authentication: Select OAUTH2 from the Authentication Type dropdown and click on Generate Key to generate the Key and Secret.
    Note: Keep a copy of the token as the information will not appear again. Read information about the Access Key.
  • Map Attributes: Map OpsRamp entity attributes with BMC Remedy attributes.
    1. Click +Add from the Map Attributes section.
    2. From the Add Map Attributes window, enter the below information:
      • OpsRamp Entity: Select the Opsramp entity from dropdown.
      • OpsRamp Property: Select the Opsramp property from dropdown. It will change based on entity selection.
      • BMC Remedy Entity: Enter the BMC Remedy entity.
      • BMC Remedy Property: Enter the BMC Remedy property.
    3. Click +Property Value in the Property Values section, and enter BMC Remedy Property Value and OpsRamp Property Value and click Save.
      Note:
      • The Property values section appears based on the OpsRamp Property selected.
      • To add property values, click +Property Value.
      • To map more attributes, click +Entity.
  • Properties:
    1. Click +Properties from the Properties section.
    2. Enter the values for the Properties and Value fields and click Save.
      Note: To add properties, click +Properties
    3. Click Add Map Attributes.
    4. Click Next. The Outbound tab is displayed.

Configure the Outbound (From OpsRamp to BMC Remedy)

BMC Remedy Inbound and Outbound configuration

To configure the outbound, follow these steps:

  • Configuration: The notification details to trigger integration events are displayed.
    1. Base URI: https://{subdomain}.com/arsys/services/ARService?server=onbmcremedy-s&webService=OpsRamp_CreateIncident
    2. Notification Type: Select the Notification Type. Available options are REST API and SOAP API.
    3. Authentication Type: Based on the Notification Type selected, the Authentication Type differs. Available options are Basic, OAuth2, JWT, None.
  • Map Attributes: From the Map Attributes window, enter the below information:
    1. OpsRamp Entity: Select the OpsRamp entity from dropdown.
    2. OpsRamp Property: Select the OpsRamp property from dropdown. It will change based on entity selection.
    3. BMC Remedy Entity: Enter the BMC Remedy entity.
    4. BMC Remedy Property: Enter the BMC Remedy property.
    5. Click +Property Value in the Property Values section, and enter BMC Remedy Property Value and OpsRamp Property Value and click Save.
      Note:
      • The Property values section appears based on the OpsRamp Property selected.
      • To add property values, click on +Property Value.
      • To map more attributes, click on +Entity.
    • Click Add Map Attributes .
  • Events: Events are for sending notifications when an action is performed on OpsRamp entities.
    1. Click Add in the Events section.
    2. Enter a name for the event.
    3. Select the Entity, Entity Type, and Entity Type Event from the drop-down lists.
    4. (Optional) Under Advanced Settings, enter the values for Property, Operator, and Value and click Save.
    5. From Actions: Select Use Parent Configuration checkbox to inherit parent configuration.
      1. Enter Endpoint URL.
      2. Select the Notification Type. Available options are REST API and SOAP API.
      3. Select the Authentication Type. Based on the Notification Type selected, the Authentication Type differs. Available options are Basic, OAuth2, JWT, None.
      4. Select the web method.
    6. Headers:
      1. Click +Add and enter/select the header name and value.
      2. Click Save to save the header name.
      • (Optional) Click +Add to add more _headers
      • Enter the Payload.
    7. Response:
      1. Click +Add and enter/select the response name and value.
      2. Click Save to save the response name.
      • (Optional) Click +Add to add more responses.
        Note:
        • The event is created, only if you provide the response properties.
        • You cannot enter more than four responses.
    8. (Optional) Attachment: In the Attachment section, provide inputs in the Process Type, Attachment Endpoint URL, and Web Method fields.
    9. Attachment Headers: In the Attachment Headers section, provide inputs in the Name and Value fields and click on Save.
      1. Enter the payload in the Attachment Payload box.
      2. Enter the Key and Value in the Attachment Response section.

    10. Click Add Event. The event is added.
      There are some actions you can perform on the Events.
      See here for more details.

Integration response mapping configuration

Response mapping configuration is mainly based on the response payload that is received in third party payload; below are a few examples for response mapping configuration:

  1. sample response payload to mapping the id in response mapping:
    {
"id":"INC0001",
"type":"incident",
"tool":"servicedesk"
}

    external ticket id = $id
    We need to append $ to the value

  2. sample response payload to mapping the id in response mapping:
    {
"result":{
"id":"INC0001",
"type":"incident",
"tool":"servicedesk"
    }
}

    external ticket id = $result.id

  3. Sample response payload to mapping the id in response mapping
    {
       "result":[
          {
             "ticketDetails":{
            "id":"INC0001",
            "type":"incident",
            "tool":"servicedesk"
      },
         "Description":{
            "display_value":"testing description",
            "value":"validating"
         }
      }
   ]
}

    external ticket id = $result[0].ticketDetails.id

  4. sample response payload to mapping the Incident Number in response mapping
        {
      "result": {
      "Incident Number": "INC0001",
      "type": "Incident"
      }
    }

    external ticket id = $result[‘Incident Number’]


  • Failures: In the case of failure in integration, an Email is sent to the user about the failure in integration.
    To configure failure notification:
    1. Click add from the Failures section.
    2. Select notification type as Email.
    3. Enter the email address(es) in the To and CC fields
    4. Click Add Failure Notifications. The details are added.
    5. Click Finish. The integration is installed.

Actions on Integration

You can perform actions on an integration.

  • See here for more information.

Actions on Event

Follow these steps to perform actions on the events:

  1. Click on the integration name.
  2. Navigate to Outbound tab > Events section.
  3. Hover over the event name.
  4. Click the actions (three dots) menu. A popup appears with options.
    • Copy Id: To copy an event Id.
    • Edit: To edit the event details.
    • Save as: To save an event name.
    • Validate: Validate if the event is successful.
      • Select Json or Form.
        • Json: Enter the payload and click on Validate.
        • Form: Enter the property and value in the fields and click on Validate.
          A green tick appears if the event is successful
    • Remove: To remove an event.

Audit Logs

View logs from the Audit Logs tab. You can view if the event was successful or not.

Integration event payloads

The following are the field and example payload to create incidents.

Create incident

FieldValue
Endpoint URLhttps://{subdomain}.com/arsys/services/ARService?server=onbmc-s&webService=OpsRamp_CreateIncident
Headers
  • Accept: application/xml
  • Content-Type: text/xml
  • SOAPAction: OpsRamp_CreateIncident
MethodPOST
Authentication typeBASIC
UsernameBMC Remedy username
PasswordBMC Remedy password

Request with OpsRamp tokens

The following is a sample request with OpsRamp tokens.

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:OpsRamp_CreateIncident">
     <soapenv:Body>
     <urn:Create_OpsRampIncidentNew>
     <!--Optional:-->
     <urn:Incident_Number></urn:Incident_Number>
     <urn:Summary>$incident.subject</urn:Summary>
     <urn:Notes>$incident.impact</urn:Notes>
     <urn:Priority>[@$incident.priority.name@]</urn:Priority>
     <urn:Vendor_Ticket_Number>$incident.uniqueId</urn:Vendor_Ticket_Number>
     <urn:OpsRamp_Status>[@$incident.status.name@]</urn:OpsRamp_Status>
     <urn:Source_Type>Inbound</urn:Source_Type>
     </urn:Create_OpsRampIncidentNew>
     </soapenv:Body>
    </soapenv:Envelope>

Response

The following is a sample response.

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <soapenv:Body>
     <ns0:Create_OpsRampIncidentNewResponse xmlns:ns0="urn:OpsRamp_CreateIncident">
     <ns0:Incident_Number>INC000003142691</ns0:Incident_Number>
     <ns0:OpsRamp_Status>Open</ns0:OpsRamp_Status>
     </ns0:Create_OpsRampIncidentNewResponse>
     </soapenv:Body>
    </soapenv:Envelope>

Use tag: $Body.createResponse.createResult.EntityResults.Entity.TicketNumber to read the BMC Remedy ticket ID and save it to the external entity ID of the OpsRamp incident.

Authentication error message

The following is a possible error message for an authentication error:

    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <soapenv:Body>
     <soapenv:Fault>
     <faultcode>soapenv:Server.userException</faultcode>
     <faultstring>ARERR [623] Authentication failed</faultstring>
     <detail>
     <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">dv-mt-01</ns1:hostname>
     </detail>
     </soapenv:Fault>
     </soapenv:Body>
    </soapenv:Envelope>

Required field error message

The following is a possible error message for a required field error:

    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <soapenv:Body>
     <soapenv:Fault>
     <faultcode>soapenv:Server.userException</faultcode>
     <faultstring>ERROR (326): Required field cannot be blank.; 536870914</faultstring>
     <detail>
     <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">dv-mt-01</ns1:hostname>
     </detail>
     </soapenv:Fault>
     </soapenv:Body>
    </soapenv:Envelope>