Space banner This documentation supports the 18.05 version of Multi-Cloud Service Management.To view the documentation for the previous version, select 18.02 from the Product version menu.

Configuring connectors


connGliffy.png

A connector is an integration with a BMC application or a third-party application. Each BMC Helix Multi-Cloud Service Management feature requires a set of connectors to establish connections with Remedy ITSM and the ticket management systems. When setting up BMC Helix Multi-Cloud Service Management, as a tenant administrator, you must specify account and server details for the connectors. The following illustrations depicts examples of only some of the connectors for BMC Helix Multi-Cloud Service Management. 

ConnectorPosition.png

While the process for configuring connectors remains the same for all BMC Helix Multi-Cloud Service Management features, each connector needs some service-provider-specific information to be set up. For more information about connectors, see Connectors.

The connector configuration process is a part of the overall set up for BMC Helix Multi-Cloud Service Management. Complete all steps of the process when setting up Multi-Cloud Service Management for the first time. For Multi-Cloud Service Management features that you set up after the first-time configuration, you can reuse existing components and configure only those new components that you require. For more information, see Configuring Multi-Cloud Service Management.


Ensure that you have selected the features you want to enable and that BMC Helix Multi-Cloud Service Management displays a list of connectors you need for the selected features.

To configure a connector

  1. Click Configure the following connectors in Integration Studio.
    BMC Helix Multi-Cloud Service Management takes you to BMC Integration Studio to configure the connectors.

    connectorsList.PNG
  2. In Integration Studio, select a connector and click Configuration to enter the field values.
    You might need to click the arrow on the ribbon in the lower section of the screen to open the Configuration pane. For more information about configuration fields, see Connector configuration.
    If you need to integrate with multiple instances of Jira, click Add Connection Configuration to add configuration settings for all the Jira instances that you want to use.
  1. Click Save Configuration after you enter the appropriate values.

ConnectorConfigScreen.png

  1. After updating the configuration, click Accounts to add a user account.
    You might need to click the arrow on the ribbon in the lower section of the screen to open the Accounts pane. Refer to Connector configuration for more information about accounts.
    If you need to integrate with multiple instances of Jira, select the connector configuration for each of the Jira instances and add the appropriate account. 

    ConnectorAccountScreen.png

    Important: If you have multiple connector configurations, ensure that you associate them with the right account else the default configuration might get associated with the account.


Connector configuration

Connector

Features using the connector

Account

Configuration

Remedy ITSM


Incident brokering

  • Remedy Incident to AWS
  • Remedy Incident to Salesforce Service Cloud
  • Salesforce Service Cloud to Remedy Incident

DevOps integration

  • Manual association of Remedy Change with Jira Issues
  • Remedy Change to Jira Issue
  • Jira Issue to Remedy Change
  • Remedy Incident to Jira Issue
  • Jira Issue to Remedy Incident
  • Remedy Incident to Agile Central Issue

Service Dashboard

  • Service Dashboard
  • Service Notifications

Add the account of a Remedy ITSM user who has permissions to view business service requests, and update incidents and change requests.

If you are integrating with an on-premises instance of Remedy ITSM, enter the following:

Site - Select the site that you created for Remedy.

AR server - Enter the name of your on-premises BMC Acton Request System server.

AR server port - Enter the port number for your on-premises BMC Acton Request System server.

If you are using Remedy OnDemand, your Remedy ITSM connector configuration will be completed by BMC. It is recommended that you retain the configuration set up by BMC.


Multi-Cloud

Incident brokering

  • Remedy Incident to AWS
  • Remedy Incident to Salesforce Service Cloud
  • Salesforce Service Cloud to Remedy Incident

DevOps integration

  • Manual association of Remedy Change with Jira Issues
  • Remedy Change to Jira Issue
  • Jira Issue to Remedy Change
  • Remedy Incident to Jira Issue
  • Jira Issue to Remedy Incident
  • Remedy Incident to Agile Central Issue

Service Dashboard


    • Service Dashboard
    • Service Notifications

The account for this connector is set up by BMC during initial configuration.

Click reauthenticate.PNG to re-authenticate your account after you change the password for your tenant administrator account in Innovation Studio.

The Multi-Cloud connector configuration is completed by BMC. Retain the Multi-Cloud connector configuration as received out-of-the-box.

AWS

Remedy Incident to AWS

Ensure that you have an AWS access key before you set up your AWS connector. For more details, see AWS documenation.

Enter the following when you click Add Account:

  • AWS access key id
  • AWS access key secret

Not applicable.

Service Cloud

  • Remedy Incident to Salesforce Service Cloud
  • Salesforce Service Cloud to Remedy Incident

Add a Service Cloud user that has permission to view and update cases.

Not applicable.

JIRA

  • Manual association of Remedy Change with Jira Issues
  • Remedy Change to Jira Issue
  • Jira Issue to Remedy Change
  • Remedy Incident to Jira Issue
  • Jira Issue to Remedy Incident

Add the account of a JIRA user who can view and update Jira issues.

If you need to integrate with multiple JIRA instances, add an account for each of the Jira instances.

If you need to integrate with multiple instances of Jira, add a Connection Configuration configuration for each instance.

Name - Enter a name for the connector configuration

Site - For each on-premises Jira instance, select the site that you created.
For Jira instances in the cloud, select Cloud as the site.

Jira Server Hostname: Enter the name of your Jira server

Jira server Port: Enter the port number of the Jira server.

Protocol: Enter the protocol

CA Agile Central

Remedy Incident to Agile Central Issue


Not applicable.

SMTP Email

Incident brokering


    • Remedy Incident to AWS
    • Remedy Incident to Salesforce Service Cloud
    • Salesforce Service Cloud to Remedy Incident

DevOps integration

  • Manual association of Remedy Change with Jira Issues
  • Remedy Change to Jira Issue
  • Jira Issue to Remedy Change
  • Remedy Incident to Jira Issue
  • Jira Issue to Remedy Incident
  • Remedy Incident to Agile Central Issue
  • Service Dashboard


Add an email account that is to be used for sending error notifications.

Add details of the email server that is to be used for sending error notifications.

Name - Enter a name for the connector configuration.

Site - Select the appropriate site for your email server.

Connection type: Select the type of connection for your email server.

Incoming Email

  • Service Dashboard
  • Service Notifications

Provide details of the email account where you would like to receive service notifications.

Enter a Name for the configuration and specify a Site.

Where to go from here

Configuring-processes

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*