Temenos Web Services

Temenos Web Services Temenos Web Services include a development environment (Temenos Web Services Composer) and a runtime environment. The runtime environment accepts incoming web service requests, places them on the T24 input queue, and builds a web service response from the T24 output message.

Message Queue • Message queuing is used to enable indirect connection between the Channels layer and the Application layer. • An optional middleware infrastructure that allows T24 to use message-driven communication with the Channels layer.

TWS Composer parts • An Eclipse plugin • A WAR file containing the web service implementation • The Eclipse plugin is used to determine which versions and enquiries to expose as web services. This is a 'one off' operation, performed by technical staff at the customer site. The plug in generates a WAR file which contains the code required to actually run the web service. The WAR file is deployed to a JavaEE application server, making the services available to external applications. • Note that once the WAR has been created and deployed, the Eclipse plugin is not involved in the operation of the services themselves

Services • The Eclipse plugin presents a list of the 'Business Services' defined in the T24 table EB.SERVICE. Each Business Service is a collection of 'Business Operations' which are stored in the PW.ACTIVITY table. A Business Operation can be either a contract (a version combined with a function) or a query (enquiry). • The selected Business Operations are exposed as web services in the generated WAR file. • The following sections detail the configuration and usage of TWS Composer: • Architecture • Installation • Configuration • Using TWS to generate services