Common Client Interface (CCI)
The following options are available for structuring your adapter:
Der gesamte Funktionsumfang des Adapters...
● 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.
● You make an additional session ejbs available in addition to the resource adapter.
You implement the access to the adapter and possibly additional parts of the features.
○ For the receiver channels, implement the ejbs as an adapter-specific Adapter Framework module.
You implement the module interface. They replace the SAP default module ModulProcessorExitBean in the receiver module chain.
○ In sender channels, you can call a separate ejb first instead of the module processor. The ejb performs parts of processing and then calls the module processor.
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 you implement all features of the adapter in the resource adapter, you must take the requirements in the following table 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 PI
Requirement |
JCA |
PI |
Comments |
Reference Page |
CCI support |
Possible |
Mandatory (in case 1) Possible (in case 2) |
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. More information: 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. More information: Adapter Framework JCA CCI Library, under XIConnectionSpec and XIConnectionFactory |
104 |
Connection.get Local Transaction()/ Auto Commit |
Possible |
Optional |
The transaction concept of the Adapter Framework does not currently allow the use of local transactions or XAResource. AS Java transactions are used. More information: Transactions for the Asynchronous Receiver Direction, Transactions for the Asynchronous Sender Direction |
105 |
InteractionSpec standard properties |
Possible |
Mandatory |
The Adapter Framework defines special CCI InteractionSpecs, which must be supported by adapters. More information: Adapter Framework JCA CCI Library, under XIInteractionSpec and XIInteraction |
107 |
InteractionSpec ResultSet properties |
Possible |
Should not be met |
Adapter Framework interfaces do not use any 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. More information: Adapter Framework JCA CCI Library, under XIInteractionSpec and XIInteraction |
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. More information: Adapter Framework JCA CCI Library, under XIInteraction |
108 |
MappedRecord, indexed record |
Possible |
Should not be used |
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. More information: Adapter Framework JCA CCI Library, under XIMessageRecord |
123 |