TxConnect 1.2

TxConnect is a JCA compliant universal connector written in accordance to Sun’s JCA specifications (JSR016).

  Add it to your Download Basket!

 Add it to your Watch List!


Rate it!
send us
an update
LGPL (GNU Lesser General Public License) 
3.2/5 14
Sadi Melbouci
ROOT \ Programming \ Code Generators
TxConnect is a JCA compliant universal connector written in accordance to Sun’s JCA specifications (JSR016). It connects J2EE based applications to legacy systems. The TxConnect project generically handles multiple protocols by providing an adapter for each type of protocol.

TxConnect manages a pool of re-usable connections, security and transactions. The java application gets the ConnectionFactory from JNDI and then requests a Connection handle and all the functions of pooling, security and transactions are provided.

It propagates the transactions from the J2EE container to the legacy systems or Enterprise Information System (EIS) without requiring any change to the legacy systems or applications.

TxConnect supports both XA Transaction as well as Local Transactions.

TxConnect comes with an SSH, sFTP, Telnet and Socket adapters and will be extended to support SAP, IMS, CICS, MVS, TP8 and TDS.

TxConnect is bi-directional, so that the J2EE application can submit real time transactional requests to the legacy application and receive the responses as speedily and reliably as using natively the legacy application.

TxConnect can be installed on any J2EE compliant container and provides a single interface to access all the type of legacy systems.

System contracts

System contracts define the connection between the application server and the EIS. The EIS side of the system contract is implemented by a resource adapter -- a system-level software driver or adapter specific to the EIS (Telnet, SSH, Socket …etc). The application server and the resource adapter collaborate by means of the system contract to provide secure, robust, scalable access to the EIS.

Three types of system contracts are defined:

The connection management contract enables physical connections to the EIS and provides a mechanism for the application server to pool those connections.

The transaction management contract supports access to an EIS in a transactional context. Transactions can be managed by the application server, providing transactions that incorporate other resources besides the EIS, or they can be internal to the EIS resource manager, in which case no transaction manager is required.

The security contract supports secure access to the EIS. How system contracts are implemented on each side (application server and resource adapter) is not specified by JCA; they can be implemented as each vendor sees fit.

Client API

The second element of JCA is the client API. The API can be specific to the resource adapter or it can be the standard Common Client Interface (CCI) as defined by JCA. The CCI is meant to be used by vendors to provide integration tools and frameworks, making it easier for developers to access enterprise systems. It is recommended (but not mandated) that the resource adapter make use of the CCI.

TxConnect defines a single interface for all type of EIS applications; it is a combination between CCI and TxConnect custom interface.

Resource Adapter module

The resource adapter module contains all of the elements necessary to provide EIS connectivity to applications. Specifically, the resource adapter module includes the following components:

- The Java classes and interfaces that implement the resource adapter
- Any utility Java classes required by the resource adapter
- Any EIS-specific platform-dependent native libraries
- The deployment descriptor

Application servers make use of the deployment descriptor supplied with a resource adapter to configure it to a specific operational environment.

Last updated on February 12th, 2008

#universal connector #JCA specifications #XA transactions #JSR016 #J2EE #XA #JNDI

Add your review!