The Software AG PI Adapter for EntireX allows EntireX applications to communicate and exchange data with multi-vendor processes that are connected through the SAP Exchange Infrastructure.
The SAP PI framework provides a set of standard adapters and provides mechanisms for users to add their own adapters. Inside SAP PI, messages can be exchanged between the Software AG adapters and the adapters provided by SAP or third party adapter vendors.
The PI Adapter for EntireX supports both the "Sender" direction and the "Receiver" direction.
The PI Adapter for EntireX requires an existing installation of the EntireX Workbench, EntireX Broker and an RPC client or an RPC server.
For communication with the PI Adapter for EntireX, an XMM (XML Mapping) file (which contains the IDL-to-XML mapping) is required. The IDL-to-XML mapping as well as the XSD files are generated by the EntireX Workbench. Also an IDL file (together with an XMM mapping file) can be generated by exporting the message definitions as XSD schema files from the PI Integration Builder and then importing the XSD files with the EntireX Workbench.
The connection between the Software AG adapter and the EntireX application occurs over an EntireX Broker connection to an appropriate RPC server. Messages received by the Software AG adapter are translated into a format understood by the RPC Server, then passed to the RPC Server. For synchronous messages, a response is generated by an RPC module and returned.
The PI Adapter for EntireX is used in integration scenarios where the Software AG product webMethods EntireX is already installed and in use.
The PI Adapter is called by SAP PI and receives a PI message. The payload of the PI message is an XML document that the PI Adapter translates into the appropriate format and passes to the EntireX application. The application performs the processing that is requested by the message and sends its results back to the PI Adapter. The PI Adapter converts the results to an XML document, then builds a response PI message that contains the XML document as the payload and sends it to SAP PI.
If you are using "EntireX Reliable RPC" as the message protocol, the RPC request is sent asynchronously to the RPC server application and the PI Adapter does not wait for a response.
The connection between the RPC client application and the Software AG adapter occurs from an appropriate RPC client over an EntireX Broker connection. Subprogram (RPC) calls received by the Software AG adapters are translated into a PI message, then passed to the PI Integration Server. For synchronous messages, a response is generated by the PI Integration Server scenario and returned to the RPC client application.
The PI Adapter is called by the RPC client application and receives an RPC request. The RPC request is converted to a PI message which is passed to the infrastructure of the PI Integration Server. The corresponding PI sequence is executed and returns its result as a PI message. The PI Adapter converts the PI message to an RPC response message which is sent back to the RPC client application to complete the RPC call.
If you are using "EntireX Reliable RPC" as the message protocol, no response message is sent back to the RPC client.