What are the options for deploying a resource adapter?
• Standalone deployment – The resource adapter is deployed as a standalone module. • Embedded deployment – The resource adapter is first assembled into a J2EE application and then it is deployed as part of that J2EE application. How do I deploy a standalone resource adapter to OC4J? You can use admin.jar to deploy a standalone resource adapter to OC4J. admin.jar is located in the same directory as your oc4j.jar after installation. Suppose you have a resource adapter called myrar.rar, which is located in directory mypath. You’d need to provide a name to this resource adapter for undeployment. Suppose you’d like to name this deployment myrar_name, you can deploy myrar.rar into OC4J by using this command: java -jar admin.jar ormi://my_host:my_rmi_port admin_username admin_password -deployConnector -file mypath/myrar.rar -name myrar_name Replace my_host, my_rmi_port, admin_username and admin_password with the proper values in your OC4J installation.
• Standalone deployment – The resource adapter is deployed as a standalone module. • Embedded deployment – The resource adapter is first assembled into a J2EE application and then it is deployed as part of that J2EE application. How do I deploy a standalone resource adapter to OC4J? Assuming your OC4J home is $J2EE_HOME, the resource adapter is packaged in standalone_ra.rar, and you’d like to name the resource adapter “standalone”. Then you need to create a directory named “standalone” in $J2EE_HOME/connectors, copy standalone_ra.rar to $J2EE_HOME/connectors/standalone, add the following to J2EE_HOME/config/oc4j-connectors.
