Integrations

BMC products are available for customers to purchase and can be integrated with BMC Helix Innovation Suite.

For more information, see:

• BMC Live Chat

• Installing BMC Atrium Core Web Services components

• BMC Atrium CMDB extensions overview (Make sure that you are logged in to view this content)

• Integrating BMC Helix CMDB with Microsoft SCCM by using an adapter

• BMC-Helix-Client-Management-service
• To configure the BMC Change and Configuration Management (CCM) integration, use Atrium integrated jobs. 
• Integrate BMC Discovery with your BMC Helix environment by using the BMC Client Gateway, or purchase BMC Helix Discovery and integrate it with the BMC Helix environment.

Third party applications can be integrated with  BMC Helix Innovation Suite by using the following methods:

• Rest API (Recommended)
• Web services
• ODBC Read-only integration
• Integrations that require a port (Using Kaazing client gateway)
  For integrations that need a port, the port needs to be configured in the Kaazing Client Gateway config file, kwic-config.xml.
  Create a support ticket, provide the integration and port details and attach the config file so that the BMC SaaS Operations team can also do the configuration on the Kaazing server side for the integration to be functional.
  Depending on the integration information available, you can either submit a single ticket or multiple tickets. If you have the necessary details for all integrations, submit a single Support ticket or if you do not have all integration details handy, you can submit multiple Support tickets when you are ready with the port details of those integrations. 

You can call AR C APIs to connect to the AR Server and perform the following functions on the AR object from your third-party applications:

• Create - Create an instance of the object.
• Delete - Delete an existing instance of the object.
• Get - Get details about an existing instance of the object.
• Set - Set (update) an existing instance of the object.
• GetList - Search and get a list of matching instances of the object.

For more information, see 

• Using the AR System API for integration

• AR System API library functions

You can call AR Java APIs to integrate with the AR System and perform different functions on the AR object from your third-party applications: The Java API is a collection of classes, interfaces, and relationships that provide full client functionality like the AR System C API in a style consistent with typical Java programming techniques. 

For more information, see 

• AR System Java API overview

• Programming with the Java API

• BMC Atrium CMDB Java API package

Flat files may be pushed to a folder on the Mid Tier or AR server (depending on requirements) using the MFT process. Both encrypted and unencrypted connections and transfers are supported, however, encryption is recommended. The MFT process moves data to a point where it can be consumed by other mechanisms (such as AI or the Data Management utility) for importing data into BMC Helix ITSM applications. See Lifecycle-Requests for information about how to request FTP directory configuration. See Data Management for more information about the Data Management utility.

• Atrium Integrator and Data Management jobs best practices 
• Integrating-with-Active-Directory-to-load-ITSM-people-data
• Best-practices-for-customizing-Data-Management-jobs

• BMC Helix Discovery
• BMC Helix iPaaS 
• BMC Helix Multi-Cloud Broker 

Phone systems such as Avaya and Cisco can integrate directly into the Smart Recorder feature of Smart IT. If the phone system software also has IVR capabilities, it can pass a verbal description of the issue to Smart Recorder as text. See Integrating Smart Recorder with phone systems for details.