Page tree

Skip to end of metadata
Go to start of metadata

BMC provides a flexible model for data integrations to and from its Helix services. Integrations may be configured using any approved communication method or adapter.

This topic contains the following information:

Approved integration methods

Any integrated system that communicates using one of the following methods is pre-approved. These types of integrations do not require approval from BMC’s Customization Review Board (CRB).

Method or AdapterServicesDescriptionBMC Helix Client Gateway Prerequsite
Web Services

BMC Helix ITSM

BMC Helix Custom Applications

BMC Helix Business Workflows

This integration technology (XML, WSDL, UDDI, REST and SOAP) allows you to build distributed applications without programming and is the preferred method for integrating with BMC Helix services.

  • Use the Set Fields workflow action and a web services object to consume third-party web services in BMC Helix applications.
  • Starting with version 19.08, BMC Helix ITSM provides the ability for you to call a third-party REST API using Developer Studio, assuming the third-party application exposes its REST APIs. For lower versions, BMC Helix ITSM does not consume the REST service; it is for third-party consumption to the BMC Helix application only. For more information on this new feature, see Calling third-party REST APIs.
  • Use the AR System platform to create and publish a Web Services object.
No
C API BMC Helix ITSM
The AR System API on the server is the most technically complex method. It requires knowledge of C programming and building executables. However, it provides access to all AR System server functionality for a tightly linked and high-performance integration.Yes
Java APIBMC Helix ITSMThe AR System Java API is a collection of Java classes that provide AR System C API functionality in a Java development environment. Developers can use this abstraction layer to quickly build enhanced applications for the web.Yes
AR System Plug-insBMC Helix ITSMAR System clients perform data operations on external systems through the AR System server, plug-in service, and plug-in related APIs. The plug-in service extends the AR System server to integrate with external data sources. The AR System server connects to the plug-in service, which activates the proper plug-in when a transaction is made.Yes
Open Database Connectivity (ODBC) Access

BMC Helix ITSM

BMC Helix Custom Applications-based applications

Third-party tools with appropriate permissions can access any information in the application database via ODBC. ODBC access is only permitted as read-only and may be granted to the production database. See ODBC access requests for additional information.

Yes
BMC Atrium Integrator (AI) adapter

BMC Helix ITSM

Helix Custom Applications

Helix Business Workflows

The BMC Atrium Integrator adapter provides a single method of importing and exporting data to and from AR System and the BMC Helix ITSM suite. It supports the ability to import and export data from multiple types of data sources. These data sources include text files, Excel files, data in relational databases, data in other AR Server systems, AR data export files (.arx files), and more.Yes
Managed file transfer (MFT)

BMC Helix ITSM

BMC Helix Custom Applications

BMC Helix Business Workflows

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.No
Security Assertion Markup Language (SAML)

BMC Helix ITSM

BMC Helix Custom Applications

BMC Helix Business Workflows

SAML is a standards-based authentication protocol that allows federated authentication between your environment and the Helix applications. It is the preferred method for authentication. See Federated authentication for more information about SAML.No
Simple Mail Transfer Protocol (SMTP) transactions

BMC Helix ITSM

BMC Helix Custom Applications

BMC Helix Business Workflows

BMC Helix Client Management

The inbound and outbound email integration service enables customers to open tickets in their BMC Helix environment using email and to receive notification emails for events such as ticket creation, updates, and so on. See Planning email integration with BMC Helix services and Inbound and outbound email integration for additional information.No
Computer telephony integration (CTI)BMC Helix ITSMComputer telephony systems such as Avaya and Cisco can integrate directly to 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 IT with phone systems for details.No

Reminder:

BMC imposes a 10MB limit on all attachments.

For any integration not using a pre-approved method above, the customer (or their designated onboarding partner) must submit a request to BMC’s CRB in advance of development. See the BMC Helix ITSM Customization Policy for additional information.

Non-standard integration methods 

BMC supports the use of Java filters and AR Server Database Connectivity (ARDBC) plug-ins under certain conditions. See Customizations as part of integrations for a detailed summary of what types of customizations are allowed in BMC's cloud, and how to get approval to implement them.

Integration development and maintenance

BMC Helix customers are responsible for:

  • Procurement, installation, and maintenance of any on premises integrated system
  • Implementation and configuration of the integration (this typically requires a statement of work from an onboarding partner)
  • Ongoing maintenance of all integrated systems throughout the service term (this includes upgrades required to any on premises integrated system to ensure version compatibility with the Helix service)
  • Obtaining approval from BMC’s CRB in advance of implementation of any integration not communicating using an approved method
  • Requesting assistance from BMC SaaS Operations for port configurations
  • Configuring the BMC Helix Client Gateway on premises component for an integration requiring low level security (see BMC Helix Client Gateway connectivity for additional information)

 

10 Comments

  1.  

  2.  

  3.  

  4. I'm not sure why you would need BMC Helix Client Gateway for the Computer Telephony Integration (CTI).  The telephone system is simply popping up a URL to Smart IT and passing parameters.  Is that a typo in the doc?

    1.  

      1.  

  5.  

    1.  

  6. link "BMC Helix Client Gateway connectivityaddress to BMC Helix Client Activation instead of Gateway.

    1.