As of ActiveControl 8.40, there are essentially three main ways of integrating ActiveControl with other tools:
1. Using the SAP Integration Framework that has been available within ActiveControl for the past decade.
2. Using the Node-Red Integration Framework, introduced in ActiveControl 8.40 (2021)
3. Utilising standalone APIs and webhooks.
Although the focus of this document is (3) – all three will now be summarised in turn.
SAP Integration Framework.
ActiveControl has long offered an Integration Framework – based on SAP ABAP – to enable integration between ActiveControl and 3rd Party tools used by our customers. The following integrations are offered.
|Cherwell||ITSM||Integration Guide available on request|
|Team Foundation Server||ITSM||Integration Guide|
|HPSM||Manual Testing||Integration Guide|
|smartShift||S/4 migrations||Integration Guide|
|Jenkins||AUtomated Testing||Integration Guide|
Of these integrations, the ServiceNow and JIRA integrations are the most mature and well-established at Basis Technologies customers. The others were built to fulfil specific Customer requirements, and are less widely utilised within Basis Technologies customer-base.
Node-RED Integration framework
In 2021,a new Node-Red integration Framework was introduced as part of ActiveControl 8.40. Node-RED is a flow-based development tool for visual programming, for wiring together hardware devices, APIs and online services. Basis Technologies believe that using Node-RED as an integration middleware between ActiveControl and 3rd Party products will enable new integrations to be setup much more easily and rapidly than we have been able to do in the past. Basis Technologies intend to replace the use of the SAP Integration Framework with this new Node-RED integration framework over time.
As ‘templates’ for new integrations are created by Basis Technologies, Integration Guides will become available via https://docs.basistechnologies.com/
|Azure DevOps||ITSM / DevOps||In Progress|
SOAP APIs, webservices and webhooks.
There may be instances where Basis Technologies may want to build their own integrations between ActiveControl and other tools, either because Basis Technologies does not already offer an out-of-the-box integration via either our SAP or Node-RED integration frameworks – or because the Customer prefers to use their own middleware such as Tibco, PI etc – or because the tool is proprietary or non-strategic and Basis Technologies do not have the capacity to develop the Integration for our Customers.
This can be achieved using APIs, webservices and webhooks that are available as part of ActiveControl.
The purpose of this document is to detail what is available as part of ActiveControl, for customers that do want to explore this option.
The intended audience for this document are the technical teams looking to implement integration between ActiveControl and third party tools – but not using our existing SAP and Node-RED integration frameworks.
The document assumes prior knowledge of ActiveControl and also general Integration principles.
Basis Technologies effort to develop or setup Integrations using our SAP or Node-Red Integration Frameworks is a chargeable activity. Similarly, providing Customers with assistance in setting up their own integrations using our APIs, webservices or webhooks is chargeable consulting rather than a maintenance support activity. If a Customer is interested in setting up an Integration and requires Basis Technologies assistance, then they should reach out to their Account Manager in the first instance to discuss options of how best to proceed.