Schritt 2: Konfigurieren Ihres SAP-Systems

To establish a communication between UiPath Test Manager and your SAP system, configure the SAP system by creating a communication user and activating the required services.

For web service Basic authentication and RFC

1. Erstellen Sie einen Kommunikationsbenutzer in Ihrem SAP-System für die Integration mit dem UiPath Test Manager. Weisen Sie die erforderlichen Rollen und Berechtigungen basierend auf den internen Richtlinien Ihrer Organisation zu.
   • Die Integration verwendet Standardschnittstellen über RFC oder Web Service (HTTPS).
   • UiPath erfordert keine spezifischen Autorisierungen, außer bei RFC-Verbindungen.
   Hinweis: Wenn Sie eine RFC-Verbindung verwenden, weisen Sie dem Kommunikationsbenutzer das S_RFCACL -Autorisierungsobjekt zu.
2. Wenn Sie eine Webservice-Verbindung (HTTPS) für die Integration verwenden möchten, aktivieren Sie die erforderlichen SAP-Dienste, um die Verbindung mit UiPath herzustellen.
   Hinweis: Diese Dienste werden für schreibgeschützte Vorgänge verwendet. UiPath verwendet nur HTTP GET -Methoden zum Abrufen von Informationen aus dem SAP-System.
   In der folgenden Liste sind die erforderlichen SAP-Dienste aufgeführt, die für die Verwendung der Heatmap und der Analyse der Auswirkungen von Änderungen aktiviert werden müssen:

   • Heatmap-Dienste:
     • /sap/opu/odata/UIPATH/HatMAP_AGREgate fortgesetzt_SRV/AllAggregatesSet
     • /sap/opu/odata/UIPATH/TRANSPORT_INFO_SRV/TransportsStatusSet
     • /sap/opu/odata/UIPATH/TRASPORT_LOOKBACK_SRV/TransportLookbackSet
     • /sap/opu/odata/UIPATH/S4_CHECK_SRV/S4Info
     • /sap/opu/odata/UIPATH/H HeatMAP_Overview_SRV/FinalHeatmapSet
   • Dienste zur Analyse der Auswirkungen von Änderungen:
     • /sap/opu/odata/UIPATH/GET_TRANSPORT_EXES_SRV/TransportExesSet
     • /sap/opu/odata/UIPATH/GET_TRANSPORT_DETAILS_SRV/DetailsSet
     • /sap/opu/odata/UIPATH/GET_TRANSPORT_DETAILS_SRV/TransportAnalysisSet
     • /sap/opu/odata/UIPATH/EXE_ANALYSIS_SRV/GetTransportAnalysis
     • /sap/opu/odata/UIPATH/GET_TRANSPORT_ALLItemS_SRV/TransportAnalysisSet
     • /sap/opu/odata/UIPATH/GET_TRANSPORT_ALLItemS_SRV/DetailsSet
   Führen Sie die folgenden Teilschritte aus, um die vorherigen Dienste zu aktivieren:
   1. Navigieren Sie zur Benutzeroberfläche Ihres SAP-Systems.
   2. Führen Sie die Transaktion SICF aus.
      Stellen Sie im Abschnitt Filter für aufrufende ICF-Hierarchie sicher, dass SERVICE im Feld Hierarchietyp eingegeben ist.
      Abbildung 1. Der Filter für das Aufrufen des ICF-Hierarchiebildschirms in SAP
      

      

      
      
   3. Wählen Sie Ausführen aus, um die Ausführung der SCIF -Transaktion abzuschließen.

      Ein Auswahlbildschirm wird angezeigt, der verschiedene in Ihrem SAP-System verfügbare Dienste anzeigt.

      Abbildung 2. Der Auswahlbildschirm mit allen in SAP verfügbaren Diensten
      

      

      
      
   4. Erweitern Sie unter Virtuelle Hosts/Dienste den folgenden Menüpfad: default_host > sap > opu > odata > uipath.

      Wenn dies Ihre erste Aktivierung ist, sind die UiPath-Dienste wahrscheinlich ausgegraut, was bedeutet, dass sie installiert, aber nicht aktiv sind. Nach der Aktivierung werden sie fett angezeigt.

   5. Klicken Sie mit der rechten Maustaste auf jeden UiPath-Diensteintrag unter uipath und wählen Sie Dienst aktivieren aus.
      Abbildung 3. Aktivieren von UiPath-Diensten
      

      

      
      
   6. Wählen Sie im Popup-Fenster Aktivierung von ICF-Diensten die Option Ja aus, um die Dienstaktivierung zu bestätigen.

      Sobald ein Dienst aktiviert ist, wird er fett angezeigt.

For web service OAuth authentication

Rationale

The transport provided includes all transportable objects (OAuth profiles, customizing entries) required for UiPath services. However, SAP does not allow full OAuth configuration to be transported for security and system-specific reasons. For this reason, after importing the transport provided, you must complete the OAuth configuration manually in your environment.

Context

The full OAuth configuration cannot be transported to protect sensitive data and maintain system integrity.

• Client Secrets are system-specific - Secrets cannot be exported or imported for security compliance.
• Authorization Server URLs differ per environment - Each landscape (DEV, QA, PROD) uses unique endpoints.
• Certificates and STRUST entries are local - SSL/TLS trust must be configured manually in each system. 
• User assignments and roles are client-dependent - Technical users and authorizations vary across systems. 

• Sensitive data protection - OAuth credentials and tokens cannot be transported to prevent exposure.

Voraussetzungen

Each environment (DEV, QA, PROD) requires separate manual setup. Ensure you perform the following prerequisites.

1. Keep the documentation of endpoints and credentials secure. You will need to provide the Authorization Endpoint and the Token Endpoint in step 4.5.
2. Ensure the Authorization Endpoint check is running.
   1. Go to Transaction SICF and execute it.
   2. Navigate to :/sap/bc/sec/oauth2. Check that the following node is active: authorize (Authorization Endpoint). If the node is inactive, right-click it, and from the context menu, select Activate Service.
   Figure 4. Authorization Endpoint Check
   

   

   
   
3. Ensure the Token Endpoint check is running.
   1. Wechseln Sie zu Transaction SICF .
   2. Navigate to :/sap/bc/sec/oauth2. Check that the following node is active: token (Token Endpoint). If the node is inactive, right-click it, and from the context menu, select Activate Service.
4. Observe the naming convention for the Authorization Endpoint.

   Here is an example of the Authorization Endpoint: https://vhclashci.dummy.nodomain:44301/sap/bc/sec/oauth2/authorization?sap-client=100

   • Part 1 is the Domain Name - https://vhclashci.dummy.nodomain
   • Part 2 is the Port Number - 44301
   • Part 3 is the Static string  - /sap/bc/sec/oauth2/authorization
   • Part 4 is the SAP Client - 100

   To build the authorization string, do the following:

   1. Part 1 - Run transaction RZ11 and search for the entry ‘icm/host_name_full’ – this value will be the domain name for your entry in the endpoint.
   2. Part 2 – Run transaction SMICM and select the menu path “Goto->Services”, find the HTTPS protocol and use the number associated with HTTPS.
   3. Part 3 – Hardcode the value ‘/sap/bc/sec/oauth2/authorization’.
   4. Part 4 – Enter the SAP client you are currently using.
   5. Make sure to use the semicolons and other punctuation, as required.
5. Observe the naming convention for the Token Endpoint.

6. Here is an example of the Authorization Endpoint: https://vhclashci.dummy.nodomain:44301/sap/bc/sec/oauth2/token?sap-client=100

   • Part 1 is the Domain Name - https://vhclashci.dummy.nodomain
   • Part 2 is the Port Number - 44301
   • Part 3 is the Static string  - /sap/bc/sec/oauth2/token
   • Part 4 is the SAP Client - 100

   To build the authorization string, do the following:

   1. Part 1 - Run transaction RZ11 and search for the entry ‘icm/host_name_full’ – this value will be the domain name for your entry in the endpoint.
   2. Part 2 – Run transaction SMICM and select the menu path “Goto->Services”, find the HTTPS protocol and use the number associated with HTTPS.
   3. Part 3 – Hardcode the value ‘/sap/bc/sec/oauth2/token’.
   4. Part 4 – Enter the SAP client you are currently using.
   5. Make sure to use the semicolons and other punctuation, as required.

Schritte

1. Verify your transport import details and availability.
   1. Check that OAuth profiles are available. Use transaction SE80 to ensure OAuth 2.0 Client Profiles are available.
   2. From the dropdown menu, select Package.
   3. Enter ‘/UIPATH/HEATMAP’ in the textbox and hit Enter. OAuth 2.0 Client Profiles should appear in the dropdown menu. If profiles are not available, contact UiPath support.
   Figure 5. Verify transport import
   

   

   
   
2. Configure Client ID/User Id/System User and Client Secret.
   1. For transaction SUO1, contact your Security Team for user creation.
   2. Create a System User with access to /UIPATH/ services according to your company naming standards.
   3. Generate a password according to your company naming standards – this will become your ‘secret’ in OAuth2 configuration later.
3. Configure SSL/TLS Trust. For transaction STRUST, contact your Basis Team for certificate verification.
4. Create the OAuth 2.0 configuration.
   1. For transaction OA2C_CONFIG, select Create and, in the popup, select the transported profile you want use. (You will eventually use every listed profile.)
   2. Enter the Profile Name.
   3. Enter the Username for Client Name.
   4. Hit OK.
   5. Configure the fields and save your configuration:
      1. Client Secret: Select the corresponding scope (server) for each client and hit Enter.
      2. Authorization Endpoint URL (check the Prerequisites section of this topic).
      3. Token Endpoint URL (check the Prerequisites section of this topic).
      4. Client Authentication: Select the Basic radio button.
      5. Selected Grant Type: Select the Client Credentials radio button.
      6. Refresh Token Validity: Enter -1 in textbox.
      7. Clock Skew Tolerance: Enter 5 in textbox.
   6. Check the Summary screen, which should look like the screenshots below.
   Figure 6. OAuth summary page 1
   

   

   
   
   Figure 7. OAuth summary page 2
   

   

   
   
5. Configure transaction SOAUTH2 OAuth2 Clients.
   1. For transaction SOAUTH2, select Create and in the first screen, enter the following information:
      • Client Type: Confidential
      • Client Id: Enter the same Username as above (step 4.3 - 4.c)
      • Description: Enter the service name or profile name.
      • Token Lifetime: 3600 Seconds
   2. Select Next and, in the second screen, enter the following information:
      • Client User Id and Password - Checked
      • SSL Certificate - Checked
      • Check Parameter: “Client Id” – Checked
   3. Select Next and, in the third screen, enter the following information:
      • Grant Type Client Credentials Active – Checked
   4. Select Next and, in the fourth screen, enter the following information:
      • Under OAuth2 Scope Id, find the first empty line and click on the drop-down list at the end of the blank row.
      • Select each of the scopes associated with UiPath until all have been selected.
        • /UIPATH/ANALYZED_YES_OR_NO_SRV_0001
        • /UIPATH/EXE_ANALYSIS_SRV_0001
        • /UIPATH/GET_TRANSPORT_ALLITEMS_SRV_0001
        • /UIPATH/GET_TRANSPORT_DETAILS_SRV_0001
        • /UIPATH/GET_TRANSPORT_EXES_SRV_0001
        • /UIPATH/HEATMAP_AGGREGATES_SRV_0001
        • /UIPATH/HEATMAP_OVERVIEW_SRV_0001
        • /UIPATH/TRANSPORT_INFO_SRV_0001
        • /UIPATH/TRANSPORT_LOOKBACK_SRV_0001
        • /UIPATH/TRANSPORT_STATUS_SRV_0001
        • /UIPATH/ZS4_CHECK_SRV_0001
   5. Select Summary. The screen should look like the example below.
   Figure 8. OAuth2 Client summary page
   

   

   
   
6. Test the connection for Non-RISE compliant systems.
   1. Run transaction SE38 and enter the program name ‘/UIPATH/TEST_OAUTH2_SERVICE’ for Non-RISE compliant S4 systems.
   2. Hit Execute. A selection/parameter screen appears.
   3. Update the following parameters to match your system/user/password.
      • Port – HTTPS Port
      • Client – The current Client should default into a variable.
      • Secret – Enter the password for Client_ID/User.
      • System Name – The current System Name should default into a variable.
      • Client ID – Enter the User ID for UiPath Services.
   4. Hit Execute. The results appear on the next screen. Look for Service Status to be equal to ‘200’. Any other return code indicates an error.
   Figure 9. Test Non-RISE compliant connection
   

   

   
   
7. Test the connection for RISE compliant systems.
   1. Run transaction SE38 and enter the program name ‘/UIPATH/TEST_OAUTH2_SRV_RISE’ for RISE compliant S4 systems.
   2. Hit Execute. A selection/parameter screen appears.
   3. Update the following parameters to match your system/user/password.
      • Port – HTTPS Port
      • Client – The current Client should default into a variable.
      • Secret – Enter the password for Client_ID/User.
      • System Name – The current System Name should default into a variable.
      • Client ID – Enter the User ID for UiPath Services.
   4. Hit Execute. The results appear on the next screen. Look for Service Status to be equal to ‘200’. Any other return code indicates an error.