This document outlines the configuration steps required to set up the SAP BTP ABAP Environment (ABAP Cloud) for integration with the ReleaseOwl dashboard. It includes the creation of the service instance, Service Key, Communication Arrangements, and Software Components
1. Prerequisites
To access SAP BTP ABAP Environment (ABAP Cloud), ensure the following:
An active subscription to the ABAP Environment service in SAP BTP.
An ABAP Environment instance created in the relevant subaccount.
Web access enabled with required role collections assigned to users.
2. ABAP Cloud Setup- Step- by- Step Configuration Guide
Step 1: Create a Service Key
After successfully creating the ABAP Environment instance, follow these steps to generate a Service Key:
Log in to the SAP BTP Cockpit.
Navigate to your Subaccount → Instances and Subscriptions.
Select the created ABAP Environment instance.
Go to the Service Keys section.
Click Create Service Key.
Provide a name for the service key and click Create.
Step 2: Create Communication Keys
Communication keys must be created for the required communication scenarios in the ABAP Environment instance.
Follow the steps below:
Navigate to your ABAP Environment instance in the SAP BTP Cockpit.
Select the Service Keys section.
Click Create Service Key.
Provide the required JSON configuration for the communication scenario.
Click Create to generate the service key.
Service Key for Software Component Integration (SAP_COM_0510)
Use the following JSON configuration:
Service Key for ABAP Unit Test Integration (SAP_COM_0735)
Similarly, create the service key for ABAP Unit Test Integration using the following JSON configuration:
Alternative Method: Create Communication Arrangements in ABAP Cloud
Communication arrangements can also be created directly in the ABAP Cloud system for the required communication scenarios.
Log in to the ABAP Cloud system.
Navigate to Administration → Communication Arrangements.
Select the Communication Scenario:
SAP_COM_0510 – Software Component Test Integration
In the Common Data section:
Enter an Arrangement Name.
In the Communication System field, click New to create a new system.
Create Communication System
Enter a System ID and Name (as per naming convention).
Click Create to generate the Communication System.
Create User for Outbound Communication
Under Outbound Communication, click the “+” (Add) button.
User Name (as per naming convention)
Password (define a secure password of your choice, following your organization’s password policy)
Click Save to complete the arrangement setup.
Create Communication Arrangement for ABAP Unit Test Integration (SAP_COM_0735)
Repeat the same process for ABAP Unit Test Integration:
Go to Communication Arrangements.
Select Communication Scenario:
SAP_COM_0735 – ABAP Unit Test Integration
In the Common Data section:
Enter an Arrangement Name.
In the Communication System field, click New to create a new system.
Enter a System ID and Name (as per naming convention).
Click Create to generate the Communication System.
Create User for Outbound Communication
Under Outbound Communication, click the “+” (Add) button.
Enter:
User Name (as per naming convention)
Password (define a secure password of your choice, following your organization’s password policy)
Click Save to complete the arrangement setup.
Verification of Service Details
Once the communication arrangements (SAP_COM_0510 and SAP_COM_0735) are successfully created and activated, the corresponding service details can be verified in the Service Key generated for the ABAP Environment service instance.
3. Manage Software Components
Step 3: Create Software Component
In the ABAP Cloud system, navigate to Manage Software Components.
Software Component Name (as per naming convention)
Repository URL (Git Repository URL)
Step 5: Clone the Software Component
After creating the Software Component:
Select the created Software Component.
Personal Access Token (PAT)
Select the required Branch to clone.
The software component is now connected to the Git repository and ready for ReleaseOwl-based deployment.
Once the above setup is completed, the system will be ready for integration through ReleaseOwl.