SOAP Connector Inbound

Owned by Stonebranch (Deactivated)
Jan 31, 2024


Overview

The SOAP Connector - Inbound operation is a synchronous operation that uses the Listen MEP.

It consists of an application workload making a web services call using the SOAP protocol to the Universal Event Monitor for SOA SOAP Listener on (default) port 7880.

The body of the message, which is usually associated with the application data, is written to a file where either:

  • Universal Event Monitor (UEM) can use the event as a trigger.
  • External application, such as a scheduler, can access the files directly.

Note

A SOAP operation that matches the SOAP operation of the remote application workload must exist in the UAC.xml configuration file.


See SOAP Inbound Connection for examples and UAC.xml File Description for a description of the elements and structure of the UAC.xml file.

System Flow

The following figure illustrates the system flow for a SOAP Connector - Listen inbound operation using the Universal Event Monitor for SOA SOAP Connector.



System Flow Description

The following list describes the steps (1 - 3), above.

Step 1

The application workload makes a SOAP request to Universal Event Monitor for SOA using the SOAP protocol on port 7880. Note that Universal Event Monitor for SOA consumes the message locally, meaning on the server that hosts Universal Event Monitor for SOA.

Step 2

The SOAP connector consumes (that is, processes) the SOAP request and writes the content of the SOAP message to a file whose name and location are specified in the UAC.xml configuration file. If you set the writeEnvelope attribute to true, Universal Event Monitor for SOA will write the entire SOAP message, including the envelope, to the specified file.

Step 3

The SOAP connector will then reply to the initial request using a message with a single node, meaning its an acknowledgement only. The purpose of the reply is to satisfy the request / reply operation and release the block of the initial request.