Information
This documentation supports the 22.1 and consecutive patch versions of BMC Helix Multi-Cloud Broker.To view an earlier version, select the version from the Product version menu.

Common connector content


Introduction

 A connector configuration contains information about the third-party system such as the protocol, server host name, server port, and account details.

Configuration procedure

Excerpt Name: ConnectorConfigProcess

Click here to expand...

For each feature you selected, complete the following procedure for the connectors listed on the Configuration Links page.

  1. To navigate to BMC Helix Integration Service, on the Configuration Links page, click Configure connectors in Integration Studio under Required Common Configurations.
    You must configure the connectors listed for each feature, in addition to the connectors listed under Required Common Configuration.
  2. To enter field values, select a connector, such as ITSM, and click Configuration.
    You might need to click the arrow on the ribbon in the lower section of the screen to open the Configuration pane.
  3. To update the configuration defaults, enter the appropriate field values by referring to the list of connectors at the end of this procedure.
  4. To add or update the user account that is used to access the vendor application, click Accounts.

Common connectors

ITSM

Excerpt Name: ITSM connector

Click here to expand...
  • Configuration
    If you are integrating BMC Helix Multi-Cloud Broker with an on-premises instance of ITSM, enter the following values:

    Field

    Value

    Site

    Select the site that you created for Remedy.

    AR server

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

    AR server port

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

  • Account
    Add a ITSM user account that has permissions to view business service requests and permissions to update incidents, change, or problem requests.

Multi-Cloud

Excerpt Name: Multi-Cloud connector

Click here to expand...
  • Configuration
    While activating BMC Helix Multi-Cloud Broker, BMC configures the Multi-Cloud connector. Do not modify the default Multi-Cloud connector configuration.
  • Account
    BMC sets up the account for the Multi-Cloud connector.
    Click reauthenticate.PNGto re-authenticate after you have changed the password for your tenant administrator user account in BMC Helix Innovation Studio.
    For information about changing the user password, see Creating or modifying People data.

SMTP Email

Excerpt Name: SMTP Email connector

Click here to expand...
  • Configuration
    To send email notifications for errors, specify values for the following fields:

    Field

    Value

    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.

  • Account
    Add an email account to be used for sending error notifications.


AWS

Excerpt name: awsConnector

Click here to expand...
  • Configuration

Not applicable

  • Account

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

Enter the following when you click Add Account:


    • AWS access key id
    • AWS access key secret

Azure Monitor

Excerpt Name: Azure Alerts connector

Click here to expand...
  • Configuration
    If you are integrating BMC Helix Multi-Cloud Broker with Azure Monitor, enter the following values:

    Field

    Value

    Name

    Enter a name for your connector configuration.

    Description

    Enter a description for your connector configuration.

    Site

    Select the site required to establish a connection between Azure Monitor and BMC Helix Integration Service. You can either use the default cloud site or create your own site.

    Number of instances

    Retain the default value.

    WebHook Message Type

    Select Basic or Secure. Select the same type when creating actions on Azure alerts in Microsoft Azure.

    Azure Tenant Id

    Required only when you use secure webhook method.

    Application Id

    Required only when you use secure webhook method.

    Application ID URI

    Required only when you use secure webhook method.

CA Agile Central (Rally Software)

Excerpt Name: caAgileCentral

Click here to expand...
  • Configuration

    Field

    Value

    Name

    Enter a name for the connector configuration.

    Site

    For an on-premises CA Agile Central instance, select the site that you created. For instances in the cloud, select Cloud as the site.

    CA Agile Central Hostname

    Enter the name of your CA Agile Central server.

    CA Agile Central server Port:

    Enter the port number of the CA Agile Central server.

    Protocol

    Enter the protocol.

  • Account
    • Add the account of a CA Agile Central user who can view and update issues.

IBM QRadar

Excerpt Name: QRadar

Click here to expand...
  • Configuration

    Field

    Value

    Name

    Enter a name for the connector configuration.

    Description

    Enter a description for the configuration.

    Site

    Select Cloud.

    Number of instances

    Keep the default value.

    QRadar Server URL

    Enter the URL of QRadar SIEM server.

  • Account
    • Add the account of a QRadar SIEM user who can view and update offenses

JIRA

Excerpt Name:  Jira

Click here to expand...
  • Configuration

    Field

    Value

    Name

    Enter a name for the connector configuration

    Site

    For each on-premises Jira instance, select the site that you created.
    For cloud instances of Jira instances, 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.
    Enter 443 if your Jira server is SSL enabled.

    Protocol

    Enter the protocol used by the Jira server.

    Certificate Authority

    Copy the contents of a self-signed certificate.

    Warning

    Important

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

  • Account
    • Add the account of a Jira user who can view and update Jira issues.
    • For an on-premises instance of JIRA, enter the password for the user. For a cloud instance of JIRA, enter the API token for the user.
    • If you need to integrate with multiple Jira instances, add an account for each of the Jira instances.


JIRA Service Desk

Excerpt Name: jiraServiceDesk

Click here to expand...
  • Configuration

Field

Value

Name

Enter a name for the connector configuration.

Site

For an on-premises Jira Service Desk instance, select the  site that you created.
OR
 For Jira Service Desk instances in the cloud, select  Cloud  as the site.

Jira Server Hostname

Enter the name of the Jira Service Desk server.

Jira server Port

Enter the port number of the Jira Service Desk server. Use port number 443 for HTTPS protocol.

Protocol

Enter the protocol used by the Jira Service Desk server.

  • Account
    Add the account of a Jira Service Desk user who can view and update Jira Service Desk incidents.

Microsoft Azure DevOps

Excerpt Name: azure

Click here to expand...
  • Configuration

    Field

    Value

    Name

    Enter a name for the connector configuration.

    Site

    Select Cloud as the site.

    Azure DevOps Cloud Service URL

    Azure DevOps Services Organization

    Enter the name of the organization defined for Azure DevOps Services.

    API Version

    Select 5.0.

  • Account
    • Add the account of a Azure DevOps user who can view and update work items

Remedyforce

Excerpt Name: remedyforce

Click here to expand...
  • Configuration
    • If you are integrating with an on-premises instance of ITSM, enter values for the following fields:

      Field

      Value

      Name

      Enter a name for the connector configuration

      Description

      Enter a description for the connector configuration

      Site

      Select the site required to establish a connection between Remedyforce application and Integration service. You can either use the default cloud site or create your own site.

      Number of instances

      Use the default value

      Type


    • If you need to integrate with multiple instances of Remedyforce, add a Connector Configuration for each instance.
  • Account
    • Add the account of a Remedyforce user who can view and update Remedyforce tickets.
    • If you need to integrate with multiple Remedyforce instances, add an account for each of the Remedyforce instances.

Salesforce Service Cloud

Excerpt Name: salesforceServiceCloud

Click here to expand...
  • Configuration
    Not applicable
  • Account
    Add a Service Cloud user that has permission to view and update cases. Ensure that you add a user account that is at the highest level in the role hierarchy, so that all attachments from Service Cloud are visible. if you do not have a role hierarchy, ensure that you create a role hierarchy and assign the appropriate roles to your users (agents) who create cases.

TrueSight Operations Management

TrueSight Ops Mgmt for PSR

Excerpt Name: tsom

Click here to expand...
  • Configuration
    If you are integrating BMC Helix Multi-Cloud Broker with an on-premises instance of ITSM, enter the following values:

    Field

    Value

    Name

    Enter a name for the connector configuration.

    Description

    Enter a description for the connector configuration.

    Site

    Select the site required to establish a connection between TSOM and BMC Helix Integration Service.

    You can either use the default cloud site or create your own site.

    Number of instances

    Keep the default value (2).

    TSPS Server URL

    Enter the URL of TrueSight Presentation Server (TSPS) that you configured while installing TSOM.

    For example, enter https://[TSPS Server Name].

    TrueSight Data Providers

    Enter the hostname of TrueSight Infrastructure Management (TSIM) server that you configured while installing TSOM.

    For example, enter [TSIM Server Name].

    TrueSight User Realm

    If you are using Local User Authentication with Remedy Single Sign-On (Remedy SSO or RSSO), enter the realm name that you are using for the authentication.

    TrueSight Tenant

    Enter the name of the TrueSight tenant.

    If you do not have the tenant name, enter *.

    TrueSight Retry Count

    Keep the default value (5) or enter a new one.

    TrueSight Retry Interval

    Keep the default value (60000) in milliseconds or enter a new one.

    TrueSight Concurrent Request

    Keep the default value (10) or enter a new one.

  • Account
    Add a ITSM user account that has permissions for viewing business service requests and permissions for updating incidents, change, or problem requests

ITSM for PSR

Excerpt Name: ITSMPSR


Click here to expand...
  • Configuration
    If you are integrating BMC Helix Multi-Cloud Broker with an on-premises instance of ITSM, enter the following values:

    Field

    Value

    Name

    Enter a name for the connector configuration

    Description

    Enter a description for the connector configuration

    Site

    Select the site required to establish a connection between ITSM and BMC Helix Integration Service.

    You can either use the default cloud site or create your own site.

    Number of instances

    Keep the default value (2).

    ITSM Url

    Enter your ITSM URL.

    For example, enter http://[ITSM Server Name]:8008.

  • Account
    Add a ITSM user account that has permissions for viewing business service requests and permissions for updating incidents, change, or problem request.


ServiceNow

Excerpt Name: snow

Click here to expand...
  • Configuration
    <To add details>
  • Accounts


 

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

BMC Helix Multi-Cloud Broker 22.1