Performing preconfiguration tasks for BMC Helix Integration Service
After you complete the common preconfiguration tasks, perform the tasks described in this section if you choose BMC Helix Integration Service as your integration technology.
Important
The go-forward scope for BMC Helix Integration Service will be limited to BMC-to-BMC centric integration use cases. For more information, see Product announcements.
To deploy BMC Helix Integration Service sites and Integration Controller to integrate with on-premises third-party applications
The activation email that you receive from BMC contains the information about your instance of BMC Helix Integration Service. Make sure that you have the tenant administrator credentials for your instance of BMC Helix Integration Service.
Best practice
- Set up sites in BMC Helix Integration Studio.
A site lets you access the on-premises applications that are running on your local machine or on a server in your organization's data center. - Install the Integration Controller
The Integration Controller is required to integrate BMC Helix Multi-Cloud Broker with your on-premises applications.
For more information about setting up sites and installing the Integration Controller, see Installing and configuring sites to run on-premises connectors.
To define a business service in BMC Asset Management for incident brokering or the Services Dashboard
To implement incident brokering or the Service Dashboard, you must add a business service in BMC Helix ITSM. Skip this step if you are setting up BMC Helix Multi-Cloud Broker for a service that has already been defined in BMC Helix ITSM.
Important
This step is not required for DevOps integration with Atlassian Jira Software and Rally Software (formerly known as CA Agile Central).
- Log in to BMC Asset Management.
- Create a business service that you want to use for ticket brokering; for example, Amazon EC2 Compute.
For information about creating a Business Service CI, see Creating and modifying CIs.
Comments
Log in or register to comment.