You are on page 1of 19

Welcome to this learning unit, an Overview of Temenos Web Services .

In this
unit, you will learn about TWS, where it fits within the T24 Architecture and
how it fits.

TWS2.Install TWS(EE)-R13.03 1
At the end of the session you will be able to

1. State where TWs fits in the T24 Architecture


2. Name the steps involved in publishing a T24 Service as a webservice
3. Identify the various components involved

TWS2.Install TWS(EE)-R13.03 2
T24 has a functionally rich architecture. Any functionality within T24 may be
accessed via OFS i.e. Open Financial Service.

What is OFS? Well, OFS is a standard module within T24, with a module code
OF. It is the ONLY standard gateway to TEMENOS T24. Now, you may be
thinking what does that mean? Simply put, it means that every single
interaction with T24 is driven through OFS.

OFS is message driven , i.e. it works on a request-response based system. The


OFS syntax, or message structure is proprietary to TEMENOS T24. It is the
native way to represent requests to execute T24 transactions, enquiries or
routines.

The OFS module provides the infrastructure necessary to process the OFS
messages.

TWS2.Install TWS(EE)-R13.03 3
T24 Technical Architecture comprises of different layers as shown.
Servers/products from various vendors may be deployed at each layer. Each
layer is scalable.

TWS Composer is used to provide robust SOA webservices for T24.

TWS2.Install TWS(EE)-R13.03 4
Provision
Business services are pre-packaged in Model Bank and aligned with
the BIAN service landscape
Business services are composed of multiple business operations
A business operation is an atomic T24 transaction or query
Business service definitions may be modified
Tooling allows selective creation of web services from the service
landscape

TWS2.Install TWS(EE)-R13.03 5
This slide depicts the service definition hierarchy built into T24. Multiple
service landscapes can be defined.

Business Areas / Domains and Sub Domains – EB.SERVICE.PACKAGE (not


available yet)
Business Services – EB.SERVICE
Business Operations – PW.ACTIVITY
Transactions – VERSION + FUNCTION
Queries – ENQUIRY

TWS2.Install TWS(EE)-R13.03 6
PART 1
T24 produces XML schema to represent a PW.ACTIVITY, i.e. from the underlying
VERSION or ENQUIRY

PART 2
The T24 tooling comes as a series of plug-ins developed for popular integrated Development
Environments (IDE), namely eclipse for java deployment and Microsoft Visual Studio for .Net
environments. Within eclipse, a ‘perspective’ offers a view of the service landscape as a tree
(with check boxes). From within the service landscape view, a user/developer can select the
Business Areas, Domains, Sub-Domains, Services and operations to build and deploy as web
services. The sub-domains can cascade to multiple levels providing custom levels of
granularity. There is a clear separation of the Service definition within T24 (owned by the
business) and the technical tooling used to publish web services to the enterprise.

The T24 web services plug-ins use either JAXB / AXIS / CXF or the .Net CLR to create the
annotated classes from the schemas. These classes inherit a Super-class responsible for
proving the communications necessary to interact with T24 through the T24 Open
Connectivity Framework. The classes themselves can be used for integration by other
applications residing in the application server.

PART 3
The tooling offered by the platform (eclipse/Visual Studio) is then be used to deploy the
packages and generate the WSDL. Alternatively, incumbent tooling can be used for creation
based on XSD.

The actual technical generation of the web service endpoints is accomplished by the platform
(CTX/.Net) thus automatically benefiting from future enhancements to the technology.

TWS2.Install TWS(EE)-R13.03 7
PART 1
T24 produces XML schema to represent a PW.ACTIVITY, i.e. from the underlying
VERSION or ENQUIRY
- Temenos Web Service Composer connects to T24 to download the landscapes.

PART 2
The T24 tooling comes as a series of plug-ins developed for popular integrated Development
Environments (IDE), namely Eclipse for java deployment and Microsoft Visual Studio for
.Net environments. Within Eclipse, a ‘perspective’ offers a view of the service landscape as a
tree (with check boxes). From within the service landscape view, a user/developer can select
the Business Areas, Domains, Sub-Domains, Services and operations to build and deploy as
web services. The sub-domains can cascade to multiple levels providing custom levels of
granularity. There is a clear separation of the Service definition within T24 (owned by the
business) and the technical tooling used to publish web services to the enterprise.
- The TWS Composer project can then be stored in a source code repository.

TWS2.Install TWS(EE)-R13.03 8
PART 3
The tooling offered by the platform (Eclipse/Visual Studio) can then be used to deploy the
packages and generate the WSDL. Alternatively, incumbent tooling can be used for creation
based on XSD. The actual technical generation of the web service endpoints is accomplished
by the platform (Java Metro/.Net WCF) thus automatically benefiting from future
enhancements to the technology.
-The TWS Composer plugin is used to produce a deployment artifact (.war or dll)

PART 4
The TWS artefact leverages all the standard platform configuration and deployment
mechanisms. A TWS deployment benefits from all the security, transaction, and connection
pooling features of the container (IIS, Websphere, Weblogic, JBoss).
- The TWS artifact connects to T24 in our standard high availability architecture

TWS2.Install TWS(EE)-R13.03 9
1. T24 provides the business service – as groups of operations defined in
EB.SERVICE. Operations may be transactional (using VERSION and
FUNCTION) or informational (ENQUIRY).
2. T24 exposes XML schema to represent the business services. Platform
tooling turns those T24 service definitions into annotated packages that
describe the services in a medium that the Web Services runtime can
understand.
3. Once the packages are created, they may be deployed, at which time the
platform generates the Web Services Description Language (WSDL) – the
interface for the outside world.

TWS2.Install TWS(EE)-R13.03 10
1. T24 provides the service definitions to be deployed via a number of core
system calls using the same meta data as the UI.
2. Temenos Eclipse plug-is coded to allow browsing of the T24 business
services, and generation of the “code behind” packages.
3. Eclipse developer tool is used to manually deploy the “code behind”
packages (java only) to the target runtime, which causes the runtime to
generate the WSDL. Or incumbent tooling is used for creation based on
.XSD
4. Deployment target dependent on selected vendor & configuration of JEE
server.

TWS2.Install TWS(EE)-R13.03 11
1. T24 provides the service definitions to be deployed via a number of core
system calls using the same meta data as the UI.
2. Temenos Visual Studio plug-is coded to allow browsing of the T24
business services, and generation of the “code behind” packages.
3. Temenos plug-in uses platform calls to manually deploy the “code behind”
packages (C# only) to the IIS runtime, which triggers the WSDL
generation.
4. Deployment target is standardised:IIS (.net)

TWS2.Install TWS(EE)-R13.03 12
This diagram shows the generated war file deployed in J2EE application
server. As you may notice, it uses the same resource adapter as T24 Browser to
communicate with T24 application server.

TWS2.Install TWS(EE)-R13.03 13
This shows the same war deployed in a JMS architecture

TWS2.Install TWS(EE)-R13.03 14
A complete view of the JMS architecture again with the interface protocols.

TWS2.Install TWS(EE)-R13.03 15
A complete view of the TWS in TAFJ Environment.

TWS2.Install TWS(EE)-R13.03 16
This diagram shows the generated dll file deployed in an IIS application
server. As you may notice, it uses nremote, which makes use of the same
jRemote API as it’s java counterpart, to communicate with T24 application
framework.

TWS2.Install TWS(EE)-R13.03 17
You should now be able to

1. State where TWS fits in the T24 Architecture


2. Name the steps involved in publishing a T24 Service as a webservice
3. Identify the various components involved

TWS2.Install TWS(EE)-R13.03 18
TWS2.Install TWS(EE)-R13.03 19

You might also like