Setting up and going live
BMC Helix Multi-Cloud Broker is available for SaaS users. As a SaaS user, you must subscribe to BMC Helix Innovation Suite and the BMC Helix Multi-Cloud Broker service to get it deployed in your environment. When you subscribe to BMC Helix Innovation Suite, BMC Software sends you an activation email with the following information to successfully set up BMC Helix Innovation Suite:
- A URL to your instance of BMC Helix Innovation Suite
- Account details like user name and password
- Links to documentation for BMC Helix Innovation Suite
System access details
The following table lists the URL details for BMC Helix Innovation Suite:
Parameter | Value |
|---|---|
host name | The host name provided for BMC Helix Innovation Suite |
port | The port provided for BMC Helix Innovation Suite |
protocol | HTTPS |
user name | The user name provided for BMC Helix Innovation Suite |
password | The password provided for BMC Helix Innovation Suite |
Before you begin
Make sure you complete the following tasks:
Set up your BMC Helix Innovation Suite instance.
For more information, see Setting up and going live in the official BMC Helix Innovation Suite documentation.- Depending on the integration technology that you want to use, subscribe to BMC Helix iPaaS, powered by Jitterbit or contact MuleSoft to purchase the MuleSoft Anypoint Platform.
Change the default passwords for the available systems.
If you are using BMC Helix Multi-Cloud Broker on-premises version, make sure you complete the following on-premises deployment tasks:
Task | Action | Role | Reference |
|---|---|---|---|
1 | Make deployment artifacts available. | Administrator | Host the BMC Helix Innovation Suite container images and token to access the images on the Electronic Product Distribution (EPD) site and make the deployment artifacts available for download. |
2 | Make sure that your system meets the hardware and software requirements. | Administrator | System requirements in BMC Helix Service Management |
3 | Download the artifacts required to perform the installation from the BMC Electronic Product Distribution (EPD) site. | Administrator | Downloading the installation files in BMC Helix Service Management |
4 | Run the HELIX_ONPREM_DEPLOYMENT pipeline. | Administrator | Performing the BMC Helix Service Management installation in BMC Helix Service Management |
5 | Perform post installation configurations. | Administrator | Performing the BMC Helix Service Management installation in BMC Helix Service Management |
6 | If you are using BMC Helix iPaaS, powered by Jitterbit, install a private agent. Important: Install a private agent only when you want to integrate with an on-premises application. | Administrator | Private Agents in Jitterbit documentation |
To set up BMC Helix Multi-Cloud Broker and an integration platform
The following table describes the tasks to set up BMC Helix Multi-Cloud Broker and the required integration platform:
Task | Action | Reference |
|---|---|---|
Configure BMC Helix Multi-Cloud Broker | ||
1 | (Optional) Modify consent for data collection at any time. Data collection is enabled by default, and it provides information about the product usage for identifying defects, improving performance, or developing new product features. | |
2 | Add users and assign them roles and permissions based on their responsibility in the organization. | |
3 | Enable agents to view the third-party application ticket details in BMC Helix ITSM. | |
4 | Add your organization details | |
5 | Enable the brokering of BMC Helix ITSM tickets | |
Set up an integration platform | ||
6 | Set up the integration platform that you want to use for implementing integrations. |
|
7 | Configure the connectors to establish the BMC Helix Multi-Cloud Broker and third-party application connection. |
|
Where to go from here
- After setting up BMC Helix Multi-Cloud Broker, navigate to the Quick Configuration Guide to configure your integrations.
- To configure risk management for integrations involving BMC Helix ITSM change requests, see Multi-Factor-risk-assessment-for-Devops-changes.
- To track the health of your service dashboard, see Setting-up-the-Service-Dashboard.