Skip to end of metadata
Go to start of metadata

Interfaces involving more than one interface

Sometimes the interface you like to document is not a point-to-point connection, but includes a middleware component that simply takes over the routing of the message data to the right target component. A prominent example for such middleware is SAP Process Integration / Process Orchestration. Integration Repository is optimized to incorporate interfaces including SAP PI / PO as a middleware component. This is detailed in the following section.

However, you can of course include any middleware that is used in your landscape and create simple three-component interfaces. Be aware that this could require the use of two separate interface technologies for the whole interface (from sender to middleware, and from middleware to receiver), which is not supported by Integration Repository. In this case you can:

  1. Create two separate point-to-point interfaces with the corresponding interface technologies and combine them in a Composite Interface or
  2.  You could create a custom interface technology with appropriate interface attributes which describes the interface processing via the middleware in a sufficient manner. In this case you can stick to Interface objects in Solution Documentation instead of using Composite Interfaces, and you can document the interface with all the necessary attributes as usual.
PI / PO Scenario

For the SAP PI / PO scenario the setup takes place as follows:

  • Create a new Interface in the Interface Library which has a Sender LCG, a Receiver LCG, and the SAP PI / PO LCG as the Middleware Component. Select SAP Process Integration / Process Orchestration as interface technology.

   

  • Then create a new Interface Details element from the context menu. In the Interface Documentation UI you
    can see all three involved system in the header section.        

 

 

  • Next select the PI Installation Type and the right Sender Adapter and Receiver Adapter for the current interface.

 

 

  • The list of assigned attributes is then shown below. Depending on the chosen adapter types the attribute maintenance area could be divided into up to three sections, Sender Attributes, Common Attributes, and Receiver Attributes. Common attributes don’t depend on the chosen adapter type (like the PI channels used in this interface, or the sender & receiver data like party, service, interface name and interface namespace).

Sender and receiver attributes are specific for the chosen adapter type and can be used to describe additional properties of the inbound or outbound processing.

 

 

Note that the value helps for the interface attributes let you select the data source which typically is the middleware component in this kind of three-component interfaces.

    


  • No labels