Common Client Interface (CCI)
The following options are available for structuring your adapter:
Der gesamte Funktionsumfang des Adapters...
1. You implement all the features of the adapter in the resource adapter and use the Adapter Framework module chain with its default inbound and outbound modules.
2. You provide the adapter by calling exit ejb as an adapter-specific Adapter Framework module.
In this case, you can use your own resource adapter interface, which does not even have to be CCI-based.
The references refer to chapter 9 (Common Client Interface) of the document J2EE Connector Architecture Specification, Final Version 1.0.
You can download this document at java.sun.com/j2ee/connector.
If all the features of the adapter are implemented in the resource adapter, then the requirements in the table below must be taken into account. The default exit bean uses CCI to call the resource adapter. The adapter must implement the javax.resource.cci interfaces, for example, Connection, in its interface classes.
Different Uses of CCI in JCA and Process Integration
Requirement |
JCA |
Process Integration |
Comment |
Reference Page |
CCI support |
Possible |
Mandatory (in case one) Possible (in case two) |
Only mandatory if using Adapter Framework default inbound and outbound modules. |
101 |
CCI Data Representation Interfaces |
Possible |
Mandatory |
The Adapter Framework defines special CCI custom records, which must be supported by adapters. See also: Adapter Framework JCA CCI Library |
101-102 |
ConnectionSpec Standard Properties |
Possible |
Mandatory |
The user name and password are used for the component-managed sign-on application security model. |
104 |
ConnectionSpec Additional Properties |
Possible |
Mandatory |
The Adapter Framework defines special CCI ConnectionSpecs, which must be supported by adapters. See: Adapter Framework JCA CCI Library, under XIConnectionSpec and NWConnectionFactory. |
104 |
Connection.get Local Transaction()/ Auto Commit |
Possible |
Should be met |
Adapters with transactional external protocols (for example, JMS, tRFC, JDBC) should provide an implementation for javac.resource.cci.Local Transaction. The Adapter Framework can thus control the commit/rollback once the module chain has been processed. |
105 |
InteractionSpec Standard Properties |
Possible |
Mandatory |
The Adapter Framework defines special CCI InteractionSpecs, which must be supported by adapters. See also: Adapter Framework JCA CCI Library, under XIInteractionSpec and NWInteraction. |
107 |
InteractionSpec ResultSet Properties |
Possible |
Should not be met |
Adapter Framework interfaces do not use ResultSet properties. Therefore, they should not be provided by adapters. |
107 |
InteractionSpec Additional Properties |
Possible |
Mandatory |
The Adapter Framework defines special CCI InteractionSpecs, which must be supported by adapters. See also: Adapter Framework JCA CCI Library, under XIInteractionSpec and NWInteraction. |
108 |
InteractionSpec JNDI lookup |
Possible |
Possible |
SAP NetWeaver enhances the JCA CCI interaction interface to a factory for InteractionSpecs. Therefore, the JNDI lookup mechanism is not used. See also: Adapter Framework JCA CCI Library, under NWInteraction. |
108 |
MappedRecord, Indexed Record |
Possible |
Should not be used |
See above under Comment for InteractionSpec ResultSet Properties. |
115 |
Custom Records |
Possible |
Mandatory |
The Adapter Framework defines certain CCI custom records, which must be supported by adapters. See also: Adapter Framework JCA CCI Library, under XIMessageRecord. |
123 |