Search
Related topics are listed below.
JIRA AC out of sync
Troubleshooting Integration Errors » Testing Scenarios » JIRA AC out of sync
Jira moves to QA in Progress AC is in the outbox but not in test queue Mark JIRA as done Query 2 will pick up the item but an do nothing with it
JIRA Query Error
Troubleshooting Integration Errors » Testing Scenarios » JIRA Query Error
Message if there is an issue with the JIRA Query. This could be eg URL is invalid URL is valid but user has no authority URL runs but doesnt find expected data – eg if AC and JIRA are out of Sync
Jira Integration User
ActiveControl Domain Controller Setup and Configuration » Bi-directional Integration Process » Jira Integration User
An integration user needs to be created in Jira for use with the integration. This integration user is what is configured against the RFC within the SAP AC Domain Controller. The integration user userid will be in email format. The integration user password needs…
Solution 031: TE field & not found for integration system & polling item &
Troubleshooting Integration Errors » Solution 031: TE field & not found for integration system & polling item &
Fields in /BTI/TE_INT_POLF – TEFIELDREF – must be valid
Solution 028: Log not initialized sub-object INTEGRATION_01 not created for log object /BTI/TE
Troubleshooting Integration Errors » Solution 028: Log not initialized sub-object INTEGRATION_01 not created for log object /BTI/TE
Go to txn SLG0, Choose /BTI/TE and click on sub-objects. Then click on new entry and create sub-object INTEGRATION_01 and save it.
Solution 005: WS call failed for integration system [X] with code [X] [X]
Troubleshooting Integration Errors » Solution 005: WS call failed for integration system [X] with code [X] [X]
Message if there is an issue with the JIRA Query. This could be eg URL is invalid URL is valid but user has no authority URL runs but doesn’t find expected data – e.g. if AC and JIRA are out of Sync
SAP Error Messages
Troubleshooting Integration Errors » SAP Error Messages
The following are examples of integration failures, in terms of error message that will seen via SLG1 and likely root-cause. Error Error Probably Root Cause Communication failure for system NN polling item. HTTP request receive failed for…
User mapping based on email address
ActiveControl Domain Controller Setup and Configuration » Inbound Integration Polling » User mapping based on email address
As part of an ActiveControl JIRA integration, a Tester has to be assigned to the Business Task being automatically created. ActiveControl integrations traditionally rely on the username on the ITSM system matching that of the SAP username. Based on this, a user field…
Polling Engine Batch Job
ActiveControl Domain Controller Setup and Configuration » Inbound Integration Polling » AC Polling Engine » Polling Engine Batch Job
Job for: /BTI/TE_INTEG_POLL A job need to be scheduled via SM36 to run the external system polling. Program Variant Job Name Frequency Notes /BTI/TE_INTEG_POLL JIRA TE INTEGRATION 5 MIN Every 3 minutes …
OTHER CONFIGURATION TABLES
OTHER CONFIGURATION TABLES
The following are other configuration tables pertaining to the ActiveControl Integration Framework. Notification Engine ActiveControl standard Notification Engine (/BTI/TE_RNOTIFICATION_ENGINE) is used to send automated emails. The Notification Engine includes a…
Polling URL
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Polling URL
As part of the ActiveControl/JIRA integration – it is possible to automatically populate the URL to the Business Task within the ActiveControl WebUI to a custom field in JIRA. This is achieved via a User Exit solution and some associated…
System Unavailability
Troubleshooting Integration Errors » System Unavailability
There may be occasion where the Integration is not possible due to system downtime on either ActiveControl or JIRA side. ActiveControl downtime If the AC Domain Controller is down or unavailable for whatever reason, when the Domain Controller becomes available again…
Solution 016: WS call failed for integration system [X] polling item [X] with code [X] [X]
Troubleshooting Integration Errors » Solution 016: WS call failed for integration system [X] polling item [X] with code [X] [X]
Check RFC Destination for correct Target Host, Service No. and Path Prefix (proxy), ensure a target system username and password is defined, SEE 4.1.3 RFC Destination Check /BTI/TE_INT_SYST that correct RFC Destination is defined, SEE 4.1.2 External System(s) Check…
Mapping
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Mapping
An essential part of the integration framework is mapping ActiveControl fields to the equivalent fields on any external system. This is achieved using the table ‘/BTI/TE_INT_MAPP’. Ideally, this process will need to be undertaken before the framework can be used.…
Solution 017: Communication failure for system [X] polling item
Troubleshooting Integration Errors » Solution 017: Communication failure for system [X] polling item
The integration was not possible due to JIRA unavailability.
Background
Introduction » Background
ActiveControl includes an Integration Framework that can be used to deliver data integration between ActiveControl and other 3rd Party Tools. The Integration Framework can manage outbound interactions with external systems (including queuing, re-sends, error…
Complex Mapping
OTHER CONFIGURATION TABLES » Complex Mapping
For complex mapping scenarios, a specific function module can be created on the ActiveControl Domain Controller to perform whatever mapping or transformation that may be required. /BTI/TE_INT_FLDE – Mapping User Exits Field Description…
RFC Destination
ActiveControl Domain Controller Setup and Configuration » Bi-directional Integration Process » RFC Destination
For API calls to 3rd party tools, AC requires setup of HTTP RFC Destination. Field Description RFC Dest Name of service and system Connection Type G = HTTP External Service Description Description…
AC Polling Fields
ActiveControl Domain Controller Setup and Configuration » Inbound Integration Polling » AC Polling Fields
/BTI/TE_INT_POLF Fields for polling items Task headers EXTSYS_NO Integration system number SEQUENCE_NO sequence EXTERNAL_REF Field in external system or value TEFIELDREF Field in AC (structure…
External System(s)
ActiveControl Domain Controller Setup and Configuration » Bi-directional Integration Process » External System(s)
The ActiveControl integration framework can be used to perform outbound integration on potentially any external system. Two tables need to be maintained here, table ‘/BTI/TE_INT_SYST’ is the table that holds all the external system id’s and descriptions along…
AC Polling Header
ActiveControl Domain Controller Setup and Configuration » Inbound Integration Polling » AC Polling Header
/BTI/TE_INT_POLH Header for polling items. The RFC destination used comes from /BTI/TE_INT_SYST-INT_PORT EXTSYS_NO Integration system number SEQUENCE_NO sequence POLLURL URL to be polled ROOT root node…
/BTI/TE_INT_PHEA table
New log tables » /BTI/TE_INT_PHEA table
Similar to /BTI/TE_INT_HEAD, stores the integration items processed successfully, in error or to be retried. They will be reported by the notification engine like the others. Created sub-object INTEGRATION_01 for object /BTI/TE: R3TR CDAT APPL_LOG This will enable…
Create sub-object INTEGRATION_01
ActiveControl Domain Controller Setup and Configuration » Inbound Integration Polling » AC Polling Engine » Create sub-object INTEGRATION_01
Go to transaction SLG0 Choose /BTI/TE and click on sub-objects. Click on new entry and create sub-object INTEGRATION_01 and save it.
AC Polling Engine
ActiveControl Domain Controller Setup and Configuration » Inbound Integration Polling » AC Polling Engine
This program is used to poll the external system for new tickets created since the last time the program was run. A variant must be created (and a job scheduled) for the particular external system along with the number of attempts that the program should make to poll…
Introduction
Introduction
This Integration Guide is intended to give the reader an overview of the capabilities of the ActiveControl Integration Engine and the out of the box (OOTB) integration scenarios supported. It also contains detailed technical specifications of the currently available…
Integration Send Engine
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Integration Send Engine
A send program is then scheduled to pick up the mapped transactions and send them out to the configured external systems. It retrieves the required records and then uses the configured send methods for each particular integration scenario to actually push the data out…
Outbound Integration
Integration Architecture » Outbound Integration
The outbound calls from AC to the external ticketing system can all be based on the Deployment Status of a change within AC. Integration scenarios based on AC status changes are delivered as standard with the AC Integration Engine and therefore require no…
Process Identifiers
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Process Identifiers
The standard out of the box integration framework integrates at task level with third party software using task status changes as integration points. A process code will need to be attached to a task deployment or planning status which subsequently needs to be attached…
Filter Values
OTHER CONFIGURATION TABLES » Filter Values
There’s a scenario field in the integration header. If this is set, the trigger program and the DDC and RTC integration classes will ignore some tasks based on this table’s contents. Some old version of the framework will filter out everything unless you…
Integration Process Flow
Integration Architecture » Integration Process Flow
The ActiveControl Integration Framework provides an open architecture for passing messages into and out of the system in a multitude of ways. Although integration can be set up in many ways, one of the more common scenarios is explained in detail below: DevOps…
Inbound Integration
Integration Architecture » Inbound Integration
There are two inbound calls in the above scenario: 1. Creation of the Business Task in AC 2. Approval of Testing/Entry of test results once testing complete Both of these calls would be web service calls to standard AC APIs (although alternative techniques are…
Notification Users
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Notification Users
It is possible to set up ‘Notification Users’ per external system that can be notified when an integration message has gone into an error status. This is run through the Email Notification Engine and the table that needs to be maintained is…
Connector Functionality
Integration Architecture » Connector Functionality
From the standard process flow above, it is envisaged that the developed connector will provide the services required on the ITSM side to initiate a web service call to ActiveControl to create a AC Business Task (which will be the representation of the ITSM ticket…
Integration Trigger Engine
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Integration Trigger Engine
A trigger program should be scheduled to pick up the Task status changes that need to be interfaced to the external system(s). This trigger program selects the appropriate AC records, dependent on the configuration set up above, and passes it through the mapping…
Conversions
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Conversions
The integration framework can also take into account value conversions. For instance where a value in ActiveControl could equal one thing maybe its corresponding value in an external could be different although they both mean the same thing. For example: A AC priority…
Integration with ActiveControl
Introduction » Integration with ActiveControl
ActiveControl offers a variety of ways to integrate inbound and outbound scenarios using documented API’s. ActiveControl provides an Integration Framework that can manage outbound interactions with external systems (including queuing, re-sends, error processing and…
Class List
ActiveControl Domain Controller Setup and Configuration » Bi-directional Integration Process » Class List
The Class is defined from Class Builder section above. SM30 /BTI/TE_INT_CLAS – Integration Object Class List Field Description EXTSYS_NO Main external system identifier, this is the identifier of the system that you wish to…
Integration Architecture
Integration Architecture
The architecture of ActiveControl can be broken down into: client software, a controlling SAP system, other participating SAP systems and integration systems. The diagram below illustrates the central role of the controlling SAP system – referred to as the…
The Domain Controller
Integration Architecture » The Domain Controller
Like the Transport Management System, ActiveControl has the concept of a “domain controller”. The domain controller does not need to be configured in any special way, it is simply the SAP system that the ActiveControl client software connects to and is where…
Update Processes
ActiveControl Domain Controller Setup and Configuration » Bi-directional Integration Process » Update Processes
Currently the integration framework is capable of updating external records in two ways in either ‘Create’ mode or ‘Update’ mode, these ‘modes’ are known within the integration framework as process codes and to try and ensure forwards compatibility these…
Integration Audit Report
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Integration Audit Report
At any time, the Integration Reporting Console can be used to see the status of all integrations, the status and history of each transaction and can also be used to update the underlying transactional data, if required, to fix errors. Program Name:…
The Integration Framework Architecture
Integration Architecture » The Integration Framework Architecture
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…
Notification Logs
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Notification Logs
This is part of the process for enhanced error handling and notifications. /BTI/TE_NOTIF_CU needs to have the Recipients flag set
Notification Recipients
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Notification Recipients
This is part of the process for enhanced error handling and notifications. These users will be notified against specific config values defined in /BTI/TE_NOTIF_CP. /BTI/TE_NOTIF_RE needs to have valid users set up
Notification Connector
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Notification Connector
This is part of the process for enhanced error handling and notifications. The configuration in table /BTI/TE_NOTIF_CP lists the error type to be communicated to the users in above table /BTI/TE_NOTIF_RE. /BTI/TE_NOTIF_CP
Document Audience
Introduction » Document Audience
The intended audience for this document are the technical teams looking to implement integration between ActiveControl and third party tools, such as ticketing systems. It does not detail how AC can be configured to manage the change process and it assumes a…
Trigger Engine Batch Job
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Integration Trigger Engine » Trigger Engine Batch Job
Job for: /BTI/TE_INTEG_TRIGGER A job need to be scheduled via SM36 to run the generation of appropriate items for integration. Program Variant Job Name Frequency Notes /BTI/TE_INTEG_TRIGGER CPS_TE_JIRA_IN …
Send Engine Batch Job
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Integration Send Engine » Send Engine Batch Job
Job for: /BTI/TE_INTEG_SEND A job need to be scheduled via SM36 to run the actual transmission of information via the integration. Program Variant Job Name Frequency Notes /BTI/TE_INTEG_SEND CPS_TE_JIRA_SD …
Audit Report Batch Job
ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process » Integration Audit Report » Audit Report Batch Job
Job for: /BTI/TE_RINTEG_AUDIT A job need to be scheduled via SM36 to run the actual transmission of information via the integration. Program Variant Job Name Frequency Notes /BTI/TE_RINTEG_AUDIT CPS_TE_JIRA_SD …
Inbound Integration
Integration Architecture » Inbound Integration
For inbound integration scenarios AC provides several SOAP web services. Currently, these are: • Create a Business Task • Change a Business Task • Read a Business Task • Analyse a Business Task • Read the results of an analysis for a Business…
Trace for Integration via Proxies
Trace for Integration via Proxies
To find if there is a connection established and data transferred between the active control and the external system via proxies, Go to the transaction code SRT_UTIL and click on the ‘Traces’. Give the user ID that is stored in the calling system and enter, the…