Temenos Web Services for Java

(TWS(EE))

User Guide

Page 1
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.

Copyright 2002-2006 TEMENOS Holdings NV. All rights reserved.

 Document revisions
Date Author Changes Made
26/06/2010 Ashleigh Weinman Initial revision
22/07/2010 Ashleigh Weinman Add configuration set-up for new TWS
Project
23/07/2010 Ben Connectivity
26/07/2010 Ashleigh Response
27/08/2010 Roman Changed the name in Java component to
T24Services instead of Landscape

05/01/2011 Eswaran Connection parameters

09/02/2011 Des Adkinson AA Services section added

Page 2
Contents
Introduction.................................................................................................................................................4
Goals........................................................................................................................................................4
Usage.......................................................................................................................................................4
Services....................................................................................................................................................4
AA services.............................................................................................................................................5
Using TWS to generate services..................................................................................................................5
1. Create a TWS Project......................................................................................................................7
2. Open the T24Services view.............................................................................................................9
3. Select the services to expose.........................................................................................................10
4. Set up T24 connectivity.................................................................................................................10
5. Deploy the TWS Web Application................................................................................................11
6. TWS Web Service Response.........................................................................................................14

Page 3
Introduction
The Temenos Web Service Composer (TWS) is used to expose T24 versions and enquiries as Web
Services.

TWS replaces TAG, the previous Temenos web service tooling offering.

There are implementations for both Microsoft (.NET) and Java stacks; this document is only concerned
with the Java implementation.

Goals

TWS is designed to make it simple to easy to expose T24 versions and enquiries as Web Services using
standard technologies.

Usage

There are two main parts of TWS:

 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.

Page 4
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.

AA services

When defining ‘Business Operations’ in the PW.ACTIVITY table for AA transactions, the PRODUCT
and ACTIVITY to be used must be specified in the AUTOM.FIELD and AUT.NEW.CONTENT fields of the
specified VERSION record. The screen shot below shows the PRODUCT “PERSONAL” and ACTIVITY
“INTERNET.SERVICES-NEW-ARRANGEMENT” specified in the VERSION record
AA.ARRANGEMENT.ACTIVITY,AA.NEW.NOCCY.PW.

Failing to supply this information will result in an error when creating web services.

Using TWS to generate services

The high level process used to generate web services is as follows:
1. Use the Eclipse plugin to:
a. Select the operations to expose
b. Generate a WAR file
2. Deploy the generated WAR file to an application server

Page 5
The services are then available to external applications.

The process is described in more detail below.

Page 6
1. Create a TWS Project

1. Install the TWS plugin (if it is not already installed)

2. Open Eclipse

3. Create a new TWS project

3.1. From the File menu, select new->project

3.2. A dialog will pop up, in the pop up dialog, select TWS->TWS Project.

Page 7
3.3. Enter a name for the project.

3.4. Set the Connection Parameters via the Configure Workspace Settings link.

3.5. Click Finish.

Page 8
2. Open the T24Services view
2.1 Window>ShowView>Other>Temenos Web Services. Open the T24Services option.

2.2 Highlighting the new project will now display the Web Services from T24 in the T24Services
Tab.

Page 9
3. Select the services to expose

3.1 In the T24Services view, select (tick) the Business operations for which Web services are to be
created.

3.2 Click on the Create Services button in the far right hand corner of the T24Services window.

3.3 A progress bar will indicate the progression of the Web Services being generated.

4. Set up T24 connectivity

TWS web applications are TOCF (EE) compliant and communicate with T24 via standard TOCF (EE)
connectivity i.e. via the jca resource adapter (‘AGENT’) or via the java messaging service (‘JMS’).
(see TOCF(EE) documentation for further details)

Since TOCF(EE) was only introduced in T24 R09, T24 R08 users will in all likelihood be using TOCF (TCS) for
connectivity,  so additional setup will be required for TWS (please refer to the “TWS R08 quick guide”).

Page 10
 TOCF(EE) connectivity is configured in the following file:
<TWS-project-dir> \WebContent\WEB-INF\tws.properties
and must be edited by hand if changes to the defaults are required.

The following properties are available for editing:

connector.type (valid values are ‘agent’ (default) and ‘jms’)

This sets the T24 connectivity mode to ‘AGENT’ and ‘JMS’ respectively.

(‘direct’ is another valid value but is not intended for production environments. It allows for
deployment in a simple web container like Apache Tomcat and can be useful for quick testing of
web services).

max.attempts (valid values are integers > 0 (default is 3))

This sets the number of times a given web service request will be tried (if connectivity problems
arise) before giving up.

Application server deployment descriptors

Deployment descriptors for TOCF(EE) supported application servers (JBoss, WebSphere, WebLogic)
are provided in the same directory as the tws.properties file; They reference the required
application server resources which are required for TWS. Sensible default values have been
provided in these deployment descriptors but these files may need to be modified (if e.g. the jndi-
names do not match up with an existing TOCF(EE) installation).

5. Deploy the TWS Web Application

Once a TWS project has been created, it can be deployed to an application server in 2 ways:

1. Eclipse deployment (convenience deployment method for development use)

- Open the Eclipse ‘Servers’ view and create a new server.
- Right click server > Add and Remove > Add the desired TWS projects.

Page 11
 - (Double click server to see / edit server properties).
- Right click server > Start.

2. Standalone deployment (deployment method for production environment)

- Right click TWS project > Export > WAR file.

Page 12
 - Deploy the created WAR file to the application server
- Start the application server.

Test that the web services are successfully deployed by browsing to the following URL:

http://<host>:<http port>/<TWS Project name>/services

You should see a web page that looks something like:

Web Services
Endpoint Information
Service Address: http://localhost:8080/MyTWSProject/services
{T24WebServicesImpl}T24WebServicesImplService
Name: WSDL: http://localhost:8080/MyTWSProject/services?wsdl
Port
{T24WebServicesImpl}T24WebServicesImplPort Implementation com.temenos.tws.T24WebServicesImpl
Name: class:

The web services are now deployed and ready to use.

Page 13
6. TWS Web Service Response
The response to a TWS web service request is in two parts: the status object and the business
object.

The ‘Status’ object contains the following fields:

successIndicator
- a string value indicating the success / failure of the web service request. Can be one of 5
possible values:

Success – request completed successfully

TWSError – error occurred in TWS web app
T24Error – T24 error encountered
T24Override – Override condition encountered
T24Offline – T24 System is offline

transactionId
- the T24 transaction id for the completed request

messages
- list of all success / error messages returned from T24 or TWS web app

The business object returned is dependent on transaction being processed. It will be a

representation of the T24 application updated by the transaction.

When an AA web service is invoked, multiple T24 applications can be updated by a single
transaction. In this case multiple status and business objects will be returned. The successIndicator
of each status object must be checked to determine whether the transaction was processed
successfully.

Page 14