This document is intended to be a landing pad for all the application programming interfaces available to developers.
Here is the Integration Guide for 7.6.04 from BMC.
The Client Type APIs
There are several programming languages available for building Remedy clients.
Both the native Windows client (aruser), Mid-Tier and Developer Studio has been built using this type of API, along with most third party integrations to the AR System.
If you are building your own Developer Studio, you will need to stick to Java or C, but in 99% of the cases you are only working with Data, and in those cases all the interfaces are ok.
If you only need to create, search or update data within the AR System, you can let your environment and programming skills direct your choise of language.
|Technology||Pros||Cons||Quick Start / Comparison||Download||Learning more|
|.NET and COM|
.NET and COM: 8.07.6.4 7.1
.NET and COM:
Remedy Javadocs API
Remedy Javadocs API Reference
The Filter Plugin API for extending Filter Actions to other programming languages
The FilterAPI plugin architecture allows for defining programs that will be run by either the C or Java Plugin servers. You can pass data from a standard Filter Set Fields action (of type FilterAPI) and then map return values back to fields. A FilterAPI plugins allow for an ideal mechanism of interacting with third party systems that expose interfaces that can't be connected to via standard Remedy methods (e.g. web services, db queries, etc).
Below are links to community developed FilterAPI plugins samples provided with full source code for those interested:
The ARDBC Plugin API for integrating other Database Type resources into the AR System
This API is used when you want to make an external data source available for Users and/or Remedy Developers in the same way as any form. They are called Vendor Forms.
Your integration can allow searching, viewing, updating and creation of data in the external data source.
A pre-build integration for LDAP (AD) using ARDBC technology is shipped with the AR Server.
The AREA Plugin API for authentication integrations
This plugin is used when you keep your passwords, and/or account information such as email, license type and permission groups outside your AR System database.
An LDAP integration built on this API is shipped with the system to integrate to, for example, Active Directory (AD).
Consuming external Web Services from the AR System
You can call external web services from filters, in order to push or get data into the AR System.
This is done via a Plugin that is shipped with the AR Server, and runs within the Plugin server.
Publishing Web Services from the AR System
Publishing data or interfaces to the AR System can be done on Mid-Tier, via a HTTP Web Service interface.
This is useful when you want other systems to submit, search or modify data within your AR Server.
Data Visualization Field integrations
You can seamlessly incorporate other web content, or your own rich web applications within a Data Visualization field, to allow better user interaction.
The programmer can hook into the user session in order to get or set data in the users session, or to retrieve/update additional information directly from the AR Server. The latter is done via the ordinary Client Type Java API described above, while leveraging the users session to the server, including permissions and the AR License.
This is the Web-replacement for client side Run Process or COM integrations executed from within the ARUser Windows client.
Integration through Email Engine
You can use emails to send notifications from the AR System, or to receive emails from users or other system.
You can send email commands to the AR System in order to submit, modify or search for tickets using both a native format and an XML-based format.
Direct SQL integrations
You can have your AR System issue SQL-commands within the database it is connected to.
The SQL commands can be executed from Filters, Active Links or Character Menus (menus connected to individual fields).
You can access external databases as well, but these has to be made available within the (single) database that your AR Server connects to. For example via a database link.
Database integration using View Forms
If you need flexible integrations to a database table, you can point a View Form to this table.
This would typically be a table or view containing data external to the AR System, but it must be data that can be accessed from the (single) database that your AR Server connects to. For example via a database link.
BMC Atrium Integration Engine (AIE/EIE)
The Atrium Integration Engine is a mechanism to manage data transfers between external data sources and the CMDB along with AR System forms. It is a bi-directional and multi-threaded data transfer engine. It supports event based or scheduled information flow. It is ideal for bulk, incremental data syncronization transfers.
AIE provides an intuitive graphical interface for field mapping and job configurations.
Data sources include:
- Flat file e.g. csv, XML
- Database using the associated connectors - SQL, Oracle and DB2
- Custom built adapters via Adapter Development Kit
With BMC Atrium Integration Engine, you can do scheduled bulk data transfers and event-based integrations initiated by either the source, target, or any other application. You can also use BMC Atrium Integration Engine for initial data load, incremental data transfers, and data synchronization. You can build links between BMC Remedy IT Service Management (BMC Remedy ITSM) applications and Enterprise Resource Planning (ERP), Customer Relationship Management, Supply Chain Management, and other enterprise applications.
BMC Atrium Integrator (7.6.x and above)
Atrium Integrator is an integration engine that enables you to transfer data from external data stores to BMC Atrium Configuration Management Database (BMC Atrium CMDB) classes. You can connect to a wide variety of input sources using connectors such as JDBC, ODBC, JMS, native databases, web services, and complex XML. Atrium Integrator provides you with the ability to clean and transform your data before putting it into BMC Atrium CMDB.
Atrium Integrator replaces BMC Atrium Integration Engine. You can continue using BMC Atrium Integration Engine for existing data mappings and exchanges, but BMC recommends that you use Atrium Integrator for all new data transfers. BMC Atrium Integration Engine will be deprecated in a future release.