A basic design philosophy of AR System is that it is almost always used in conjunction with other tools and products to create an integrated solution.
AR System is designed to have many integration points, making it easy to combine with your other solutions.
This table lists the technologies available for integrating with AR System:
Method Description Page
C API (Application Programming Interface)
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 tightly linked, high-performance integration.
page 41
Java API The AR System Java API is a collection of Java classes that provide AR System C API functionality in a Java development environment.
Using this abstraction layer allows developers to quickly build enhanced applications for the web.
page 49
Web Services This integration technology (XML, WSDL, UDDI, and SOAP) allows you to build distributed applications without programming:
• Use the Set Fields workflow action and a Web Services object to
“consume” third-party web services in AR System applications.
• Use AR System to create and “publish” a Web Services object.
page 61
Integration technologies
AR System Plug-Ins AR 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.
page 105
Data Visualization Field
The data visualization field provides a framework and services for BMC Remedy Mid Tier-based graphing solutions. It provides an efficient way to add graphical elements (such as flashboards) to AR System forms.
page 167
AREA Plug-Ins (AR System External Authentication)
BMC Remedy provides a special API that allows user logins to be validated from a data source outside the AR System database. This API is called the AR System External Authentication (AREA) API.
page 124 and page 127 Filter API Plug-Ins The filter API enables you to use filters to permit other applications to
make calls back into AR System.
page 105
ARDBC Plug-Ins (AR System Database Connectivity)
AR System Database Connectivity enables you to access and manipulate data that is not stored in AR System. Using the ARDBC API, you can create plug-ins used by AR System server to manage data. These plug-ins are loaded at run time and implement calls that are analogous to the set, get, create, delete, and get-list API calls for entries in a form.
page 105 and page 135
Vendor Forms Vendor forms allow AR System to present data from external sources as entries in an AR System form. Vendor forms require you to have an ARDBC plug-in installed and configured.
page 183
View Forms View forms allow direct read-and-write access to data in database tables that are not owned by AR System. This allows direct access to these tables, as if they were owned by AR System, without programming, database replication, or synchronization.
page 187
SQL Database Access Third-party tools with appropriate permissions can access any information in the AR System database. In addition, AR System workflow can query other databases.
page 197
ODBC Access ODBC (Open DataBase Connectivity) is a standard database access method developed by Microsoft. Using the BMC Remedy ODBC driver, any client capable of accessing ODBC can have read-only access to AR System forms. Reporting is a common use of ODBC.
page 201
BMC Atrium Integration Engine (AIE)
The BMC Atrium Integration Engine mediates between the AR System server and vendor applications such as SAP®, Oracle, and other applications and databases for which adapters are developed. Adapters can come from BMC Remedy, from partners, or from customers.
page 221
Command Line Interface (CLI)
A Command Line Interface (CLI) is available with most AR System clients. This enables a client to be started and passed a set of parameters so that either it is in a specific state and displays information or it completes a process and exits with no user interface displayed.
page 233
XML Import and Export
AR System can export and import object definitions in XML.
AR System clients can convert AR System objects to XML and vice versa without making calls to the AR System server. When the server exports the file in XML format, it adds a header required to make it a valid XML document. This same header is required for the server to import an XML file correctly. Otherwise, the file is assumed to be in the standard AR System definition format.
page 233
Method Description Page
Running External Applications (Run Process)
One of the actions available in AR System workflow is the Run Process action. AR System can use the command line interfaces of other applications to start those applications and pass them initial data. In some cases, the third-party application is simply started, while in others AR System waits for a response.
page 259
OLE Automation BMC Remedy User supports OLE Automation. It can be both an Automation server and Automation client. This enables AR System to send commands or data to other applications and to receive commands or data from other applications.
page 269
Dynamic Data Exchange (DDE)
BMC Remedy User supports DDE. It can be both a DDE client and server. This enables AR System to pass data to other Windows applications and to be started “in context” by other applications.
page 285
SNMP You can use SNMP to manage complex networks through SNMP-compliant management consoles and monitor network devices.
page 307
Licensing Applications
Authorized integration system vendors (ISVs) can make their applications licensable at the application and user levels.
page 323
Method Description Page
Chapter