Search
Related topics are listed below.
GitLab Integration
GitLab Integration
Example GitLab integration The below workflow diagram describes a potential GitLab Integration scenario as part of an overall ActiveControl workflow. A JIRA integration is also depicted in this example. Figure: Potential Gitlab (and JIRA) integration reflected…
Integration Setup (GitLab)
Integration Components » Outbound Integration » Integration Setup (GitLab)
The ActiveControl / GitLab integration outbound integration works by ActiveControl calling GitLab Customer GitLab Administrators would need to setup GitLab for the purpose of the Integration with ActiveControl. This would be used to as part of the ActiveControl…
GitLab User
Integration Components » Outbound Integration » Integration Setup (GitLab) » GitLab User
A system user is required in GitLab to support the integration The nature of this User will depend on the requirements and final Integration solution.
Inbound Integration
Integration Components » Inbound Integration
When the automated testing cycle completes, Gitlab will need to report back to ActiveControl whether the testing was a Pass or Fail. Typically the following activities will happen as part of Gitlab automated testing Inbound integration: 1. GitLab pipeline…
Integration Components
Integration Components
The following components form part of the ActiveControl / Gitlab Integration solution. Summary Notes 1 Remote Function Calls None 2 System Users Refer to here 3 Number Range …
ActiveControl Integration Framework
ActiveControl Integration Framework
ActiveControl Domain Controller 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…
SAP User
Integration Components » Outbound Integration » SAP User
A SAP user is required to support the Gitlab Integration. The Integration could potentially use the existing AC_BATCH user, however given that this User is what the Test Results will be signed off against as part of the Integration – most customers might prefer…
Document Purpose
Document Purpose
Introduction ActiveControl includes an out-of-the-box Integration Framework which has enabled bi-directional integration capabilities with ITSM products such as JIRA, ServiceNow and HPSM for many years. More recently, this Integration Framework has evolved to also be…
/BTI/TE_INT_SYST
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_INT_SYST
Table /BTI/TE_INT_SYST is used to specify the integrations that are running, and also some key information relating to the integration. It is possible to run multiple Integrations as part one ActiveControl implementation. Field Explanation …
Pre-Requisites
Integration Components » Pre-Requisites
The following are pre-requisites for setting up the ActiveControl integration with Gitlab. It should be noted that these setup activities are the responsibility of the Customer team; Basis Technologies do not have expertise in GitLab. 1. Install GIT A…
Custom Fields
Integration Components » Outbound Integration » ActiveControl General Configuration » Custom Fields
The ActiveControl / Gitlab integration for automated testing relies on GitLab being able to tell the testing tool what automated tests need to be performed. In most scenarios, this is best done by the user (ie a Developer or Tester) manually indicating on the the…
Further Information
Further Information
As detailed earlier in this Integration Guide, the ActiveControl / Gitlab integration is not an out-of-the-box ‘plug it and play’ Integration in the sense of many of the more established and mature ActiveControl integrations such as JIRA and ServiceNow. It…
/BTI/TE_INTEG_TRIGGER
Integration Components » Outbound Integration » SAP Programs » /BTI/TE_INTEG_TRIGGER
The /BTI/TE_INTEG_TRIGGER trigger program is used as part of the Gitlab Integration to select the appropriate ActiveControl records to push out to Gitlab. This program would be scheduled as a variant to run every 5-10 minutes, to push the latest payload out to…
/BTI/TE_RNOTIFICATION_ENGINE
Integration Components » Outbound Integration » SAP Programs » /BTI/TE_RNOTIFICATION_ENGINE
ActiveControl includes a standard Notification Engine to notify the appropriate stakeholders at the appropriate time in the workflow. These notifications are switched on/off via program /BTI/TE_RNOTIFICATION_ENGINE in the Domain Controller, and scheduled to run as a…
Error Logging
Integration Components » Error Logging
Standard SAP logging is possible as part of the Gitlab integration. The prerequisite for this is that the subobject of /BTI/TE is created via transaction SLG0 in the Domain Controller. Example configuration * For INTEGRATION_NN, the NN should be the EXTSYST_NO as…
/BTI/TE_INT_PC
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_INT_PC
Table /BTI/TE_INT_PC details the process codes that are available as part of the Integration Integration Framework. Field Description PROCESS_CODE The process codes used by the integration framework to perform some kind of action. The…
/BTI/TE_INT_MAPX
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_INT_MAPX
Fields to be mapped for some json fields have to be set in table /BTI/TE_INT_MAPX in the ActiveControl Domain Controller SAP system /BTI/TE_INT_MAPX can be used to send over Custom Field numbers to Gitlab, which may be needed for processing on the receiving end, as…
/BTI/TE_GITLABBR
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_GITLABBR
GitLab Branch Repositories are configured in table /BTI/TE_GITLABBR Field Description EXTSYS_NO Integration System Number [as defined in /BTI/TE_INT_SYST] ProjectID Is the ActiveControl project ID assigned to the…
/BTI/TE_INT_PROC
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_INT_PROC
Table /BTI/TE_INT_PROC is used within the Integration Framework to define the Process Identifiers that are used within the Integration. Field Description EXTSYS_NO Integration system number (as configured in /BTI/TE_INT_SYST …
/BTI/TE_TVARV
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_TVARV
Clone or pull the SAP GitLab Repository to the SAP application server and configure the file path(the file containing peer review information to be pushed in gitlab repo) in table /BTI/TE_TVARV with variant variable TE_GIT_FILE The batch template attached for…
Import Options
Integration Components » Outbound Integration » ActiveControl General Configuration » Import Options
As the Outbound integration is triggered by transports being imported into a system and landing in the Test Queue, it is advisable to DISABLE the following target configuration option: Continue importing transport requests when an import error occurs It is also…
/BTI/TE_INT_CLAS
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_INT_CLAS
Table /BTI/TE_INT_CLAS is used to define Integration(s) and their corresponding Class; the classes are the bulk of the integration processing is done. The ActiveControl integration works on the principle of having a class for each external system that we need to…
/BTI/TE_INT_USR
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_INT_USR
Within the ActiveControl integration framework, 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…
/BTI/TE_INT_MAPP
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_INT_MAPP
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…
/BTI/TE_RF
Integration Components » Outbound Integration » SAP configuration tables » /BTI/TE_RF
Number range for object /BTI/TE_RF needs to be setup in the TE Domain Controller via SNRO for the Integration Framework to operate. Example configuration
/BTI/TE_INTEG_SEND
Integration Components » Outbound Integration » SAP Programs » /BTI/TE_INTEG_SEND
The /BTI/TE_INTEG_SEND send program is used 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…