ManagedConnectionFactory Properties 

The JCA standard provides its own connection configuration mechanism. It is based on JavaBean properties, which are implemented in the ManagedConnectionFactory class. The properties must be JavaBean compliant. There must be setter and getter methods, which are called in the following cases:

...

●      During deployment, if the deployment descriptor RAR file contains <config-property> elements.

●      During runtime, when the NetWeaver Administrator of AS Java is used to set or keep such properties, for example.

The JCA mechanism is generally not suited to the requirements of Process Integration configuration for the following reasons:

       1.      The JCA configuration approach is connection-based, the Process Integration approach is message-based.

That is, the configuration data is not selected statically for each connection, but dynamically with message data such as party, communication component, and communication channel/interface.

       2.      The adapter configuration in Process Integration is set up in the same way for all adapters and always takes place at the same location. Alternative methods of adapter configuration have been intentionally avoided.

The only reason to use JavaBean properties in the ManagedConnectionFactory is to set default values in the deployment descriptor at deployment time.

In the example adapter, these default values are the adapter type JCA and the adapter namespace http://sap.com/xi/XI/sample. The third parameter addressMode is used for implementation examples of different variants of the address determination.