Configuring BMC Helix Multi-Cloud Broker
This section guides you through the process of setting up BMC Helix Multi-Cloud Broker for your organization. As a tenant administrator, you need to complete a few configuration tasks like providing server details, account information, and trigger conditions among others, to start using BMC Helix Multi-Cloud Broker features. These configurations are performed in BMC Helix iPaaS, powered by Jitterbit, BMC Helix Integration Service, BMC Helix Innovation Suite, and BMC Helix Multi-Cloud Broker.
The BMC Helix Multi-Cloud Broker Quick Configuration Guide takes you through the steps of the configuration process. For the tasks that need to be performed from BMC Helix Integration Service or BMC Helix Innovation Suite, the Quick Configuration Guide provides links to launch the appropriate application.
The following image provides a quick overview of the BMC Helix Multi-Cloud Broker configuration process:
Preconfiguration tasks
Before you start using BMC Helix Multi-Cloud Broker, you must perform the preconfiguration tasks that help you to set up the product, for example, adding server details, configuring user credentials, and so on.
To get a list of tasks, see Performing preconfiguration tasks.
BMC Helix Multi-Cloud Broker features
The following table describes the features that you can configure with your cloud service provider.
| Feature | Description | Reference |
|---|---|---|
| Incident Brokering | The Incident Brokering feature facilitates efficient service management by integrating BMC Helix ITSM with cloud service providers (for example AWS). When a service desk agent creates an incident in BMC Helix ITSM, BMC Helix Multi-Cloud Broker creates a corresponding ticket with the appropriate cloud service provider (for example AWS). Incident brokering is supported for the following vendors:
| For an overview of this feature, see Incident brokering. For information about configuring this feature, see:
|
| Ticket Consolidation | The Ticket Consolidation features facilitate consolidation of vendor tickets into BMC Helix ITSM. A corresponding ticket is created in BMC Helix ITSM when an incident is created in the cloud service provider's ticketing system. Ticket consolidation is supported for the following vendors:
| For an overview of this feature, see Consolidation of tickets from vendor applications into BMC Helix ITSM. For information about configuring this feature, see:
|
| DevOps Implementation | DevOps Implementation features aim at addressing the challenge of integrating tools used by the IT operations teams and those used by development teams in a DevOps environment. BMC Helix Multi-Cloud Broker helps integrate BMC Helix ITSM with tracking tools such as Atlassian Jira Software or Rally Software (formerly known as CA Agile). DevOps implementation is supported for the following tools:
| For an overview of this feature, see DevOps integration. For information about configuring this feature, see:
|
| IT operations management integrations for cloud monitoring (Notification) | IT operations management integrations for cloud monitoring provides integration with IT operations management (ITOM) vendors. It enables you to track the availability, consistency, reliability and quality of your services. IT operations management integrations for cloud monitoring is supported for the following tools:
| For an overview of this feature, see IT operations management integrations for cloud monitoring For information about configuring this feature, see: |
| Cloud Service Dashboard | The Cloud Service Dashboard enables tracking of status and view metrics for all the services. | For an overview of this feature, see Cloud Service Dashboard. For information about configuring the Cloud Service Dashboard, see Setting up the Service Dashboard. |
| Security | Security integration with IBM QRadar enables you to manage offenses in BMC Helix ITSM to service that risk with its ticket management platform. | For an overview of this feature, see Enabling prebuilt integration with IBM QRadar. |
Vendor data configuration
A vendor organization is a third-party vendor that provides a service to your organization. To enable ticket brokering, as a tenant administrator, you must specify the details about the vendor organization and the service with which you want to integrate. BMC Helix Multi-Cloud Broker uses the vendor data and service data to map fields across applications and associate services with the appropriate vendors. You can set up vendor data in BMC Helix Multi-Cloud Broker.
Configurations specific to integration platform
To enable an integration between BMC Helix ITSM and vendor applications, you can choose either BMC Helix iPaaS, powered by Jitterbit or BMC Helix Integration Service as the underlying integration platform. Based on the integration platform that you choose, you must configure different components that help you connect applications and transfer data between them.
The following table provides a brief overview of these components:
| Underlying integration platform | Component | Description |
|---|---|---|
BMC Helix iPaaS | Project variables | A project variable is a data element that you can update based on your environment settings. You set a project variable before running an integration. You can set a project variable for credentials, filenames, or environment settings. |
BMC Helix Integration Service | Connector | A connector is an integration with a BMC or third-party application, such as BMC Helix ITSM, Atlassian Jira Software, and so on. Each connector supports a certain number of triggers, actions, or both. A connector configuration contains information about the third-party system such as the protocol, server host name, server port, and account details. You can configure Connectors in BMC Helix Integration Service. You might need to configure several connectors for each feature that you want to set up. |
| Flow | A flow is a connection between two connectors that enables you to accomplish a certain task. Each flow has a source application and a target application. A triggering event in the source application will cause an action to take place in the target application. When setting up BMC Helix Multi-Cloud Broker, as a tenant administrator, you must specify the appropriate trigger conditions and field mapping for each flow. You can configure flows in BMC Helix Integration Service. You might need to configure multiple flows for each feature that you want to set up. | |
| Connector target | BMC Helix Multi-Cloud Broker defines processes to call vendor application specific actions to perform different business functions. When triggered by using a rule, a process uses the actions defined to implement the business logic for a given business case. The process is associated with a Connector Target which provides the process with the information required to connect to a vendor service. |
Service configuration
You can add services to the BMC Helix Multi-Cloud Broker service dashboard and view the health of these services. This helps you analyze the service data, gain insights into the service performance, and take necessary actions on the services.
To learn about adding the services, see Setting up the Service Dashboard.
Comments
Log in or register to comment.