41
TAFJ : Empowers JEE Application Server capabilities
===============================
Main message :
- T24 is performing 100% inside standard JEE Application Server.
- T24 benefits of direct and standard JDBC mechanism to connect to database.
- All T24 functionalities fully available and running in pure java.
Slide description (bottom to top) DATABASE
======
- T24 is still database independent and supports , Oracle, DB2, SQL Server and jBASE. The main difference is that the connections (pool) is handled by the JEE App. Server
JEE APPLICATION SERVER
================
- JDBC DataSource: standard and direct access to the database. (No need of Direct Connect Driver anymore.) Connection to database are managed and maintained by the App. Server.
- TAFJ : TAFJ is the RUN-TIME of T24. TAFJ is entirely written in java and is fully EE compliant. It is making the binding between the next layer (T24) and the App. Server.
- T24.jar : The T24 business logic resides and executes into the JEE Application Server.
- MDB : Message Driven Beans are Java EE components that are automatically “woken up” by the App. Server as soon as a message is available.
Wikipedia definition :
Message Driven Beans are business objects whose execution is triggered by messages instead of by method calls. The Message Driven Bean is used among others to provide a high level ease-of-use abstraction for the lower level JMS (Java Message Service) specification. It may subscribe to JMS message queues or message topics, which are typically injected into the bean.
- Message Broker : The Message Broker is providing and managing messages on demand. This is the “Queues” container.
The Message Broker used can be internal to the App.Server or a 3rd party. On the physical deployment model this layer may be separated from the T24 JEE App. Server.
The connection to the Message Broker is done using JMS.
- UI Servlet T24 Browser Servlet or ARCIB Servlet that are hosted by the Servlet Container of the App. Server. On the physical deployment model this layer may be separated from the T24 JEE App. Server.
CLIENT LAYER
=========
This is the technology used to access T24 from a workstation. Flash or ADOBE AIR if using NEO or HTML if using T24 Browser.
Remark :
The physical deployment model may be divided in four separated layers (database, T24 JEE App. Server, Message Broker, Web Layer). However, the idea of this slide is to underline the fact that TAFJ and all TEMENOS components (in blue) are part of the JEE Application Server. Therefore this slide has been designed to put in the center the JEE App. Server to visually reinforce that message.
41
42
TAFJ : Empowers JEE Application Server capabilities
===============================
Main message :
- T24 is performing 100% inside standard JEE Application Server.
- T24 benefits of direct and standard JDBC mechanism to connect to database.
- All T24 functionalities fully available and running in pure java.
Slide description (bottom to top) DATABASE
======
- T24 is still database independent and supports , Oracle, DB2, SQL Server and jBASE. The main difference is that the connections (pool) is handled by the JEE App. Server
JEE APPLICATION SERVER
================
- JDBC DataSource: standard and direct access to the database. (No need of Direct Connect Driver anymore.) Connection to database are managed and maintained by the App. Server.
- TAFJ : TAFJ is the RUN-TIME of T24. TAFJ is entirely written in java and is fully EE compliant. It is making the binding between the next layer (T24) and the App. Server.
- T24.jar : The T24 business logic resides and executes into the JEE Application Server.
- MDB : Message Driven Beans are Java EE components that are automatically “woken up” by the App. Server as soon as a message is available.
Wikipedia definition :
Message Driven Beans are business objects whose execution is triggered by messages instead of by method calls. The Message Driven Bean is used among others to provide a high level ease-of-use abstraction for the lower level JMS (Java Message Service) specification. It may subscribe to JMS message queues or message topics, which are typically injected into the bean.
- Message Broker : The Message Broker is providing and managing messages on demand. This is the “Queues” container.
The Message Broker used can be internal to the App.Server or a 3rd party. On the physical deployment model this layer may be separated from the T24 JEE App. Server.
The connection to the Message Broker is done using JMS.
- UI Servlet T24 Browser Servlet or ARCIB Servlet that are hosted by the Servlet Container of the App. Server. On the physical deployment model this layer may be separated from the T24 JEE App. Server.
CLIENT LAYER
=========
This is the technology used to access T24 from a workstation. Flash or ADOBE AIR if using NEO or HTML if using T24 Browser.
Remark :
The physical deployment model may be divided in four separated layers (database, T24 JEE App. Server, Message Broker, Web Layer). However, the idea of this slide is to underline the fact that TAFJ and all TEMENOS components (in blue) are part of the JEE Application Server. Therefore this slide has been designed to put in the center the JEE App. Server to visually reinforce that message.