Configuring SAP Cloud ALM for Integration Suite

[lochie283740187]

SAP Cloud ALM and Integration Suite

SAP Cloud ALM supports numerous SAP Products, including Integration Suite and monitoring. It provides a much more comprehensive UI than the standard Integration Suite Message Processing Log, and allows users to set up alerting in other third party systems with relative ease. 

Introduction

This blog is the second in a three part series that introduces how to enable SAP Cloud ALM for your Integration and Exception Monitoring needs. This first blog will discuss how to provision SAP Cloud ALM, the second blog will discuss connecting SAP Integration Suite to SAP Cloud ALM, and the third blog will discuss connecting third party incident management to SAP Cloud ALM.

First Blog - https://community.sap.com/t5/technology-blogs-by-members/sap-cloud-alm-provisioning/ba-p/13708430

Second Blog -  This Blog

Third Blog - https://community.sap.com/t5/technology-blogs-by-members/configuring-sap-cloud-alm-for-integration-a...

BTP Cockpit Configuration

To connect SAP Cloud ALM to Integration Suite, an endpoint that can retrieve the Message Log and Artifact Health must be create in BTP Cockpit. This is a straightforward and standard process, except require adding special Role Groups to the Service Instance in BTP. For a more in-depth guide, follow this link on Integration Suite – Accessing Cloud Integration Runtime

Prerequisites

• IAS & Users Configured
• BTP Cockpit S User / Global Account Configured
• Cloud Foundry Enabled and User Permissions for managing Cloud Foundry
• Integration Suite Tenant Configured

Steps for creating endpoint.

1. Under the Cloud Foundry Tab on the left, navigate to Spaces.
2. Create a Space and assign yourself (at least) Space Developer Role
3. Navigate to Services -> Instances and Subscriptions, and Create
4. Select the Process Integration Runtime Service.
5. Select the integration-flow plan.
6. Check the tick box about pricing, and assign an Instance Name

Although enabling a Service can result in costs depending on the service, Process Integration Runtime is a standard service that comes along with Integration Suite, at No Additional Cost.

7. Select the Next Button

8. Add the Roles , “MonitoringDataRead”, and “MonitoringArtifactsDeploy.”

9. Review and Create the Instance.

10. Navigate to the newly created Instance, and create a Service Key

11. Give a meaningful name, and use the default Key Type, ClientId/Secret

For later steps, download the service key, and save to safe location.

SAP Cloud ALM Configuring

In Cloud ALM, you can navigate to Administration -> Landscape Management, where you can create the numerous services that connect to SAP ALM, this includes an extensive range of SAP Products, but also has third party services such as ServiceNow (mainly for monitoring purposes). Here is a full list of SAP products that are supported out of box.

Once these Services are configured, SAP ALM can monitor those functionalities (once configuration on those endpoints are configured).

Prerequisites

• User requires Connectivity and Destination Administrator Role Collection in the SAP Cloud ALM

Service Configuration

The Service Configuration must be applied for all external systems to connect to SAP Cloud ALM, even SAP supported products. These services acts as a connection point and improves visibility on all connected systems.

To access this, enter the Landscape Management and then Services and Systems on the left.

Creating a Service

1. Add a New Service/System

For both Service Now and Integration Suite, this can be selected as a Service.

1. Select a unique name (consider Dev, test, and prod systems)
2. Add a description.
3. System Number: Enter the system Number for SAP Products

For non-SAP Products, select a unique name to identify the tenant. Using ServiceNow as an example, use the ServiceNow Instance Name

1. Service Type: Select the relevant Service Type (ServiceNow, Integration Suite, etc.)
2. Tenant Role: Select the relevant Role
3. Root URL: Select the endpoint for the service

For ServiceNow, this would be the tenant URL, but for Integration Suite, it would be the Service key URL generated earlier.

1. The remaining fields are optional
2. Select Save when completed.

After this, the service has been created, but an Endpoint is also needed. 

Endpoint Configuration

1. Select the newly created Service
   
2. Select “Add” in the Endpoints section
   
3. Give relevant endpoint name and use cases if the default values are not correct / unique
4. Add the relevant security Information.

For Integration Suite, you should copy the service key created in BTP, and paste it as an OAtuh2ClientCredentials.

For Third Party Systems, the API User credentials will suffice, but this will also require the third party's tenant URL.

1. Check connection to see for permissions issues.

Optional:

If the needed authentication type is not supported by SAP Cloud ALM landscape management, it is also possible to create a destination via the SAP BTP cockpit of the SAP Cloud ALM tenant and select a different authentication type there. In this case follow the generic documentation for 3rd party ticket systems.

Display the Integration Suite Tenant Logs

When you navigate to Integration and Exception Monitoring, there is a one time setup to view the services that you want displayed. To do this, refer to the below screenshot.
By selecting the bull’s eye, you can to pick the services you want displayed in the Integration and Exception Monitoring, e.g. Integration Suite Instances. However, multiple instances can be included here for as many services as created in the Landscape Management. You can also pick the calendar to show the monitoring between certain time periods.

Steps to activate Monitoring.

1. Select the relevant Integration Suite Tenant
2. Select the three dots over an Integration Suite tenant and select edit configuration.
3. Select the Integration Suite Service you wish to edit.
4. In the Endpoint Field, select the appropriate endpoint from the drop down menu
5. Activate the type of monitoring you wish to perform on Integration Suite

SAP Integration Suite Messages will show all status of each message of a particular integration. Whereas Artifact integration Content will show the status of the overall Integration / Artifact.

Once this is done, the default monitoring is set up, and the integrations and their status’ can be seen as above. More configurations can also be done to onforward this information to other services, such as ServiceNow ticketing, emailing relevant stakeholders, or creating the above alerts for higher level monitoring.

Conclusion

With this, you should now be able to see Messages and Failed Integrations in SAP Cloud ALM. 

SAP Cloud ALM SAP Integration Suite SAP BTP, Cloud Foundry runtime and environment