|
Oracle® Containers for J2EE Deployment Guide
10g Release 3 (10.1.3) Part No. B14431-01 |
|
 Previous |
 Next |
|
Oracle® Containers for J2EE Deployment Guide
10g Release 3 (10.1.3) Part No. B14431-01 |
|
|
Previous |
Next |
A resource adapter can be packaged and deployed as a standalone RAR that is available as a shared resource to all applications within the OC4J instance.
This chapter includes the following topics:
A resource adapter deployed as a standalone RAR is deployed as a child of the default application, making the connector available to all other applications deployed to the OC4J instance.
The resource adapter is deployed to the ORACLE_HOME/j2ee/home/connectors directory by default. This directory is specified in ORACLE_HOME/j2ee/home/config/server.xml, the OC4J server configuration file.
The following updates are also made to the OC4J instance:
A new <connector> element defining the resource adapter is added to ORACLE_HOME/j2ee/home/config/oc4j-connectors.xml, which provides an enumeration of the standalone resource adapters deployed to the OC4J instance.
An oc4j-ra.xml descriptor is generated in a new directory with the same name as the connector in the ORACLE_HOME/j2ee/home/application-deployments directory.
Because a standalone RAR is a resource that may be shared by multiple applications, redeploying or undeploying a standalone RAR requires a restart of the default application. This in turn will force a restart of all deployed applications, which are child applications of default.
Because of this requirement, redeploying or undeploying a standalone resource adapter is a task that will likely be rarely performed in a production environment.
