The standard integration scenario is to combine ActiveControl and a third party IT Service Management product, and possibly a Test Automation product to create a fully integrated end-to-end process for managing change.
This typically requires both inbound and outbound integration:
- Change created in third party ITSM system
- Change approved for development in ITSM system
- Change interfaced to ActiveControl (inbound integration)
- Change managed through ActiveControl for deployment to Test and Pre-Prod with updates sent to ITSM system to reflect progress (outbound integration)
- Change deployed to production through ActiveControl and ITSM system updated (outbound integration)
- Change verified and closed in ITSM system
Note: This section of the Administration Guide will describe in detail how such integration can be easily accomplished using the ActiveControl Integration framework, but it should be noted that the framework can be extended for use in many other integration scenarios.