The J2EE Connector Architecture defines standard Java interfaces for simplifying the integration of enterprise applications with J2EE-based Java applications. With these interfaces, Java developers can access existing databases, ERP applications and legac
Tutorial Details:
Elements of the J2EE Connector ArchitectureThe J2EE Connector Architecture defines a set of functionality that application server vendors must provide and which back-end system vendorsThe JCA has two basic components, the Common Client Interface (CCI) and a set of system-specific services. An adapter developer provides an interface to CCI along with its side of the system contracts specified as part of the connector architecture. The application server vendor implements its side of the system contracts as part of its base J2EE platform.Connection Management -- Connection management enables the application server to create and manage connections to back-end systems. One important capability provided is support for connection pooling, since connections to back-end systems are expensive. Connection pooling enables an EJB server to pool connections to back-end systems, so rather than opening connections on an as-needed basis, connections with data and services are established, configured, cached and reused automatically by the application server. This contract enables an application server to offer its own services for transaction and security management.
Transaction Management -- The transaction management contract supports transactional access to underlying resource managers. This service enables the transaction manager provided within the EJB server to manage transactions across multiple back-end systems. Connector developers define what level of transaction support with either single or two-phase commit -- for working across multiple back-end systems and their associated resource managers.
Security -- This service enables the developer to define security between the EJB server and the back-end system. The specific security mechanism that is used is dependent on the security mechanism provided by the back-end system. For example, if a system requires Kerberos, then the connection developer will include it. Under the contract, the connector provider must also support user authentication, user authorization and any specific security contracts required by the back-end system.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: J2EE Connector Architecture Promises to Simplify Connection to Back-End Systems
View Tutorial: J2EE Connector Architecture Promises to Simplify Connection to Back-End Systems
Related
Tutorials:
 An introduction to agents - JavaWorld June 1998
An introduction to agents - JavaWorld June 1998
|
Solid JRun serves
up Java on a budget - JavaWorld June 2000
Solid JRun serves
up Java on a budget - JavaWorld June 2000
|
Develop n-tier
applications
using J2EE - JavaWorld December 2000
Develop n-tier
applications
using J2EE - JavaWorld December 2000
|
The magic of Merlin - JavaWorld March 2001
The magic of Merlin - JavaWorld March 2001
|
J2EE project
dangers! - JavaWorld March 2001
J2EE project
dangers! - JavaWorld March 2001
|
Device programming with MIDP, Part
3 - JavaWorld
July 2001
Device programming with MIDP, Part
3 - JavaWorld
July 2001
|
Connect the
enterprise with the JCA, Part 1
Connect the
enterprise with the JCA, Part 1
|
To EJB, or not to
EJB?
To EJB, or not to
EJB?
|
Connect the
enterprise with the JCA, Part 2
Connect the
enterprise with the JCA, Part 2
|
Use Web services
to integrate Web applications with
EISs
Use Web services
to integrate Web applications with
EISs
|
J2EE or J2SE?
JNDI works with both
J2EE or J2SE?
JNDI works with both
|
Is WSDL the
indispensable API?
Is WSDL the
indispensable API?
|
Reinvented
wheel
Reinvented
wheel
|
Design patterns make for
better J2EE apps
Design patterns make for
better J2EE apps
|
Java's secret weapon
Java's secret weapon
|
Business process
automation
made easy with
Java, Part 1
Business process
automation
made easy with
Java, Part 1
|
The J2EE 1.4 Tutorial
The J2EE 1.4 Tutorial is a guide to developing enterprise applications for the Java 2 Platform, Enterprise Edition (J2EE) version 1.4. Here we cover all the things you need to know to make the best use of this tutorial.
|
J2EE Connector Architecture
J2EE Connector Architecture
Introduction
If you\'ve ever had to integrate legacy data, data sources, or functionality with a new application, you\'ve no doubt faced a number of challenges: for instance, figuring out how to connect to legacy systems, m
|
Using a JMS Provider with MDBs via the J2EE Connector Architecture
Using a JMS Provider with MDBs via the J2EE Connector Architecture
In this article I will provide a brief introduction to MDB and the J2EE Connector Architecture (JCA), examining how MDBs can be deployed with the JCA 1.5 resource adapter to use a JMS pro
|
J2EE pathfinder: Implement JSP custom tags in five easy steps
JSP custom tags provide a standardized mechanism for separating presentation and business logic in a dynamic Web page, allowing page designers to focus on presentation while application developers code the back end. In this installment of J2EE pathfinder,
|
|
|
|
