Documentation
DocumentationDeveloperAcademyCommunitySupportLogin
Start typing to search…

BMC Remedy/Helix Access Requirements

What is this account used for:

To integrate with BMC Remedy, Moveworks leverages the BMC Platform REST API.

To authenticate to this API, Moveworks BMC Connector requries a service account along with its username and password.

Moveworks interacts with your BMC Remedy System for actions such as:

  • Monitor tickets for autonomous resolution
  • Reach out to an employee when a BMC Remedy ticket needs the employee's attention
  • Create tickets to log issues the bot has resolved autonomously
  • Create tickets for issues that require an agent's attention
  • Triage incoming tickets
  • Read knowledge base articles, so that the bot can serve them to employees
  • Read the BMC Remedy user table so that the bot can log and assign issues appropriately.

Outlined below are the BMC interface forms and REST API interfaces required to read and write to BMC Remedy that the bot service account will need access to, as well as reasons for the access.

Required Access for ITSM Integration/ Core Ticketing & Ticket Notifications:

  1. HPD.IncidentInterface - Get Incident Details
  2. HPD.IncidentInterface_Create - Create Incident
  3. HPD.WorkLog - Update Ticket Work notes
  4. SRM.WorkLog - Update REQ Ticket Work notes
  5. SRM.RequestInterface - Get Request Details
  6. SRD:ServiceRequestDefinition_Base - Get Request Schema Definitions
  7. CTM:People - Get User Information

Required Access for Knowledge Search:

  1. RKM:KnowledgeArticleManager - Get Knowledge article metadata
  2. RKM:HowToTemplate - Get HowToTemplate Article Body Content
  3. RKM:KnownErrorTemplate - Get KnownErrorTemplate Article Body Content
  4. RKM:ProblemSolutionTemplate - Get ProblemSolutionTemplate Article Body Content
  5. RKM:ReferenceTemplate - Get ReferenceTemplate Article Body Content

How does authentication work?

When Moveworks authenticates with BMC over HTTPS port 443, BMC verifies that the credentials are valid, the AR Server generates a JSON Web Token (JWT).

Moveworks then uses the JWT in subsequent API calls, and regenerates it every 55 minutes.

Authentication Example:

TOKEN_RESPONSE=$(curl -s -X POST "${REMEDY_SERVER}/api/jwt/login" 
-H "Content-Type: application/x-www-form-urlencoded" 
-d "username=${USERNAME}" 
-d "password=${PASSWORD}")

Connector Configuration (step-by-step)

  1. Navigate to the Connectors module in your Moveworks Setup by selecting Built-in Connectors. You can find this under Core Platform section.
  2. On the top right, Click Create New.
  3. Search for and select the BMC Remedy (includes Remedy Helix) connector.

  1. Name the connection and choose the Common Base URL option.
  2. Input the URL for your BMC instance.
  3. Select BMC Remedy AR Auth
  4. Input the Username and password of your BMC Service account.

References

BMC Documentation: https://docs.bmc.com/xwiki/bin/view/Service-Management/IT-Service-Management/BMC-Helix-ITSM/itsm253/Developing/Integrating-third-party-applications-with-BMC-Helix-ITSM-by-using-the-platform-REST-API/Overview-of-the-platform-REST-API/

Updated 7 days ago