Download PDF - IBM Redbooks

J2C connector components
J2C defines contracts between the application, the connector, and the
application server where the application will be deployed:
► Container contract
The container contract defines what the application server expects to find in a
deployed application. This is the standard contract between an EJB and its
container. It consists of the bean callback methods, such as ejbCreate(),
ejbLoad(), and ejbActivate().
► Application contract
The application contract defines what the connector expects to receive from
the application. It is defined by the Common Client Interface (CCI) API.
► System contract
The system contract specifies the behavior that every J2C resource adapter
must support. The contract components are:
– Connection management contract
This allows the application server, with the assistance of the adapter, to
pool connections to the EIS.
– Transaction management contract
Transactions are a key concept needed to support distributed computing.
– Security management contract
This details the sign-on procedures that are carried out when the client in
WebSphere establishes a connection to the resource adapter or EIS.
These contracts imply that all participating components are J2EE connector
architecture-compliant. The application, connector, and application server must
all be compliant with the J2EE architecture.
CICS authorization and authentication support
Each application that accesses a JCA resource has a resource deployment
descriptor (res-auth) that determines the authentication behavior when
accessing the resource.
Authentication can be done using:
Container authentication When container authentication is specified,
the user ID and password used on the
connection are provided by the container.
Application authentication When application authentication is specified,
the user ID and password used on the
connection are provided explicitly by the
Chapter 1. Introduction 23