Search
Related topics are listed below.
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…
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
Error creating polling parser 01 0000000001
Troubleshooting Integration Errors » Error creating polling parser 01 0000000001
In /BTI/TE_INT_POLF table the field mapping details are incorrect. See section 4.2.3.
Solution 008: Error building inbound structure for integration system [X] polling item [X]
Troubleshooting Integration Errors » Solution 008: Error building inbound structure for integration system [X] polling item [X]
See SLG1 logs for program and error type In /BTI/TE_INT_POLH table the integration system url defined is incorrect. Reference to item 01 is Create and 02 is Update.
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…
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…
Solution 012: Failed to process task [X] for integration system [X] polling item &
Troubleshooting Integration Errors » Solution 012: Failed to process task [X] for integration system [X] polling item &
If a field is marked as mandatory it must be mapped if not then you will get error in the error in SLG1 ● Mandatory field and mapped – no error ● Not Mandatory – no error ● Mandatory and not mapped -error
Config Errors
Troubleshooting Integration Errors » Testing Scenarios » Config Errors
Fields in /BTI/TE_INT_POLF – TEFIELDREF – must be valid If a field is marked as mandatory field it must be mapped if not then you will get error in the error in SLG1 ● Mandatory field and mapped – no error ● Not Mandatory – no…
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
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…
New log tables
New log tables
The following are the main data tables relating to Integration, along with a brief description. Table Description /BTI/TE_INT_PHEA Inbound Integration – Header Logging Information Stores the integration items processed successfully, in…
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:…
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…
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…
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
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…
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
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…
/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…
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…
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…
Solution 002: Connection failed for integration system [x] on port [x]
Troubleshooting Integration Errors » Solution 002: Connection failed for integration system [x] on port [x]
See SLG1 logs for program and error type In /BTI/TE_INT_SYST table define the correct INT_PORT. This port description derives from the HTTP RFC destination created for this integration. See section 4.1 above. For an integrated HTTP call from SAP to a…
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…
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…
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…