Onboarding Guide

• WHINT provisions and manages the SAP BTP subaccount

• You expose systems to the WHINT account (e.g. via Cloud Connector or Reverse Proxy)

• WHINT sets up and maintains the Integration Cockpit

• You receive user access to the cockpit instance

• Best for: Fast onboarding with minimal internal effort

• Who sets it up: WHINT Support

• Notes: You provide the BTP service instance and client credentials

• You own the BTP subaccount

• WHINT deploys and configures the Integration Cockpit

• All connectivity remains inside your landscape

• You manage user roles and access in BTP

• Connect your own PostgreSQL database instance

• Best for: Data sovereignty with vendor-managed cockpit setup

• Who sets it up: WHINT (with your BTP access)

• Notes: You provide the BTP service instance and client credentials

SAP BTP Subaccount Configuration

Once the Integration Cockpit is deployed to SAP BTP Cloud Foundry, complete these essential configurations. These steps are required only once after your first deployment to ensure secure connectivity and proper authentication.

SAP Single Sign-On (SSO)

Enable SSO using SAP's XSUAA service for authentication.

Create XSUAA Service Instance

1. In your SAP BTP Cockpit, go to your subaccount

2. Navigate to Services → Service Marketplace

3. Search for Authorization and Trust Management Service

4. Click Create and select:

   • Service: Authorization and Trust Management Service

   • Plan: application (required for SSO functionality)

   • Instance Name: Choose a descriptive name (e.g. whint_xsuaa_sso)

Configure the instance:

1. On the Parameters step, upload or paste your xs-security.json configuration file

2. This file defines the security scopes and role templates for your application

3. Click Next → Create

The XSUAA instance is now created and visible in your service instances list.

Note: Append the redirect-uris if you are using a custom identity provider instead of the SAP default IDP. For example:

CODE

...
      "redirect-uris": [
          "https://**.cfapps.eu10-004.hana.ondemand.com/**",
          "https://**.cfapps.eu10-004.hana.ondemand.com/user/login/callback**",
          "https://**.accounts.ondemand.com*",
          "https://login.microsoftonline.com*",
          "<more>..."
      ],
...

Bind to Application

Create the application binding to enable SSO:

1. In the same XSUAA service instance, navigate to Bound Applications tab

2. Click Create under the bound applications list

3. In the creation wizard:

   • Step 1 - Basic Info:

     • Application: Select whintic-<name> from the dropdown

     • Keep other defaults

   • Step 2 - Parameters:

     • Paste the same xs-security.json configuration

   • Step 3 - Review:

     • Review your configuration

4. Click Create

The binding appears in the Bound Applications list with status Created.

Restart Application

For SSO to take effect:

1. Navigate to your WHINT Integration Cockpit application

2. Go to Overview

3. Click Restart

4. Wait for the application to fully restart (status changes to Started)

Users can now authenticate using SAP SSO when accessing the Integration Cockpit.

Microsoft Single Sign-On (SSO)

Enable users to authenticate with their Microsoft Azure AD credentials.

Update User-Provided Variables

1. In your SAP BTP Cockpit, navigate to your subaccount

2. Go to Cloud Foundry → Spaces → Select your space

3. Find your WHINT Integration Cockpit application

4. Click User-Provided Variables in the left menu

5. Select WHINTIC and click edit

6. Add or update the auth_providers section:

auth_providers:
  - name: "azureadv2"
    display_name: "Microsoft"
    client_id: "<your-azure-ad-client-id>"
    secret: "<your-azure-ad-client-secret>"
    callback_url: "<your-wic-route>/user/login/callback"
    scopes:
      - "https://graph.microsoft.com/.default"
    tenant: "<your-azure-ad-tenant-id>"

Replace the placeholders:

• <your-azure-ad-client-id>: Your Azure AD application client ID

• <your-azure-ad-client-secret>: Your Azure AD application secret

• <your-wic-route>: Your WIC application URL (e.g. https://wic-app.cfapps.eu10.hana.ondemand.com)

• <your-azure-ad-tenant-id>: Your Microsoft tenant ID

6. Click Save

7. Restart the application for changes to take effect:

   • Go to Overview in the application menu

   • Click Restart

Find your WIC route under the application's Routes section in the BTP Cockpit. Copy the full URL including https://.

Test SSO Authentication

For Microsoft SSO:

1. Log out of the Integration Cockpit

2. On the login page, you should see a Microsoft login option

3. Click it and authenticate with Azure AD credentials

4. You should be redirected back to the Integration Cockpit dashboard

For SAP SSO:

1. Access the Integration Cockpit URL

2. SSO should automatically authenticate you based on your SAP session

3. If prompted, log in with your SAP credentials

If SSO isn't appearing, clear your browser cache and ensure you restarted the application after configuration changes.

SAP Cloud Connector

Create a connectivity service in the BTP Cockpit

Create a new “Connectivity Service” Instance.

After creation select the new instance and create a new binding.

The information and credentials from this JSON file (e.g. clientid, clientsecret, url, onpremise_proxy_host+onpremise_proxy_port) are used to create a Proxy configuration in the Integration Cockpit.
For detailed instructions, see: Proxies - SAP Cloud Connector Integration

Create a technical user in your connected ABAP or Java stack. Assign the following roles:

• SAP_XI_API_DISPLAY_J2EE

• SAP_XI_APPL_SERV_USER

• SAP_XI_MONITOR_J2EE

• SAP_PI_B2B_TPM_ADMIN

1. Create a technical user and assign the role SAP_XI_APPL_SERV_USER (or the equivalent authorization object):

2. Grant RFC authorizations in object S_RFC:

3. External Services Check:

4. Grant table authorizations in object S_TABU_NAM:

5. Grant Messaging Monitoring authorizations:

See Section 1.1.1 – SAP Integration Suite → SAP Event Mesh: Instance Creation And Service Key Retrieval

Event Mesh in SAP Integration Suite (EMIS) is currently not supported.

SAP Cloud Connector: Expose Backend

Set up the SAP Cloud Connector to securely link the Integration Cockpit with your on-premise SAP ABAP systems (e.g. ECC, S/4HANA).

You can choose between two connectivity options based on your deployment scenario:

• HTTP(S)

• RFC and HTTPS

HTTPS

Services to be allowed in SAP Cloud Connector (HTTPS)

• /sap/bc/soap/rfc

• /sap/opu/odata/IWFND/catalogservice

Applicable Deployment Models

This configuration applies to the following connectivity options:

• 1.1.1 - WHINT-hosted in WHINT BTP subaccount, direct connection via SOAP-RFC + HTTPS

• 1.2.1 - WHINT-hosted in WHINT BTP subaccount, via SAP Cloud Integration (CPI) and SOAP-RFC + HTTPS

• 2.1.1 - Customer-managed in own BTP subaccount, direct connection via SOAP-RFC + HTTPS

• 2.2.1 - Customer-managed in own BTP subaccount, via SAP Cloud Integration (CPI) and SOAP-RFC + HTTPS

SAP generally does not recommend using SOAP-RFC.
However, providing a user with clearly limited access rights is acceptable.
Check SAP Note 131403 for security considerations.

RFC and HTTPS

Function Modules to be allowed in SAP Cloud Connector (RFC)

• RFC_READ_TABLE

• SXMB_GET_MESSAGE_LIST

Services to be allowed in SAP Cloud Connector (HTTPS)

• /sap/opu/odata/IWFND/catalogservice

Applicable Deployment Models

This configuration applies to the following connectivity options:

• 1.2.2 - WHINT-hosted in WHINT BTP subaccount, via SAP Cloud Integration (CPI) and RFC + HTTPS

• 2.2.2 - Customer-managed in own BTP subaccount, via CPI and RFC + HTTPS

For additional details, see:
How to Connect SAP ABAP Backends to Integration Cockpit

Deployment Options

SAP Cloud Connector: Create User

This step is only needed when you want to create your Cloud Connector as Data Source in the Integration Cockpit.

Create a named user with display-only rights before configuring the Cloud Connector as a data source.

Create User with Display-Only Rights

Option 1: Via LDAP (SAP Help Portal)

Option 2: Manually edit users.xml

Add a new user with username Display and role sccdisplay to grant read-only access.

Generate SHA256 password hash:

1. Use a SHA256 hash generator (SHA256 Generator or any SHA256 tool)

2. Convert your clear text password to SHA256 format

3. Paste the generated hash into the password attribute

Edit users.xml File

File Location: <scc_installation_path>/config/users.xml
Example paths:

• Linux: /opt/sap/scc/config/users.xml

• Windows: C:\SAP\scc\config\users.xml

Add the Display user entry:

<?xml version='1.0' encoding='utf-8'?>
<tomcat-users xmlns="http://tomcat.apache.org/xml"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://tomcat.apache.org/xml tomcat-users.xsd"
              version="1.0">
  <role rolename="admin"/>
  <group groupname="initial" roles=""/>
  <user username="Administrator" password="<EXISTING_SHA256_HASH>" groups="" roles="admin"/>
  <user username="Display" password="<YOUR_SHA256_HASH_HERE>" groups="" roles="sccdisplay"/>
</tomcat-users>

Important:

• The password attribute contains the SHA256 hash, not clear text

• Keep the Administrator user entry unchanged (pre-existing hashed password)

• Only add or modify the Display user with your generated SHA256 hash

Next Step:

• Customer Self-Managed: Use the Display username and clear text password when configuring the data source

• WHINT-Hosted: Use service binding credentials from your SAP CPI tenant

Create new entry for SAP Cloud Connector

This step is only needed when you want to create your Cloud Connector as Data Source in the Integration Cockpit.

Add an entry into your SAP Cloud Connector to allow calls from your CPI tenant (subaccount)

The access policy have to be set to “Path And All Sub-Paths”, to grant access for the connection from the WHINT Integration Cockpit.

Assign the following role collections to your technical user (S-User):

• IntegrationOperationServer.read

• AuthGroup.IntegrationDeveloper

• AuthGroup.Administrator

Assign the following role collections to your technical user (S-User):

• PI_Integration_Developer

• PI_Administrator

You can also select read-only roles if you don´t like to give full access.

See Section 1.1.5 Microsoft Azure → Microsoft Azure [Service Key Retrieval]

For Atlassian Jira and Confluence, you will use an API user or token.

See Section 1.3 Jira & Confluence → API Access Token Setup (Jira & Confluence)

This quick guide provides a general overview for setting up Data Sources when credentials (e.g. service keys or tokens) are already available.

In this example, it focuses primarily on SAP BTP services such as Cloud Integration, Event Mesh, and API Management.

For other platforms or if additional setup guidance is required, refer to the platform-specific instructions in the sections below.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

• Name: Enter a clear identifier
  (PLATFORM]_[REGION] → e.g. CPI_EU)

• Type: Select the data source type:

  • e.g. SAP_BTP (Cloud Integration), SAP_PO, etc.

• Environment: Choose the environment classification:

  • DEVELOPMENT, TEST, QUALITY or PRODUCTION

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with your credentials:

• Connection Details:

  • Features: Select one or more: Complexity, Adapter, Authentication, Last Traffic, etc.

  • Product: Select one or more: API MANAGEMENT, CLOUDINTEGRATION, EVENTMESH, INTEGRATIONASSESSMENT

• Region: Example: EU10

• Hostname: without http(s)://
  Example: wxxxx.it-cpixxx.cfapps.euxx-xxx.hana.ondemand.com

Authentication

• Type: Choose from: ACCESSTOKEN, APIKEY, BASICAUTH, OAUTH2and enter your credentials

2. Click “Save” to complete data source creation.

This example is specific to SAP BTP.
Fields like Region, Token URL or Product may not apply to other systems such as Jira, ABAP or Azure.
Always follow the system-specific instructions provided below.

Step 1: Add Scheduled Tasks

To schedule jobs for a Data Source:

1. Open the Data Source.

2. Click “+” Add Task.

3. Choose the Task Type and set the recurrence:

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent process overlap. Note that the CONFIGURATION task may require additional runtime.

4. Click “Save” to confirm.

Quick Task Setup Overview

• SAP_BTP, ABAP, Azure → Use Configuration + Inventory + Runtime

• Jira → Use Configuration only

• Confluence → Use Update only

Step 2: Run Tasks Manually

You can manually execute any task to validate access, credentials and data structure before scheduling regular runs.

• Select the checkbox next to the task you want to run.

• Click “Start Task” to trigger immediate execution.

• Use the “Logs” section to monitor execution details or troubleshoot errors.

• Use the “Job Monitor” section to verify successful completion of each Task.

Sequential Task Execution with Completion Check
Execute each task one after the other in the specified order.
After each task, use the Job Monitor to confirm it has successfully finished before continuing.

Example Order:

1. SAP_BTP

2. Configuration → Check Job Monitor

3. Inventory → Check again

4. Runtime

For further clarification on, see Step 3: Job Monitor below.

Step 3: Job Monitor

Check “Job Monitor” for execution results:

• Green – Success (see “Last Run”)

• Red – Failure (check “Logs”)

If you have running tasks you see them under “Active Tasks”:

Before retrieving your service key, ensure that API Management, API Portal is available as an entitlement in your SAP BTP Subaccount.

If not, follow the steps below before continuing.

Step 1: Check Service Entitlements

1. Open your SAP BTP Subaccount.

2. Navigate to Entitlements.

3. Ensure the following service is added:

   • Service: API Management, API Portal

   • Plan: apiportal-apiaccess

→ If missing, click “Add Service Plan” and assign it before proceeding.

Step 2: Check the Service Marketplace

1. In your BTP Subaccount, go to Service Marketplace.

2. Search for:

   • Service: API Management, API Portal

   • Plan: apiportal-apiaccess

→ If already available, proceed to Step 3.
→ If not, ensure the entitlement (Step 1) was added.

Step 3: Create a New Service Instance

1. Select API Management, API Portal in the Service Marketplace.

2. Click “Create” (instance).

3. Configure the instance:

   • Plan: apiportal-apiaccess

   • Space: e.g. dev

   • Instance Name: e.g. WHINT_APIM

4. Confirm with “Create”
   

   

Step 4: Create and Retrieve the Service Key

1. Select your newly created API Management instance.

2. Click “Create Service Key”.

3. Enter a name, e.g. WHINT_APIM_KEY and confirm.

4. Click “View” to display the credentials.

4. Extract the following OAuth2 values for later use:

• clientid

• clientsecret

• url

• tokenurl

→ Continue to Data Source setup below.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. WHINT API Management

   • Type: SAP_BTP

   • Category: e.g. DEVELOPMENT

     

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained earlier:

Connection Details

• Features: Check all applicable (e.g. Complexity, Adapter, Authentication, Timing, etc.)

• Product: Select APIMANAGEMENT

• Region: e.g. EU10

• Proxy: not required

Authentication

• Type: Select OAUTH2 and enter the credentials from the Service Key

  • Client ID: Enter from the Service Key → clientid

  • Client Secret: Enter from the Service Key → clientsecret

  • Token URL: Enter from the Service Key → tokenurl

  • Scope: not required

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • Configuration

   • Inventory

   • Runtime

     

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. RUNTIME - Reads traffic information from the tenant

3. INVENTORY - Pushes the raw data into the inventory

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

Before retrieving your Service Key, ensure that a SAP Process Integration Runtime service instance with the api plan exists in your SAP BTP Subaccount.

If not, follow the steps below before continuing with Step 4: Create and Retrieve the OAuth2 Service Key.

Step 1: Check the Service Marketplace

1. Open your SAP BTP Subaccount.

2. Navigate to Service Marketplace.

3. Search for:
   Service: SAP Process Integration Runtime
   Plan: api

→ If the service instance already exists, proceed to Step 3.
→ If not, continue with Step 2 to create it.

Step 2: Create a New Service Instance

1. In Service Marketplace, select SAP Process Integration Runtime.

2. Click “Create” (to create an instance).

2. Configure as follows:

   • Plan: api

   • Space: e.g. dev

   • Instance Name: e.g. WHINT_CLOUD_INT

Step 3: Assign Roles

1. In the Roles section, select the following authorizations:

• AuthGroup_Administrator

• AuthGroup_IntegrationDeveloper

• AuthGroup_BusinessExpert

2. Click “Create” to finalize the instance.

4. Create And Retrieve Service Key

1. In your created service instance, select “Create Service Key”.

2. Enter a name (e.g. WHINT_CLOUD_KEY) and confirm.

3. After creation, click “View” to display the credentials.

4. Extract the following OAuth2 values for later use:

• clientid

• clientsecret

• url

• tokenurl

→ Continue to Data Source setup below.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. CPI_CF

   • Type: SAP_BTP

   • Environment: e.g. Production

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained earlier:

• Features: Check all applicable (e.g. Complexity, Adapter, Authentication, Timing, etc.)

• Product: Select CLOUDINTEGRATION

• Region: e.g. EU10

• Hostname: from Service Key url without http(s)://

• Optional:

  • Store Artefact ID in Property:

  • Filtered ID for E2E Generation: e.g. Generic_EOIO_Receiver|de.whint.wic.alert

  • Proxy: not required

Authentication

• Type: Select OAUTH2 (recommended) and enter the credentials from the Service Key

  • Client ID: Enter from the Service Key → clientid

  • Secret: Enter from the Service Key → clientsecret

  • Token URL: Enter from the Service Key → tokenurl

  • Scope: not required

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • Configuration

   • Inventory

   • Runtime

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. INVENTORY - Pushes the raw data into the inventory

3. RUNTIME - Reads traffic information from the tenant

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. CPI_EU

   • Type: SAP_BTP

   • Environment: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained earlier:

• Features: Check all applicable (e.g. Complexity, Adapter, Authentication, Timing, etc.)

• Product: Select CLOUDINTEGRATION

• Region: e.g. EU10

• Hostname: from Service Key url without http(s)://

• Optional:

  • Store Artefact ID in Property: e.g. LeanIX External ID

  • Filtered ID for E2E Generation: e.g. Demo_trigger_1|de.whint.ims.test.trigger

  • Proxy: not required

Authentication

• Type: Select OAUTH2 (recommended) or BASICAUTH and enter the credentials from the Service Key

  • Client ID: Enter from the Service Key → clientid

  • Client Secret: Enter from the Service Key → clientsecret

  • Token URL: Enter from the Service Key → tokenurl

  • Scope: not required

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • Configuration

   • Inventory

   • Runtime

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. INVENTORY - Pushes the raw data into the inventory

3. RUNTIME - Reads traffic information from the tenant

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

Before retrieving your Service Key, ensure that the Integration Assessment service is entitled and available in your SAP BTP subaccount. ㅤㅤㅤ

If not, follow the steps below before continuing with Service Key retrieval.

Step 1: Check Service Entitlements

1. Open your SAP BTP Subaccount.

2. Navigate to Entitlements.

3. Confirm that the following service is added:

   • Service: Integration Assessment

   • Plan: default

→ If not present, click “Add Service Plan” and assign the entitlement.

Step 2: Check the Service Marketplace

1. In your BTP Subaccount, go to Service Marketplace.

2. Search for:

   • Service: Integration Assessment

   • Plan: default

If the service is not visible, double-check that the entitlement was added in Step 1.

Step 3: Create a Service Instance

1. Click “Create” (instance).

2. Use the following settings:

   • Plan: default

   • Space: e.g. dev

   • Instance Name: e.g. WHINT_IA

3. Click “Create” to finalize the instance

Step 4: Create and Retrieve the OAuth2 Service Key

1. After the instance is created, open it and select “Create Service Key”.

2. Enter a name, e.g. WHINT_IA_KEY and confirm.

3. Click “View” and extract the following values:

• clientid

• clientsecret

• tokenurl

• url

→ Continue to Data Source setup below.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. SAP IntegrationAssessment

   • Type: SAP_BTP

   • Category: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained earlier:

Connection Details

• Features: Check all applicable (e.g. Complexity, Adapter, Authentication, Timing, etc.)

• Product: Select INTEGRATIONASSESSMENT

• Region: e.g. EU10

• Proxy: not required

Authentication

• Type: Select OAUTH2 and enter the credentials from the Service Key

  • Client ID: Enter from the Service Key → clientid

  • Client Secret: Enter from the Service Key → clientsecret

  • Token URL: Enter from the Service Key → tokenurl

  • Scope: not required

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • Configuration

     

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Result

Your data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

Before retrieving your Service Key, ensure that a (SAP) Event Mesh service instance with the default plan exists in your SAP BTP Subaccount.

If not, follow the steps below before continuing with Service Key Retrieval.

Step 1: Check the Service Marketplace

1. Open your SAP BTP Subaccount.

2. Navigate to Service Marketplace.

3. Search for:

   • Service: Event Mesh

   • Plan: default

→ If not, continue with Step 2 to create it

Step 2: Create a New Service Instance

1. In Service Marketplace, select Event Mesh.

2. Click “Create” (to create an instance).

3. Configure the instance with the following:

• Plan: default

• Space: e.g. dev

• Instance Name: e.g. WHINT_EM

3. In the Parameters section, insert the following JSON:

{
"options": {
"management": true,
"messagingrest": true,
"messaging": true
},
"namespace": "whint/em/test",
"rules": {
"topicRules": {
"publishFilter": [
"${namespace}/"
],
"subscribeFilter": [
"${namespace}/"
]
},
"queueRules": {
"publishFilter": [
"${namespace}/"
],
"subscribeFilter": [
"${namespace}/"
]
}
},
"version": "1.1.0",
"emname": "embroker"
}

Replace "whint/em/test" with your actual namespace if needed.

4. Retrieve the Service Key

1. Select your newly created (SAP) Event Mesh instance.

2. Click Create Service Key.

3. Enter a name, e.g. WHINT_EM_KEY and confirm.

4. After creation, click “View” to display the credentials.

5. Extract the following values for later use:

   • clientid

   • clientsecret

   • tokenendpoint

   • uri

→ Now continue to the Data Source setup below.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. SAP EVENT MESH

   • Type: SAP_BTP

   • Category: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained earlier:

Connection Details

• Features: Check all applicable (e.g. Complexity, Adapter, Authentication, Timing, etc.)

• Product: Select EVENTMESH

• Region: e.g. EU10

• Hostname: without http(s):// (e.g. xxxxx.it-cpi0xx.cfapps.eu10-005.hana.ondemand.com)

• Proxy: not required

Authentication

• Type: Select OAUTH2 and enter the credentials from the Service Key

  • Client ID: Enter from the Service Key → clientid

  • Client Secret: Enter from the Service Key → clientsecret

  • Token URL: Enter from the Service Key → tokenurl

  • Scope: not required

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • Configuration

   • Inventory

   • Runtime

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. INVENTORY - Pushes the raw data into the inventory

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Prerequisites: Complete the Connectivity via Basic Authentication section above before proceeding with data source configuration.

Note: The configuration varies depending on your deployment model:

• a) WHINT-Hosted: Connection through WHINT-provided Integration Flow gateway (SAP Cloud Integration)

• b) Customer Self-Managed: Direct connection to your Cloud Connector

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click "+" Add.

   

3. Enter the required values:

   • Name: e.g. SCC CC

   • Type: SAP_BTP

   • Environment: e.g. TEST

4. Click "Save".

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained earlier:

Connection Details

a) For WHINT-Hosted (Gateway Connection):

• Product: CLOUDCONNECTOR

• URL: https://<btp-region>.hana.ondemand.com/http/whint/wic/scc (from your SAP Cloud Integration Flow)

• Proxy: Leave blank (gateway handles routing)

Note: For WHINT-hosted deployments, the gateway Integration Flow (WHINT WIC SCC Gateway) is provided as part of the WHINT Integration Package.
Here you configure your URL to your Cloud Connector.

b) For Customer Self-Managed (Direct Connection):

• Product: CLOUDCONNECTOR

• URL: http://<your-scc-host>:<port>
  (e.g. http://winwpo.scc:8443)

• Proxy: Select your configured proxy from the dropdown
  (e.g. SAP CloudConnector CSCC)

Note: For customer self-managed deployments, Proxy must be configured in
Settings → Connectivity → Proxies before they can be selected here.

Authentication

a) WHINT-Hosted:

• Type: Select BASICAUTH or OAuth2

• Username: Service binding username (from your SAP CPI tenant)

• Password: Service binding password (from your SAP CPI tenant)

b) Customer Self-Managed:

• Type: Select BASICAUTH

• Username: Enter your Cloud Connector username (e.g. Display)

• Password: Enter the corresponding clear text password

2. In the Tasks section, click the "+" icon (top right of the table) to add the following tasks:

   • Configuration

3. Click "Save" to complete data source creation.

Step 3: Task Configuration

1. Start the task "CONFIGURATION" by selecting the checkbox next to it and clicking the "Start Task" icon.

   

2. Check your "Job Monitor" if the task is done or is still running under "Active Tasks".

Recommended Task Schedule

Result

Your data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

SAP PI/PO is an on-premise system and uses basic authentication.

See Platform-Specific Role Setup → SAP Process Orchestration (PI/PO) for required user roles.

Configuration Scenario in PO System

Set up the configration scenario in SAP PI/PO.

After the import of the files to the directory, go to the scenario “WHINT_Integration Cokpit”.

Copy all objects from the component “SAP_PO” to your own PI/PO component or create “SAP_PO” as component if no other exists.

Then start the configuration with the channels before configuring the ICOs.

Communication Channels

Sender Channel

These are used to start the process for both ICOs

Both can be used, and select the right one for your preferences.

SOAP_S

No Configuration needed

SOAP_S_BE

No Configuration needed

Receiver Channel

The different receiver channels are used for reading for collecting the data and send it our to the WIC.

SOAP_R

This is a dynamic channel and will be used and set dynamically during the data collection.

1. Configure “http://” or “https://” for Target URL:

   

2. Set up user and passwort at “Parameters → Advances” in the first key-value pair.

   

3. In the tab “Module”, set the values as shown in the picture

   

   Please change the value of the 2nd line in the lower table from”WHINT_IFM” to the user name which is used for authorization.

SOAP_R_Access

1. Set Target URL and Authentication in the tab “General”

   

   For the target url, the url from the description can be used.
   You have to replace “http://localhost:50000” with your host and port.
   

HTTP_R_NWDS (optional)

This channel is optional and only used to export the NWDS Folders for the WIC.

1. Configure Destination Details, Authentication and Request Details

   

WHINT | IntegrationCockpit | HTTP_R

1. Configure destination details and authentication
   

   

    

   1. Destination details:
      Use the URL from the WIC data source to set up the details.

   2. Authentication
      Use the username and password you generated in the data source of the cockpit.

Integrated Configurations

IntegrationDirectoryAccess

Configure the parameter in the tab “Receiver Interfaces”

Parameter:

• URL: Hosturl

MessageTriggerRequest_Out || IntegrationDirectory

For sender channel, use one of the SOAP_S Channels above.

Set up the parameters of the Operation Mappings in the tab “Receiver Interfaces”.

Parameter:

• SOAP_ICO: | SAP_PO | SOAP_R_Access

• HTTP_HMI: SAP_PO:HTTP_R_NWDS

If you don’t use NWDS you can set “IGNORE” for HTTP_HMI parameter. Then this will be ignored.

In Outbound Processing set the Receiver Channel to HTTP_R for all.

MessageTriggerRequest_Out || PerformanceMonitoring

For Inbound and Outbound Processing set the same channels as in the ICO for Integration Directory.

• Sender: SOAP_S

• Receiver: HTTP_R
  

Set up the parameters of the Operation Mappings in the tab “Receiver Interfaces”.

Parameter:

• Authroization: Basic Auth Header

• URL: Hosturl + “/mdt/performancedataqueryservlet”

MessageTriggerRequest_Out || ESRObjects

For Inbound and Outbound Processing set the same channels as in the ICO for Integration Directory.

• Sender: SOAP_S

• Receiver: HTTP_R

Set up the parameters of the Operation Mappings in the tab “Receiver Interfaces”.

ESRObjects

Parameter:

• Authroization: Basic Auth Header

• SOAP_DIR: | SAP_PO | SOAP_R_Access

• URL: HostURL

SoftwareComponents

Parameter:

• Authroization: Basic Auth Header

• URL: HostURL

Step 1: Create Data Source

1. Go to Settings → Connectivity → Data Sources.

2. Click the “+” (Add) button in the top-right corner.

3. Enter the required values:

• Name: e.g. WPO

• Type: SAP_PO

• Environment: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source:

Connection Details

• URL: e.g. https://whintic-test.cfapps.eu10.hana.ondemand.com/inbound/pro

• Proxy: (not required)

Authentication

• Select “BASICAUTH” and create new credentials by clicking “here” in the box below.

Basic Auth
When generating username and password, make sure to save it.
It will only be shown once!

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • INVENTORY

   • UPDATE

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “INVENTORY” by selecting the checkbox next to it and clicking the “Start Task” icon.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Before retrieving your Azure service key, ensure that your environment allows API access to Azure Monitor via the public endpoint. ㅤㅤㅤ

If your Azure Management Portal is not publicly accessible, connectivity may be routed via SAP Cloud Connector.
→ See the section “Restricted Azure Access” at the end of this setup panel.

Step 1: Create an Azure App Registration

1. Open the Azure Portal with an administrator account

2. Click on “App registrations” (or navigate to Azure Active Directory → App registrations)

   

3. Click “New registration”
   

   

   • Name: WHINT_IFM (example)

   • Supported account types: All Microsoft account users

4. After creation, note the following values from the app’s Overview page - you’ll need these later:

   • Application (client) ID

   • Directory (tenant) ID

     

Step 2: Add API Permissions

1. Open the created App Registration

2. Go to API permissions

3. Click “+ Add a permission”

4. Under Microsoft APIs, select:

   • API: “Azure Service Management”
     

     

5. Click “Add permissions”
   

   

6. Click Grant admin consent (if required)

Step 3: Assign Azure Role

1. Navigate to Subscriptions → select your subscription (e.g. ISV)

2. Go to Access control (IAM) → Role assignments

3. Click + Add > Add role assignment

4. Assign the following:

   • Role: Monitoring Reader (minimum required for Azure Monitor API)

     • Alternatively: Reader

   • Assign access to: App → select your App Registration (e.g. WHINT_IFM)

TheMonitoring Reader role provides read-only access to monitoring data across Azure resources and is sufficient for metric queries.
It is more restrictive than the general Reader role and recommended for security-sensitive environments.

Step 4: Create a Client Secret

1. In the App Registration, go to “Certificates & secrets”
   

   

2. Click “+ New client secret”

   • Description: e.g. WHINT_CPN

   • Expiry: 730 days (example)

3. Click “Add”

4. Copy and store the secret value immediately – it will not be shown again after leaving the page

Store the secret securely. This will be used to authenticate via OAuth2.

Provide the following credentials to WHINT:

• Token Service URL
  https://login.microsoftonline.com/<tenantID>>/oauth2/v2.0/token

• Client ID
  → From Step 1

• Client Secret
  → From Step 4

Restricted Azure Access

If your Azure Monitor endpoint is not publicly accessible (e.g. due to a private endpoint), API access from SAP BTP may require custom network routing.

One possible option is to expose the following endpoint via SAP Cloud Connector:

https://management.azure.com

This is a nonstandard setup and should only be implemented by experienced network/security teams.
Please contact your cloud administrator and WHINT Support before attempting this configuration.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. WHINT Azure

   • Type: MICROSOFT_AZURE

   • Category: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained during the App Registration process:

Connection Details

• Tenant: Enter the Azure Tenant ID (from App Registration – Directory (tenant) ID)

• Features: Select one or more Azure-specific features to be shown in the cockpit

• Proxy: (Not required)

Authentication

• Type: Select OAUTH2
  Enter the credentials from your Azure App Registration:

  • Client ID: From App Registration → Application (client) ID

  • Client Secret: From created Client Secret in Certificates & secrets

  • Token URL:
    https://login.microsoftonline.com/<tenantID>/oauth2/v2.0/token

  • Scope: https://management.azure.com/.default

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

• Configuration

• Inventory

• Runtime

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. RUNTIME - Reads traffic information from the tenant

3. INVENTORY - Pushes the raw data into the inventory

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your Job Monitor to verify whether the task has completed or is still listed under “Active Tasks”.

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Recommended Task Schedule

Result

Your Azure Monitor data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

Restricted Azure Access

If your Azure Monitor endpoint is not publicly accessible (e.g. due to a private endpoint), API access from SAP BTP may require custom network routing.

One possible option is to expose the following endpoint via SAP Cloud Connector:

https://management.azure.com

This is a nonstandard setup and should only be implemented by experienced network/security teams.
Please contact your cloud administrator and WHINT Support before attempting this configuration.

Create / register connected App

1. In the Anypoint Platform got to “Access Management → Connected Apps”

   

2. Click “Create app”

3. Enter the Details for the connected application.

   1. Choose a “Name” for the App and select “App acts on its own behalf (client credentials)”

      

   2. Select “Add Scopes”, select all necessary scopes and click “Next”

      

   3. In the next step choose the “Business Group”

      

   4. Select the “environments” which should be available for the credentials.

      

   5. Check the review and select “Add Scopes” to save the settings.

4. To save the credentials select “Save” at the bottom.

5. The new created app will be shown in the overview.

   

6. Click on “Copy Id” and “Copy Secret” and save them.

For the next Step, Data Source Creation use the appropriate token URL based on your Anypoint region.

Format:
https://{region}.anypoint.mulesoft.com/accounts/api/v2/oauth2/token

Examples:
https://anypoint.mulesoft.com/accounts/api/v2/oauth2/token (default/global region) or https://eu1.anypoint.mulesoft.com/accounts/api/v2/oauth2/token (EU region)

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

   

3. Enter the required values:

   • Name: e.g. Mulesoft

   • Type: MULESOFT_ANYPOINT

   • Category: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with the credentials obtained earlier:

Connection Details

• Hostname: without http(s):// (e.g. anypoint.mulesoft.com)

• Proxy: (Optional) Provide only if required by your network setup

Authentication

• Type: OAUTH2

• Client ID: Enter the Client ID from the Connected App

• Secret: Enter the Client Secret from the same Connected App

• Token URL: Use the appropriate token URL based on your Anypoint region.

  https://{region}.anypoint.mulesoft.com/accounts/api/v2/oauth2/token

  Examples:

  • https://anypoint.mulesoft.com/accounts/api/v2/oauth2/token

  • https://eu1.anypoint.mulesoft.com/accounts/api/v2/oauth2/token

• Scope: (Optional - leave empty unless specified by Anypoint client configuration)

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • Configuration

   • Inventory

   • Runtime

3. Click “Save” to complete the setup.

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. INVENTORY - Pushes the raw data into the inventory

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

This section guides you through creating a data source for direct connection to your SAP ABAP systems via SAP Cloud Connector using HTTP(S) and SOAP-RFC.

Applicable Deployment Models

WHINT-hosted in WHINT BTP Subaccount

• 1.1.1 - direct connection via SOAP-RFC + HTTPS

Customer-managed in Own BTP Subaccount

• 2.1.1 - direct connection via SOAP-RFC + HTTPS

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. ALM

   • Type: SAP_ABAP

   • Environment: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with your technical user credentials:

Connection Details

• Features: Check all applicable (e.g. IDocs, Files, SOAP Services, OData Services, etc.)

• System: Enter your SAP system ID (e.g. ALM)

• Client: Enter the client number (e.g. 001)

• Type: HTTP

• URL: Enter your SAP system's internal URL and port (e.g http://winalm.sap.whint.de:50000)

• Proxy: Select your Cloud Connector proxy configuration (e.g. SAP CloudConnector WPO)

Authentication

• Type: BASICAUTH

• Username: Enter your technical user (e.g. WHINT)

• Password: Enter the corresponding password

2. In the Tasks section, click the "+" icon (top right of the table) to add the following tasks:

   • RUNTIME

   • INVENTORY

   • CONFIGURATION

3. Click "Save" to complete the setup.

Step 3: Task Configuration

1. Start the task "CONFIGURATION" by selecting the checkbox next to it and clicking the "Start Task" icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. RUNTIME - Reads traffic information from the tenant

3. INVENTORY - Pushes the raw data into the inventory

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your data source is now configured and ready for use. Monitor task execution regularly through the Job Monitor.

This section guides you through creating a data source for proxy connection to your SAP ABAP systems via SAP Cloud Integration, using either RFC-based or HTTP-based connectivity options.

Before starting: Ensure the WHINT Integration Cockpit package is imported and deployed in CPI with both integration flows active (WHINT WIC BACKEND GATEWAY + RFC).

Applicable Deployment Models

WHINT-hosted in WHINT BTP Subaccount

• 1.2.1 - via SAP Cloud Integration (CPI) and SOAP-RFC + HTTPS

• 1.2.2 - via SAP Cloud Integration (CPI) and RFC + HTTPS

Customer-managed in Own BTP Subaccount

• 2.2.1 - via SAP Cloud Integration (CPI) and SOAP-RFC + HTTPS

• 2.2.2 - via SAP Cloud Integration (CPI) and RFC + HTTPS

Prerequisites

When using SAP CPI with SAP_CPI type configuration, you must implement the provisioned package and deploy the WHINT WIC Backend Gateway and WHINT WIC Backend Gateway RFC integration flow in your CPI tenant. Before configuring either connectivity Option A (recommended) or Option B, ensure:

1. The WHINT Integration Cockpit package is implemented in your CPI tenant

2. Both integration flows are deployed and active:

   • WHINT WIC Backend Gateway RFC - Used for RFC communication (Option A)

   • WHINT WIC Backend Gateway - Used for HTTP/SOAP-RFC communication (Option B)

Why RFC is recommended: Better performance and SAP generally recommends RFC over SOAP-RFC for security reasons (see SAP Note 131403).

Connectivity Options

Your CPI configuration supports multiple connectivity options:

Option A: RFC + HTTPS (Models 1.2.2, 2.2.2) - Recommended

• Type Configuration: SAP_CPI

• Integration Flow: WHINT WIC Backend Gateway RFC

Option B: SOAP-RFC + HTTPS (Models 1.2.1, 2.2.1)

• Type Configuration: SAP_CPI

• Integration Flow: WHINT WIC Backend Gateway (SOAP-RFC variant)

Data Source Setup - Option A: RFC + HTTPS

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. ALM via SAP CPI (RFC)

   • Type: SAP_ABAP

   • Environment: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with your technical user credentials:

Connection Details

• Features: Check all applicable (e.g. IDocs, Files, SOAP Services, OData Services, Integration Engine, RFC Destinations, SOAP XI)

• System: Enter your SAP system ID (e.g. ALM)

• Client: Specify the client number (e.g.001)

• Type: SAP_CPI

• URL: Enter your URL
  e.g.https://xxxx-iflmap.hcisbp.eu1.hana.ondemand.com/http/whint/wic/rfc

• RFC Destination: e.g. RFC_ALM_001

• Host: (leave empty)

• Port: (leave empty)

• User: (leave empty)

• Proxy: (not required)

Authentication

• Type: BASICAUTH

• Username: Enter your Username here (e.g. WHINT)

• Password: Enter the corresponding password

2. In the Tasks section, click the "+" icon (top right of the table) to add the following tasks:

   • RUNTIME

   • INVENTORY

   • CONFIGURATION

3. Click "Save" to complete the setup.

Data Source Setup - Option B: SOAP-RFC + HTTPS

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. ALM via SAP CPI (HTTP)

   • Type: SAP_ABAP

   • Environment: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source with your technical user credentials:

Connection Details

• Features: Check all applicable (e.g. IDocs, Files, SOAP Services, OData Services, Integration Engine, RFC Destinations, SOAP XI)

• System: Enter your SAP system ID (e.g. ALM)

• Client: Specify the client number (e.g.001)

• Type: SAP_CPI

• URL: Enter your URL
  e.g. https://xxxx-iflmap.hcisbp.eu1.hana.ondemand.com/http/whint/wic/http

• RFC Destination: (leave empty)

• Host: e.g. winalm.sap.whint.de

• Port: (leave empty)

• User: Enter your technical user e.g. SAPALM

• Proxy: (not required)

Authentication

• Type: BASICAUTH

• Username: Enter your Username here (e.g. WHINT)

• Password: Enter the corresponding password

2. In the Tasks section, click the "+" icon (top right of the table) to add the following tasks:

   • RUNTIME

   • INVENTORY

   • CONFIGURATION

3. Click "Save" to complete the setup.

Step 3: Task Configuration

1. Start the task "CONFIGURATION" by selecting the checkbox next to it and clicking the "Start Task" icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. RUNTIME - Reads traffic information from the tenant

3. INVENTORY - Pushes the raw data into the inventory

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your data source is now configured and ready for use. Monitor task execution regularly through the Job Monitor.

Create an API Token

1. Go to https://id.atlassian.com/manage-profile/security/api-tokens

2. Click “Create API token”

3. Enter a name (e.g. WHINT_Jira_Integration) and click on “Create”

4. Save the token.

Copy and store the token immediately - it will only be shown once

5. You will see the new token in your token list

   

Use the access token:

Type: Basic

Username: Your Jira account email address

Password: The API token you just created

Example: Test Credentials via Postman Authorization Header (optional)

Authorization: Basic base64encode(username:token)

Replace username:token with your email address and the API token, encoded in Base64.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. WHINT_Jira

   • Type: Choose Jira

   • Category: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source using your Atlassian credentials obtained earlier:

Connection Details

• Hostname: Base URL of your Jira instance e.g. your-domain.atlassian.net

• Project ID: Enter your Project ID

• Property: Confluence URL:
  Optional: Set a corresponding property e.g. Documentation URL in Confluence

  • Note: Properties can be created under Settings → Configuration → Properties)

Authentication

• Type: BASICAUTH

• Username: Email address of your Atlassian account

• Password: API Token from your Atlassian profile
  → Generated at https://id.atlassian.com/manage-profile/security/api-tokens

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • Configuration

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “CONFIGURATION” by selecting the checkbox next to it and clicking the “Start Task” icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and INVENTORY to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your Jira data source is now configured and ready for use.
Monitor task execution regularly through the Job Monitor.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources.

2. Click “+” Add.

3. Enter the required values:

   • Name: e.g. WHINT_Confluence

   • Type: Choose CONFLUENCE

   • Category: e.g. DEVELOPMENT

4. Click “Save”.

Step 2: Configure the Data Source

1. Configure the data source using your Atlassian credentials and base URL obtained earlier:

Connection Details

• Root URL: Base URL to the documentation root page
  e.g. https://whint.atlassian.net/wiki/spaces/ID/pages/xxxxxxx/WHINT

• Property: URL:
  Optional: Set a corresponding property e.g. Confluence: URL

  • Note: Properties can be created under Settings → Configuration → Properties

• Environments: Select all environments that should be included in documentation (e.g. Development, Production)

• Mode: Choose UPDATE

• Proxy: not required

Authentication

• Type: BASICAUTH

• Username: Email address of your Atlassian account

• Password: API Token from your Atlassian profile
  → Generated at https://id.atlassian.com/manage-profile/security/api-tokens

2. In the Tasks section, click the “+” icon (top right of the table) to add the following tasks:

   • UPDATE

3. Click “Save” to complete data source creation.

Step 3: Task Configuration

1. Start the task “UPDATE” by selecting the checkbox next to it and clicking the “Start Task” icon.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Result

Your Confluence data source is now configured and ready for use.
The UPDATE task will push documentation updates into Confluence.
Monitor task execution regularly through the Job Monitor.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources

2. Click "+" Add

3. Enter basic information:

   • Name: e.g. LeanIX

   • Type: LEANIX

   • Environment: e.g. Development

4. Click "Save"

Step 2: Configure Connection Details

Connection Details:

• Hostname: Your LeanIX instance (e.g. http://app.leanix.net)

• Workspace: Your LeanIX workspace name (e.g. ctideveloping)

• Features: Select features to sync (Applications, Data Objects, Interfaces)

• Update Mode: UPDATEBYEXTERNALID or other options

• Property: IT Component: e.g. IT Component (LeanIX) mapping

• Property: External ID: e.g. LeanIX: External ID field mapping

• Tag: Tag for imported data (e.g. WHINT)

• Target Field: Field for additional interface information (e.g. technicalInformation)

• Proxy: not required

Authentication (OAuth2):

• Type: OAUTH2

• Client ID: Your LeanIX API token identifier

• Secret: Your LeanIX API token secret

• Token URL: LeanIX OAuth endpoint
  (e.g. https://demo-dte.leanix.net/services/mtm/v1/oauth2/token)

• Scope: not required

Step 3: Task Configuration

1. Add required tasks in the Tasks section:

   • CONFIGURATION - Reads all raw data into the database

   • UPDATE - Aggregates the monthly traffic

2. Configure recurrence (typically daily for both tasks)

3. Start with CONFIGURATION task first

4. Click "Save" to complete setup

Important

Run CONFIGURATION task first to establish the initial connection and metadata, then schedule UPDATE for regular synchronization.

Recommended Task Schedule

Important
Ensure a delay of at least 2–3 hours between CONFIGURATION and UPDATE to prevent overlapping. CONFIGURATION may take longer to complete.

Result

Your data source is now configured and ready for use. Monitor task execution regularly through the Job Monitor.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources

2. Click "+" Add

3. Enter basic information:

   • Name: e.g. BEE360

   • Type: BEE360

   • Environment: e.g. Quality

4. Click "Save"

Step 2: Configure Connection Details

Connection Details:

• Hostname: Your BEE360 instance (e.g. eqconsultants.bee360.rocks)

• Features: Select features to sync (Business Objects, Applications, Interfaces)

• Proxy: Optional proxy configuration

Authentication (API Key):

• Type: APIKEY

• Header: Authorization

• Key: Your BEE360 API key

Step 3: Task Configuration

1. Add required tasks in the Tasks section:

   • CONFIGURATION - Reads all raw data into the database

2. Configure recurrence (daily)

3. Click "Save" to complete setup

4. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Result

Your data source is now configured and ready for use. Monitor task execution regularly through the Job Monitor.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources

2. Click "+" Add

3. Enter basic information:

   • Name: e.g. WHINT LUY

   • Type: LUY

   • Environment: e.g. Production

4. Click "Save"

Step 2: Configure Connection Details

1. Configure the data source with your user credentials:

Connection Details

• Hostname: Your LUY instance (e.g. whitepaperid.luy.app)

• Features: Select features to sync (Business Objects, Information Flows, Information Systems)

• Update Mode: CREATEUPDATE or other options

• Property: External ID: optional, but e.g. Luy: External ID field mapping

• Proxy: not required

Authentication

• Type: BASICAUTH

• Username: Your LUY username (e.g. Administrator)

• Password: Your LUY password

2. In the Tasks section, click the "+" icon (top right of the table) to add the following tasks:

   • CONFIGURATION

   • RUNTIME

   • UPDATE

3. Click "Save" to complete the setup.

Step 3: Task Configuration

1. Start the task "CONFIGURATION" by selecting the checkbox next to it and clicking the "Start Task" icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. RUNTIME - Reads traffic information from the tenant

3. UPDATE - Aggregates the monthly traffic

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Result

Your data source is now configured and ready for use. Monitor task execution regularly through the Job Monitor.

Step 1: Create Data Source

1. Navigate to Settings → Connectivity → Data Sources

2. Click "+" Add

3. Enter basic information:

   • Name: e.g. WHINT Hopex

   • Type: HOPEX

   • Environment: e.g. Development

4. Click "Save"

Step 2: Configure Connection Details

1. Configure the data source with your credentials:

Connection Details:

• Hostname: Your HOPEX instance (e.g. poc06546.demo.mega.com)

• Features: Select features to sync (Applications, Application Flows, Content)

• Update Mode: UPDATEBYEXTERNALID or other options

• Property: External ID: not required

• Proxy: not required

Authentication (API Key):

• Type: APIKEY

• Header: x-api-key

• Key: Your HOPEX API key

2. In the Tasks section, click the "+" icon (top right of the table) to add the following tasks:

   • CONFIGURATION

   • UPDATE

3. Click "Save" to complete the setup

Step 3: Task Configuration

1. Start the task "CONFIGURATION" by selecting the checkbox next to it and clicking the "Start Task" icon.

Execute the following tasks in the specified order:

1. CONFIGURATION - Reads all raw data into the database

2. UPDATE - Aggregates the monthly traffic

Run tasks one at a time and monitor each task completion in the Job Monitor before proceeding to the next step.

2. Check your “Job Monitor” if the task is done or is still running under “Active Tasks”.

Recommended Task Schedule

Result

Your data source is now configured and ready for use. Monitor task execution regularly through the Job Monitor.

Step 1: Create Housekeeping Data Source

1. Navigate to Settings → Connectivity → Data Sources

2. Click "+" Add

3. Enter basic information:

   • Name: e.g. WIC Housekeeping - Reorganization of Logs, Traffic Calculation

   • Type: LOGS

   • Environment: e.g. Test

4. Click "Save"

Step 2: Task Configuration

1. In the Tasks section, click the "+" icon to add the following tasks:

   • UPDATE - Deletes logs older than 7 days

   • RUNTIME - Generates the aggregated monthly traffic

2. Click "Save" to complete the setup

Recommended Task Schedule

Result

System housekeeping is now configured to automatically maintain log files and calculate traffic statistics, ensuring optimal Integration Cockpit performance.

Adapter Top 5: Displays most frequently used adapter types

Authentication Top 5: Shows authentication-related metrics

Complexity: Shows integration complexity classification (Low/Medium/High/Very High)

Decommissioning: Displays inactive interfaces for cleanup identification

Frequency: Displays message frequency patterns and traffic activity

Inventory: Shows interface discovery coverage and enrichment status

Landscape Check: Displays version consistency across environments

Links: Displays connection and dependency information

Robustness: Shows interface stability over the last 30 days

Strategy Fit: Adapter: Validates adapter usage against your integration strategy

Strategy Fit: Authentication: Shows authentication strategy compliance

Timing: Shows timing and performance metrics

Traffic: Shows message volume trends over the last 3 months

Based on common integration management needs, consider adding links to:

• Integration Documentation – Your organization's integration standards and guidelines

• SAP Integration Suite – Direct access to your Integration Suite tenant

• SAP Cloud ALM – Application Lifecycle Management for monitoring

• Team Collaboration Tools – SharePoint, Teams or other team spaces

• Enterprise Architecture Tools – LeanIX, HOPE, or your EAM solution

• Ticketing System – JIRA, ServiceNow or your support platform

• Development - Development and testing environment

• Quality - Quality assurance and integration testing environment

• Test - User acceptance and business testing environment

• Production - Live production environment

This represents the classic DTAP (Development, Test, Acceptance, Production) model used in enterprise integration landscapes.

Optional Additional Environments:

• Sandbox - Experimental or proof-of-concept environment

• Pre-Production - Final staging before production deployment

Option 1: By System

• “SFTP” is transformed into “File Server (xChange)” for any interface (.*)

Option 2: By Interface

• All interfaces containing “DeletedMessage” and system name ending with “RabbitMQ” is transformed into “Messaging Broker”

Option 3: By Interface w/out Sender & Receiver

• Interface “Application_Autoscaler_custom_metrics_API” is mapped with Sender = “” and Receiver = “”

• Interface: .*SalesOrder.* → Harmonized Object: Sales Order

• Interface: .*Drawing.* → Harmonized Object: CAD-Zeichnung

• Interface: .*CurrencyRate.* → Harmonized Object: Currency Rate

• Interface: .*Customer.* → Harmonized Object: Customer Data

• Interface: .*Order.* → Harmonized Object: Sales Order

• Interface: .*Invoice.* → Harmonized Object: Invoice