Search
Related topics are listed below.
Jenkins User
Integration Setup (Jenkins) » Jenkins User
The integration requires a user in Jenkins that has authorisation to trigger jobs, with an authorization token defined. This user needs a token that will be stored in the SAP RFC Destination as the password.
Outbound Integration
Integration Overview » Technical Solution » Outbound Integration
When transports land in a (configurable) Control Point location, the Jenkins automated testing is triggered via a URL send call. An XML payload contains all information relating to the associated Business Tasks and Transport Forms, including all Custom Field…
Inbound Integration
Integration Overview » Technical Solution » Inbound Integration
When the automated testing cycle completes, Jenkins will report back to ActiveControl whether the testing was a Pass or Fail. Based on that feedback, the Integration will then perform subsequent actions to add a Test Results entry onto the Business Tasks associated…
Integration Components
Integration Overview » Technical Solution » Integration Components
The following components form part of the ActiveControl / Jenkins Integration solution. Summary Notes 1 Remote Function Calls Yes 2 System Users Yes. Both SAP user and Jenkins user 3 …
SAP User
Integration Setup (SAP) » SAP User
A SAP user is required to support the Jenkins 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…
Build Pipeline
Integration Setup (Jenkins) » Build Pipeline
The ActiveControl / Jenkins integration outbound integration works by ActiveControl calling Jenkins pipeline build. Customer Jenkins Administrators would need to setup this Jenkins pipeline for the purpose of the Integration with ActiveControl. This would be used…
Further Information
Further Information
This integration is available from ActiveControl 8.3 onwards. As with all ActiveControl integrations, Basis Technologies would strongly recommend some formal consulting services support in the implementation of the Jenkins integration, so that we can help you with…
Background
Background
ActiveControl includes an out-of-the-box Integration Framework which enables bi-directional integration capabilities with ITSM products such as JIRA, ServiceNow and HPSM and also more recently with DevOps lifecycle tools such as Gitlab. During early 2020, this…
Functional Solution
Integration Overview » Functional Solution
Example Jenkins integration The below workflow diagram describes a potential Jenkins Integration scenario as part of an overall ActiveControl workflow. Figure: Jenkins (and JIRA) integration reflected as part of an end-to-end ActiveControl workflow Key…
/BTI/TE_INT_SYST
Integration Setup (SAP) » SAP Configuration Tables » /BTI/TE_INT_SYST
This configuration table 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 …
Remote Function Calls
Integration Setup (SAP) » Remote Function Calls
An “HTTP Connection to External Server” RFC Destination is required in the ActiveControl Domain Controller to communicate with Jenkins. This is configured via the usual way in SM59. The RFC requires an integration user to be created in Jenkins. Figure: A…
/BTI/TE_INT_PC
Integration Setup (SAP) » 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. As part of Jenkins integration, only CREATE process code is used. This table comes pre-configured as part of ActiveControl, and so should not need to…
/BTI/TE_INT_MAPP
Integration Setup (SAP) » SAP Configuration Tables » /BTI/TE_INT_MAPP
This table is used to define the fields that form part of the Jenkins integration. For the current Jenkins integration, Group and Priority information is sent across as part of the Integration.
Custom Fields
Integration Setup (SAP) » ActiveControl general configuration » Custom Fields
The ActiveControl / Jenkins integration for automated testing relies on Jenkins 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…
/BTI/TE_INT_PROC
Integration Setup (SAP) » SAP Configuration Tables » /BTI/TE_INT_PROC
This table is used within the Integration Framework to define the Process Identifiers that are used within the Integration. As part of Jenkins integration, only CREATE process code is used. However it is a slightly unique use of CREATE, as in most other existing…
/BTI/TE_TVARV
Integration Setup (SAP) » SAP Configuration Tables » /BTI/TE_TVARV
Table /BTI/TE_TVARV is used as part of the Jenkins integration – to configure the trigger URL used as part of the Outbound integration. The entry needs to reference the jenkins trigger URL, which depends on the script name and token: !Note that there is…
Error Logging
Integration Setup (SAP) » Error Logging
Standard SAP logging is possible as part of the Jenkins integration. The prerequisite for this is that the subobject of /BTI/TE is created via transaction SLG0 in the Domain Controller. Note that INTEGRATION_NN, the NN should be the EXTSYST_NO as defined in…
/BTI/TE_INTEG_TRIGGER
Integration Setup (SAP) » Programs » /BTI/TE_INTEG_TRIGGER
The /BTI/TE_INTEG_TRIGGER trigger program is used as part of the Jenkins Integration to select the appropriate ActiveControl records to push out to Jenkins. A Variant should be saved as per screenshot:
/BTI/TE_INT_CLAS
Integration Setup (SAP) » SAP Configuration Tables » /BTI/TE_INT_CLAS
This table 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 integrate with. …
SAP Configuration Tables
Integration Setup (SAP) » SAP Configuration Tables
This section details the configuration tables as part of ActiveControl / Jenkins integration.
Technical Solution
Integration Overview » Technical Solution
The ActiveControl Jenkins integration includes both Outbound and Inbound integrations .
/BTI/TE_INTEG_SEND
Integration Setup (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…
Import Options
Integration Setup (SAP) » ActiveControl general configuration » Import Options
Given 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…
Integration Setup (Jenkins) »
Basic jenkins installation for testing of ActiveControl AC will trigger jenkins calling an URL, like: ```bash AC will not actually use CURL… export triggeruser=acuser export triggerToken=secret # this is a crypto key generated by Jenkins export…
URL scripts
Integration Setup (Jenkins) » URL scripts
Please refer to README file provided with the Integration for some developer Curl examples. Figure: Example of Groovy script used as part of the Integration.