Document toolboxDocument toolbox

Recommended - Using SSL Encryption between SAP and Dynatrace (PowerConnect ABAP 8.X)

Dynatrace Log ingest API is available via HTTPS and standard SSL port 443. SAP supports SSL however some basic setup is needed to provide SSL functionality to the native HTTP client built in to the ICM to support HTTPS.

In case SAP ABAP environment does not have SSL support enabled, please follow the steps below.

Please note that the instructions below are for setting up SSL to Dynatrace SaaS.

Important Note(s):

If your Dynatrace OnPrem has a custom SSL certificate installed, the process is the same, however names you see in the examples will differ from the screen shots below.

If you connect to a Dynatrace server via a proxy server then you will need to install any certificates that may sign HTTPS requests that flow through it into SAP.

If you are unsure about how to configure SSL, or you get SSL chain-verify or peer verify errors in SAP log a support call. You will need a valid license and support agreement to get email and phone support.

 

  • In transaction STRUSTSSO2 activate the following SSL nodes:

    • SSL Server Standard

    • SSL Client SSL Client (Anonymous)

    • SSL Client SSL Client (Standard)

Activate by right clicking on each node and selecting “Create” – The default entry can be used unless specific security policies must be adhered too.

Change Mode ->

 

Next we need to ensure the ROOT CA (or server self-signed certificate is installed in the ABAP system).

  • Start transaction STRUSTSSO2.

  • Highlight the hostname under node “SSL client SSL Client (Standard).

  • Click on the import button in the certificate section

 

  • Enter the file path of the Dynatrace RootCA Certificate or Dynatrace Server Self-Signed Certificate.

 

  • Now the RootCA or server self-signed certificate appears in the Certificate section.

  • Please repeat this step for RootCA1 cert if needed.

  • Click on the Add to Certificate List button to add it to the Certificate List.

  • Note: The certificate shown below is if the customer has an Dynatrace SaaS environment. The same concept applies for Dynatrace OnPrem. The CN name should match the Dynatrace endpoint of where you are sending the SAP data.

  • Click Save in the toolbar to save this change

Next step would be to actually connect the SAP system to Dynatrace using transaction /n/BNWVS/MAIN.