The topic you requested could not be found.
Related topics are listed below.

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…

Integration Header

New log tables » Integration Header

Check in tables /bti/te_int_head SE16

Integration Items

New log tables » Integration Items

/BTI/TE_INT_ITEM Confirms and lists AC Polling Create #1 integration field values mapped, transition # count

Integration Events

New log tables » Integration Events

/BTI/TE_TEVENTS

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…

Integration Scenarios

Integration Architecture » Integration Scenarios

The standard integration scenario is to combine AC 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…

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…

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…

Inbound Integration Polling

ActiveControl Domain Controller Setup and Configuration » Inbound Integration Polling

This document explains the extensions made to the AC integration to cater for polling external systems for changes.

Outbound Integration Process

ActiveControl Domain Controller Setup and Configuration » Outbound Integration Process

This section guides you through the steps that are needed to configure outbound integration within ActiveControl. The Integration configuration is maintained through the SAP standard SM30/31 functions where table entries can be created and updated.

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…

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…

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:…

Troubleshooting Integration Errors

Troubleshooting Integration Errors

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…

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…

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…

Bi-directional Integration Process

ActiveControl Domain Controller Setup and Configuration » Bi-directional Integration Process

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…

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…

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…

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

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.

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

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 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…

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…

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…

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…

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…

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…

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…

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…

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…

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…

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…

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…

ActiveControl Domain Controller Setup and Configuration

ActiveControl Domain Controller Setup and Configuration

This section guides you through the steps that are needed to configure inbound and outbound integration within ActiveControl. The Integration configuration is maintained through the SAP standard SM30/31 transactions where table entries can be created and updated.…

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…

/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…

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…

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.

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…

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…

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…

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…

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.

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.…

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 …

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 …

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.

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…

Class Builder

ActiveControl Domain Controller Setup and Configuration » Bi-directional Integration Process » Class Builder

Create/Activate Integration Classes SE24 CLASS Notes /BTI/TE_CL_INTEG_POLL_JIRA Poll JSON Web service /BTI/TE_CL_INTEGR_CREATE Create Business Task action /BTI/TE_CL_INTEGR_TESTRES Enter test results action…

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…

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…

Inbound Process Flow

Integration Architecture » Inbound Process Flow

The standard inbound integration process flows would be: • Create/Change a Business Task in ActiveControl Creating or changing a Business Task requires simple calls to the appropriate web service. When changing a Task, the current field values should be read first…

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…