Reference of integration between xMatters and BMC Helix ITSM incidents by using BMC Helix iPaaS

You can integrate BMC Helix ITSM with Microsoft Azure DevOps to synchronize BMC Helix ITSM incidents with Azure DevOps work items. When a work item is created in Azure DevOps, a corresponding BMC Helix ITSM is created, and the converse is true. This integration enables your service desk agents to collaborate with developers who use Azure DevOps.

BMC Helix Multi-Cloud Broker, along with BMC Helix iPaaS, powered by Jitterbit provides the Sync_BMC_Helix_ITSM_incident_and_Microsoft_Azure_DevOps_work_item.json integration template that you can use to integrate BMC Helix ITSM with Azure DevOps. You configure the integration in BMC Helix Multi-Cloud Broker and deploy the integration template to your BMC Helix iPaaS environment.

List of project variables

The following sections describe the variables that you can update as per your requirements.

• BMC Helix iPaaS project variables

  Project variable	Value
  BHIP_API_Name	The default value of this variable is set to BMCHelixITSMIncidentAndxMattersEvent. If required, you can change the name.
  BHIP_API_User_Roles	Specify the organization roles that should have access to the new API. You can add multiple comma separated values. Important: If you do not specify any value, all the organization roles get access to the new API.
  BHIP_MCB_API_Profile_Username	The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker. Enter the user name that should be used while creating the BMC Helix Multi-Cloud Broker API profile.
  BHIP_MCB_API_Profile_Password	The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker. Enter the password that should be used while creating the BMC Helix Multi-Cloud Broker API profile.
  BHIP_Vendor_API_Profile_Type	The integration templates create APIs to accept requests from a vendor. Enter one of the following API authentication mechanisms that you want to use with this API: BASIC ANONYMOUS APIKEY
  BHIP_Vendor_API_Profile_Username	Enter the user name for the security profile that you want to use with the vendor API.  Important: Provide a value for this variable, only if you select the BASIC option in BHIP_Vendor_API_Profile_Type.
  BHIP_Vendor_API_Profile_Password	Enter the password for the security profile that you want to use with the vendor API.  Important: Provide a value for this variable, only if you select the BASIC option in BHIP_Vendor_API_Profile_Type.
  BHIP_Vendor_API_Profile_ApiKey_Name	Enter the APIKEY name for the security profile that you want to use with the vendor API.  Important: Provide a value for this variable, only if you select the APIKEY option in BHIP_Vendor_API_Profile_Type.
  BHIP_Host	Enter the BMC Helix iPaaS instance URL where you want to run this project.
  BHIP_Username	Enter the username for the BMC Helix iPaaS instance.
  BHIP_Password	Enter the password for the BMC Helix iPaaS instance.

• xMatters variables:

  Project variable	Value
  xMatters_Host_URL	Enter the xMatters instance URL where you want to run this project.
  xMatters_Username	Enter the user name to use to access xMatters.
  xMatters_Password	Enter the password for the xMatters user.
  xMatters_Form_Name	Enter the name of the xMatters form to be populated.
  xMatters_Trigger_Name	Enter the type of trigger used to define the purpose  of webhook, for example, Event Status Updates.
  xMatters_Integration	Enter Integrations. This is the name of the workflow defined for the outbound integration.
  xMatters_Workflow	Enter the name of the xMatters Workflow.

• BMC Helix Multi-Cloud Broker project variables:

  Project variable	Value
  MCB_Host	Enter the BMC Helix Multi-Cloud Broker host URL to which the xMatters events should be synchronized.
  MCSB_Username	Enter the user name that enables users to interact with BMC Helix Multi-Cloud Broker.
  MCB_Password	Enter the password for the provided user name.
  MCB_Vendor_Name	This variable is autopopulated. You must not change the default value.

  The following variables are inputs from BMC Helix ITSM. Either enter values for these variables or map appropriate xMatters fields if the data is available:

  Project variable	Value
  ITSM_Company_Name	Enter the company name for which the integration template needs to be run. For example, Calbro Services
  ITSM_Customer_First_Name	Enter the first name of the BMC Helix ITSM customer.
  ITSM_Customer_Last_Name	Enter the last name of the BMC Helix ITSM customer.
  ITSM_Incident_Type	Enter any of the following incident types that you want to create: User Service Restoration User Service Request Infrastructure Restoration Infrastructure Event Security Incident

Related topics

Getting started with BMC Helix Multi-Cloud Broker

Creating xMatters events for incidents via BMC Helix iPaaS, powered by Jitterbit