How AR System integrates with third-party products
Action Request System is a platform on which you can build applications for automating a wide range of support and business processes. AR System is designed to be used with third-party products to create an integrated solution. In many IT organizations, AR System applications are the central applications for tracking information. Therefore, the opportunities to integrate AR System with other applications are endless, ranging from simple access to diagnostic utilities to large-scale integration with manufacturing, customer interaction, and financial accounting systems.
A strength of AR System is its rich and robust API. All prospective product partners are encouraged to integrate with AR System at the API level whenever possible. For more information, see Developing-an-API-program.
Many customers purchase AR System as a development platform to create their own business applications and automate their business processes. BMC also develops and sells specific applications such as BMC Helix ITSM: Service Desk, BMC Helix ITSM: Asset Management, or BMC Helix ITSM: Change Management. These BMC applications are built on top of AR System.
Integration defined
In the context of software applications, integration means linking products together to provide increased functionality and efficiency. In other words, two products together do more (or do it faster) than the products by themselves.
AR System is a powerful foundation and development environment for applications that automate business processes. Its flexible multiplatform, multidatabase architecture and highly customizable user interface enable you to adapt AR System to the unique business processes of a particular company and to evolve as those processes change. However, AR System alone cannot perform all of the functions in an environment. Instead, you can integrate AR System applications with other applications and tools to form complete business solutions.
Integration benefits
The primary intent of business software is to enable users to do their jobs more quickly with fewer resources. Using two products separately is usually less efficient than using them in an integrated fashion. For example, a user might have to enter the same information into two different applications, which often results in errors. Or the telephone number of an incoming call might be manually entered by a customer service representative rather than automatically captured. Application integration can provide improved efficiency and effectiveness.
Areas for integration
The two primary areas for integration between applications are:
- Data sharing—Passing data structures back and forth or jointly accessing a common database.
- Process linking—One application (App1) automatically launches another (App2) "in context" so that App2 "knows" everything entered into App1, and the user can immediately focus on the part of App2 that continues the process. Or App2 automatically does its job in the background based on directions from App1, and the user does not even know it is running.
The overall environment behaves as if it was one large application, and yet the company can choose the discrete pieces that best meet the business requirements.
Real-time versus asynchronous
Products are sometimes integrated for real-time interaction.
In contrast, some integration is done asynchronously. This means that an application can be updating another application on an ongoing basis so that the second application is up-to-date the next time it is accessed.
For complete information about integrating with third-party products, see Integrating.