EDUCAÇÃO E TECNOLOGIA

Part 5: Configure Cloud Connector for Workflow Integration

This is part of a series of articles, which describe the steps to integrate an extension workflow using SAP Workflow Management on Business Technology Platform (BTP Workflow) into a Flexible Workflow in SAP S/4HANA OP.

Part 1: Integrating an Extension Workflow on SAP BTP into a Flexible Workflow
Part 2: SAP BTP Cockpit Configuration  for Usage of SAP Workflow Management
Part 3: SAP S/4HANA Backend Configuration to Communicate with SAP BTP
Part 4: User and Roles for SAP BTP Workflow and Flexible Workflow
Part 5: Configure Cloud Connector for Workflow Integration
Part 6: Workflow Scenario with Extension Step
Part 7: Flexible Workflow in Integration Scenario
Part 8: Extension Workflow using SAP Workflow Management on SAP BTP
Part 9: End-to-End Test of Workflow Integration Scenario
Part 10: Problem Solving of Workflow Integration Scenario

1. Installation of SAP JVM
2. Installation of Cloud Connector
3. Add Subaccount to Cloud Connector
4. Add Backend System to Cloud Connector
5. Add Destination in SAP BTP


Before starting with the technical description I want to add a short explanation for motivating this issue. Of course it is not necessary to install a local Cloud Connector for using the integration. However, I used it in this scenario, because it helped me in other projects when developing apps on a WebIDE, which I had to connect to the backend ABAP system via local Cloud Connector. In our scenario it is important to understand the role of this tool – to tunnel requests between two systems.

Check out for several ways how to connect to SAP BTP with a Cloud Connector in SAP Help

The following descriptions refer to a Windows environment.

The Cloud Connector (CC) is based on Java. Therefore, java must be installed. Currently, CC works with java version 7 and 8 only. You find a suiting SAP JVM on SAPs tools website.

  • Download: https://tools.hana.ondemand.com/#cloud >> SAP JVM >> sample: sapjvm-8.1.075-windows-x64.zip
  • Unzip the file and remember the JVM path, e.g. C:\Program Files\Java\sapjvm-8.1.075-windows-x64\sapjvm_8
  • Set system environment variable – in Windows:
    • Start menu >> advanced system properties >> Environment Variables
    • In the lower box add JAVA_HOME: (use the JVM path from above)
    • In the lower box edit Path and add: %JAVA_HOME%\bin
  • Unfortunately you have to restart your computer to activate the environment variables in case you had to add or change them.

top


top


  • Logon to CChttps://localhost:8443/
    • First access with user Administrator and password manage
    • After first logon change the login data
  • Button Add Subaccount

Fill the following fields:

  • Region:
    • Check dropdown list for accessible values and choose your value
    • This is probably only one value. If there are more than one values, check in SAP BTP cockpit >> global account >> menu Subaccounts >> tile with your subaccount >> field Region, which should help finding the correct data center in above mentioned dropdown list.
  • Subaccount: see Subaccount ID
  • Display Name:
    • Any meaningful name, which is later displayed in SAP BTP, remember this as CC subaccount name, sample WF_AUDIT
  • Login E-Mail:
    • Usually – especially in test scenarios – email of your user, otherwise use a generic administrator mailbox
  • Password:
    • Domain password of the user with email above
  • Location ID:
    • Another meaningful name for usage in SAP BTP in case in your CC are maintained several Subaccounts; remember this value as CC location ID, sample WF_AUDIT
  • Description:
    • Use this field for further Information (optional)

top


The to-be-connected backend system must be maintained in Cloud Connector. Do it this way in CC:

  • Menu Subaccount: CC subaccount name (sample: WF_AUDIT) >> Submenu Cloud To On-Premise

  • Add system (“+”)
  • Back-end Type: ABAP System >> Next

  • Protocol: HTTPS >> Next

  • Internal Host: Https Host
  • Internal Port: Https Port >> Next

  • Same Values for Virtual Host and Port
  • Principal typeNone >> Next

  • Host in Request Header: one of both entries >> Next

  • Description: whatever you like >> Next
  • Summary >> Finish

Now, the system is maintained and should look in CC like this:

  • Below the shown part from screenshot above you can see an empty table. Add a resource here:
    • Push ‘+’ sign
    • URL: add the path to all released resources only. In test environment the easiest way is path “/”
    • Active: set checkbox
    • WebSocket: do not set checkbox
    • Access Policy: Path and all Sub-Paths (according to the simple way in test environment; in productive environment add appropriate constraints
    • Save

  • Check availability via pushing the button as shown in the screenshot:

top


Although this section is not directly connected to Cloud Connector, it cannot be configured in an earlier step, since one value comes from CC configuration.

Logon to your SAP BTP cockpit >> subaccount

  • Menu Connectivity >> Destinations
  • Maintain backend system via link New Destination on top of the table on the right side

  • Push button Check Connection at the bottom

=> Conclusion: we successfully set up the Cloud Connector and can check that SAP BTP communicates with the backend system.

top


>> Next: Workflow Scenario with Extension Step