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 iPaaS, powered by MuleSoft, 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). To get a list of available incident brokering features, see Orientation. | For an overview of this feature, see Incident brokering. For information about configuring this feature by using different integration technologies, refer to the following documentation: |
| Ticket Consolidation | The Ticket Consolidation features facilitate consolidation of third-party application 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. To get a list of available ticket consolidation features, see Orientation. | For an overview of this feature, see Consolidation of tickets from third-party applications into BMC Helix ITSM. For information about configuring this feature by using different technologies, refer to the following documentation: |
| 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). To get a list of available ticket consolidation features, see Orientation. | For an overview of this feature, see DevOps integration. For information about configuring this feature by using different technologies, refer to the following documentation: |
| IT operations management integrations for cloud monitoring (Notification) | IT operations management integrations for cloud monitoring provides integration with IT operations management (ITOM) third-party applications. It enables you to track the availability, consistency, reliability and quality of your services. To get a list of available ticket consolidation features, see Orientation. | For an overview of this feature, see IT operations management integrations for cloud monitoring For information about configuring this feature by using different technologies, refer to the following documentation: |
| 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 Security. For information about configuring this feature by using different technologies, refer to the following documentation:
|
Vendor (or third-party application) 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 third-party organization and the service with which you want to integrate. BMC Helix Multi-Cloud Broker uses the third-party data and service data to map fields across applications and associate services with the appropriate third-party applications. You can set up third-party application data in BMC Helix Multi-Cloud Broker.
Configurations specific to integration technology
To enable an integration between BMC Helix ITSM and third-party applications, you can use BMC Helix iPaaS, powered by Jitterbit, BMC Helix iPaaS, powered by MuleSoft, or BMC Helix Integration Service as the underlying integration technology. Based on the technology that you choose, you must configure different components that help you connect applications and transfer data between them, as shown in the following image:
To learn more about the technologies and their components, see Leveraging integration technologies to integrate BMC Helix ITSM and third-party applications.
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.