Skip to end of metadata
Go to start of metadata

With Solution Manager SP10, there exists a new integration of SAP Process Integration (PI) / Process Orchestration (PO) with the Integration Repository. There was already since Solution Manager 7.1 an integration with PI/PO, however it only extracted information from the Enterprise Service Repository (ESR). The ESR contains all available integration scenarios from PI side. It does not contain any information about which scenarios are configured and running. Therefore, enhanced integration is to connect to the Integration Directory of PI to retrieve configuration data combined with available runtime information. 

For technical prerequisites, please follow this page.

Logical Ports Creation

For each Web Service in consideration, depending on the installation stack of your PI System, follow the below procedure both in the PI system and Solution Manager.

In your PI system

  • Open your Enterprise Services Repository. For this, get the URL of your PI system and append it with '/dir'.
  • Choose Services Registry under Enterprise Services Repository
  • Under Service Definition, search for the service name mentioned on the prerequisites page.
  • Select the tab Endpoint and under the section General, copy the path suffix of the service. For example, for the web service AdapterMessageMonitoring, the path suffix would be: /AdapterMessageMonitoring/basic?style=document

In your Solution Manager

  1.  Go to transaction SPROXY in your Solution Manager and under the Namespaces, select
    1. Under this namespace, select Object Types and then select Service Consumers.
    2. Under Objects, you will find the Web Services listed. For example, in the case of Dual Stack installation, you will find SenderAgreementIn listed as one of the services.
    3. Double Click on the service name. You will find Properties tab of the service. 
    4. Copy the ABAP Name of the Service from the Properties tab.
  2. Go to transaction LPCONFIG.
    1. Create a Logical Port ( Best Practice to use the ABAP Name from SPROXY and append '_<SystemID>' ) for each service per PI system.
    2. Keep the ABAP Name of the service as proxy class of the Logical Port.
    3. On the Global Settings tab of the section 'Application-Specific', mark 'State Management'.
    4. Choose Call Parameters tab.
      1. Set the HTTP Destination to your PI system's HTTP Destination SOL_API_<system id>.
      2. Paste the Path Suffix copied from the directory of your PI System for the service.
    5. In case this is the first Logical Port for the service, mark it as default port.
    6. Activate the Logical Port

Testing of Logical Ports created

  1. Go to transaction SPROXY in your Solution Manager.
  2. Double click on the Service.
  3. Click 'Test' icon on the tool bar.
  4. Enter the name of the Logical Port created for this service and for the system in scope (Value help may not work).
  5. Choose a Method using Value Help. For our example now, we will choose Query.
  6. Click Execute.
  7. From the toolbar, click 'XML Editor' icon.
  8. Remove the Section with tag <AdministrativeData>.
  9. Remove the section with tag  <Description>.
  10. Change all the attributes to * and press Execute.

  11. Evaluate the response and if you get the correct response, the Logical Port works right.

Execution Steps

  1. Launch the Integration Repository Tools application using the corresponding tile in the group Data Consistency Management SAP Solution Manager Launchpad. If the tile is not available, you can as well use transaction AGS_DCM_EXT_IMPORT. You have to select the solution context you like to import the data to (solution, branch). In PI System, you select the relevant PI component from which the data shall be imported. Note that only PI components show up which are part of the solution you like to import the data to.

  2. Stay on the tab 'Integration Directory' and choose the Logical Ports using the value help and press 'Get Data'. This is will display the interfaces from your PI system with runtime data. The Logical Ports have to be configured as described in the prerequisites.


    When the data is retrieved, you can see the interface attributes like communication channel or sender and receiver service in the attributes table below. The attributes table only shows entries when only one interface is selected in the header table.

  3. Choose the Interfaces you want to download, and then click 'Download JSON' at the top.

  4. Now you can start Solution Administration (transaction SLAN) and use the generic import feature to upload the generated JSON file to the solution. See SAP online help at -> Technology Platform -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Application Help (SAP Library) -> Process Management -> Solution Administration -> Import and Export of Content to find all details of Solution Administration’s import feature.

  • No labels