|
The Integrity architecture for integrations can be broken down into two main classes: interactive tool integrations, and process or event driven server to server integrations.
Interactive Tool Integrations:
These include integrations with productivity tools like Microsoft Office, IDEs like Eclipse and Visual Studio, requirements elicitation tools, modelling tools and others which provide alternate interfaces into the Integrity repository. They allow users to perform tasks and create content in familiar environments and interact with the Integrity platform in an unobtrusive way. Integrity Interactive tool integrations apply raw APIs in different languages and at different levels of complexity as well as abstraction technology like Integrity Gateway. These APIs and Integrity Gateway are also available to partners and customers for the development of custom integrations.
|
| |
Business Process Integrations:
When looking at the larger needs of the business a broader set of capabilities are required for integration technologies – the ability to transfer data as well as coordinate processes between various enterprise applications or between external partners and suppliers is needed. These interactions are generally process and event driven and do not require direct user interaction. Web services and Business Process Execution Language (BPEL) are rapidly becoming standards and the Integrity Integration Platform provides an environment and set of technologies to realize this vision.
|
|
