The Integration Framework is divided between inbound and outbound processes. For inbound calls, those made by a third party system into AC, a number of web services are exposed allowing the external system to manipulate ActiveControl objects. Calls to AC web services will return appropriate error messages, but expect the calling system to deal with queuing, service levels and retries for failed integration transactions. For outbound calls there is a configurable framework that includes data extraction, transformation, mapping and sending routines, alongside error detection, correction and reporting, as can be seen in the table below.

ActiveControl provides Data Extraction and Message Send components for some standard scenarios and third party tools, but these can be enhanced by the addition of custom extraction and send routines plugged into the standard framework. So if, for example, you use an in-house ITSM solution, a new send component can be developed and plugged into the integration framework to facilitate communication between it and ActiveControl. All other standard framework functions, such as data extraction, mapping and error correction remain unchanged and can be used as-is.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment