web server - Borland Technical Publications

Developing the Resource Adapter
Configuring the Security Map
To use container-managed sign-on, the Borland Enterprise Server must identify a
resource role and then request the connection to the EIS on behalf of the resource role.
To make this identification, the server looks for a security map specified with the
element in the ra-borland.xml descriptor file. This security map builds
the required associations between the server's user roles (Borland Enterprise Server
users with identities defined in a security realm) and resource roles (users known to the
Resource Adapter and/or EIS). See “Security Map” above for details on using the
Security Map.
Developing the Resource Adapter
This section describes how to develop a Connectors 1.0-compliant Resource Adapter.
Resource Adapters must implement the following system contract requirements,
discussed in detail below:
■
■
■
■
Connection management
Security management
Transaction management
Packaging and deployment
Connection management
Note
The connection management contract for the resource adapter specifies a number of
classes and interfaces necessary for providing the system contract. The resource
adapter must implement the following interfaces:
■
javax.resource.spi.ManagedConnection
■
javax.resource.spi.ManagedConnectionFactory
■
javax.resource.spi.ManagedConnectionMetaData
■
■
The ManagedConnection implementation provided by the Resource Adapter must,
in turn, supply implementations of the following interfaces and classes to provide
support to the application server. It is the application server which will ultimately be
managing the connection and associated transactions.
If your environment is non-managed (that is, not managed by the application
server), you are not required to use these interfaces or classes.
javax.resource.spi.ConnectionEvent
javax.resource.spi.ConnectionEventListener
In addition, support for error logging and tracing must be provided by implementing the
following methods in the Resource Adapter:
■
ManagedConnectionFactory.setLogWriter()
■
ManagedConnectionFactory.getLogWriter()
■
ManagedConnection.setLogWriter()
■
ManagedConnection.getLogWriter()
The resource adapter must also provide a default implementation of the
javax.resource.spi.ConnectionManager interface for cases in which the Resource
Adapter is used in a non-managed two-tier application scenario. A default
implementation of ConnectionManager enables the Resource Adapter to provide services
specific to itself. These services can include connection pooling, error logging and
268 BES Developer’s Guide