WebServices Adapter

SOAP services are used extensively and in many cases represent an important part of a company’s infrastructure. The Genesis WS-Bridge adapter defines a way of integrating SOAP services within Genesis’s framework in order to take advantage of existing third party SOAP services, or oppositely to create SOAP services reusing existing Genesis processes.

There are four different and very well defined sections inside the Genesis bridge adapter configuration: SOAP server definitions, SOAP pass through definitions, SOAP objects and SOAP clients.

A SoapServer definition represents a way of supplying data from our database layer to a SOAP service operation, whether if they are full table records or multiple records joined into a single data representation. So essentially, it generates a new SOAP operation which can be called by SOAP clients.

SoapPassThrough definitions act as a messenger between already existing Genesis snapshot processes and SOAP services clients. It transforms the SOAP object request into a DtaSet message which will be sent to a process, and adapts the DtaSet reply to a response SOAP object which will be sent back to the client.

SoapServer and SoapPassThrough definitions need to use SOAP objects in order to specify the request and the response types for their operations. These objects are defined in the SoapObjects configuration section, which should normally live at the end of the configuration file.

SoapClient definitions are used to integrate third party SOAP services into our framework, basically doing the opposite workflow of a SoapPassThrough definition.

The definition will create a RequestServer entry to the process, which will accept requests that will be transformed into the SOAP object request to be used in the third party WebService. Once the reply has come back to the process, it will be converted again to a DtaSet message, so we can return it to our Genesis client.