How to use PI/PO systems in SAP BTP

How to use PI/PO systems in SAP BTP


PI/PO systems are usually located in a private environment so you need to use special SAP services to organize the connection.
  1. First of all, configure a cloud connector on the system which has access to PI/PO. See the guide.
  2. Create two services from the command line (or from UI):
    cf create-service connectivity lite figaf-connectivity
    cf create-service destination lite figaf-destination
  3. Uncomment the two lines from the manifest.yml
    1. #  - figaf-connectivity
    2. #  - figaf-destination
  4. If your cloud connector has locationId, specify the corresponding value in vars.yml.
  5. Push the applications as usual:
    cf push --vars-file vars.yml
  6. Use virtual host and port in the Agent configuration. User should have appropriate user roles configuration. P4 port usage is not supported for now.
  7. Check the connectivity. If everything is fine, you will see the tests passed except PI libraries and EJB API access (it's expected for BTP deployment):

Specific services

Normally, it's enough just to expose root url path with all sub-paths:
If you want to specify specific services directly instead of just root url path, define the following services with `Path and All Subpaths` access policy:
  1. /dir/query/int
  2. /rep/query/int
  3. /dir/read/ext
  4. /rep/read/ext
  5. /dir/hmi_channel_xml/int
  6. /CommunicationPartyInService
  7. /BusinessComponentInService
  8. /BusinessSystemInService
  9. /ChangeListInService
  10. /CommunicationChannelInService
  11. /ConfigurationScenarioInService
  12. /IntegratedConfigurationInService
  13. /IntegratedConfiguration750InService
  14. /SenderAgreementInService
  15. /ReceiverAgreementInService
  16. /ReceiverDeterminationInService
  17. /InterfaceDeterminationInService
  18. /XISOAPAdapter
  19. /AdapterMessageMonitoring
  20. /webdynpro/dispatcher/sap.com/com.sap.xi.adminweb/AdminApp (used for user access test only)
  21. /webdynpro/dispatcher/sap.com/tc~lm~itsam~ui~mainframe~wd/FloorPlanApp
  22. /webdynpro/resources/sap.com/tc~lm~itsam~ui~mainframe~wd/FloorPlanApp 
  23. /mdt
  24. /AdapterFramework/ChannelAdminServlet
  25. /BPMFacadeBeanImplService/BPMFacadeBeanImpl

SAP PRO system user roles configuration

Be sure that the user used in Agent configuration has roles depending on the Figaf Tool tools you are going to work with:
  1. Testing Tool: SAP_XI_API_DEVELOP_J2EE (to have read/write permissions in the integration directory), SAP_XI_MONITOR_J2EE (to use AdapterMessageMonitoring WS API for fetching payloads that required for SAP LOG Module integration), and custom role (to send messages through created XI channel) with the following action:
  1. Support Tool: SAP_XI_ALERT_CONSUMER.
  2. Migration overview and PI agent reports, and you would like to add BPM related interfaces: SAP_BPM_SolutionManager (used during report generation, otherwise the error occurs Requesting user does not own the permission 'bpm.solutionmanager' which is required for this call.).
You can find more details in Agent component deployment and configuration (optional, only for PRO systems) and SAP PRO system user roles configuration (integration without Agent component) sections of the user manual available for each global version, e.g., https://figaf.com/help/irt-doc/2408/#sap-pro-system-user-roles-configuration-integration-without-agent-component