How it works

The SOA Gateway is installed locally to the data or business logic an organisation wishes to expose on the legacy platform.

The Gateway uses an eclipse-based configuration tool to define resources, and views of those resources, with simple graphical interfaces.

Once defined, the Web Service for the resource is available from the server to authorised users. Alternatively, the administrator may also use the Eclipse-based tool to register the Web Service with a UDDI server, such as CentraSite from Software AG.

Access: provided using the protocols that define what a Web Service is.

Security: a local security context is allocated to the unit of work.

Transactionality: updates that occur from the invocation of business logic or the updating of one or more databases retains the ACID (atomicity, consistency, independence and durability) transaction properties.

Performance: OnLine Transaction Processing (OLTP) performance levels that exist today are delivered.

Reliability: Proven technologies, including Apache, Apache SSL and XERCES, have been used to develop the SOA Gateway.

<< back