Viewing Resource Adapter
Configuration
A resource adapter
is initially configured at deployment time with the parameters set in its
deployment descriptors – the standard ra.xml
and the additional
connector-j2ee-engine.xml.
At runtime you can view the configuration of the started adapters on the J2EE
Engine using the Runtime tab of Connector
Container Service in the Visual Administrator tool. Most of the settings
cannot be edited runtime. You may only modify the loader
references and the ManagedConnectionFactory
properties.
To view the configuration for a resource adapter, you must select the adapter in the Connectors → Connector 1.0 tree. You can then check the following settings:
· General – you can view these settings on the General tab. They include the properties set in the standard ra.xml, such as resource adapter display name, description, vendor name, specification version, EIS type and version. Here you can also see if a license is required for the adapter and if it has been deployed within an application or it is a standalone resource adapter. The adapter is standalone, if the Is Real Applicationindicator is not selected.
· Resource adapter – these settings are displayed on the Resource Adapter tab. They include the connector group and the loader references. These properties are related to the resource adapter classloading.
· ManagedConnectionFactory – you can view these settings on the Managed Connection Factory tab. They define the configuration of the ManagedConnectionFactory (MCF) that provides a ConnectionFactory, which the applications can lookup from the JNDI registry and use to obtain a connection to the EIS. The settings are related to the transaction support and the authentication mechanism of the MCF, its specific properties, and the ConnectionFactory provided by the MCF and registered in the JNDI registry.
· Security – on the Security tab you can check the authentication type of the resource adapter and the identity subjects defined for it.
· Drivers – on the Drivers tab you can check if any JDBC drivers have been registered with the resource adapter.
For more
information about these settings, see
Deploying the Resource
Adapter in the Development Manual.