Creating a Connection to Oracle Application Server Via Remote DCM

In addition to deploying J2EE applications to a standalone OC4J instance or Oracle Application Server via local DCM, JDeveloper lets you create a connection to deploy directly to an Oracle Application Server target server via remote Oracle Application Server Distributed Configuration Management (DCM). This means the DCM utility, dcmctl, need not be installed on the same physical machine as Oracle Application Server or JDeveloper.

The process for creating a connection to remote DCM involves these steps:

To create a connection to an Oracle Application Server instance via remote DCM:

  1. In the Navigator, click + to expand the connections_icon Connections node.
  2. Right-click application_server_icon Application Servers.
  3. Choose New Connections from the context menu.
    The Connection Wizard - Welcome page is displayed.
  4. Click Next.
  5. Enter a Connection Name for this connection.
  6. In the Connection Type list box, select Oracle9i Application Server - Remote DCM.
  7. Click Next.
  8. Enter a Username and Password that corresponds to the Oracle Application Server admin user.
  9. Click Next.
  10. On the Connection page, configure the settings for the Enterprise Manager host and port, the Oracle Home directory for the remote Oracle Application Server instance, and the OC4J instance name. Click Help for details.
  11. Click Finish.

Editing Configuration Files for the Enterprise Manager OC4J Instance

(This section is applicable only if you are using Oracle9iAS Release 9.0.2.)

To manually edit the orion-web.xml and em-app.xml files:

  1. Modify the Enterprise Manager servlet configuration by editing the following files:

    1. In ${ORACLE_HOME}/sysman/j2ee/application-deployments/em/emd/orion-web.xml, comment out the following lines:

      2. <!--
      <classpath path="/<ORACLE_HOME>/dcm/lib/dcm.jar" />
      -->

      <!--
      <classpath path="/<ORACLE_HOME>/j2ee/home/jaznplugin.jar" />
      -->

    2. In ${ORACLE_HOME}/sysman/j2ee/config/em-app.xml, add the following lines: 
       
		<!-- Added dcm.jar and jaznplugin.jar in order to let -->
        <!-- EM share the same DCM stack with the DCM servlet API -->
        <library path="/<ORACLE_HOME>/j2ee/home/jaznplugin.jar" />
        <library path="/<ORACLE_HOME>/dcm/lib/dcm.jar" />

      where ${ORACLE_HOME} is the location of the Oracle9iAS ORACLE_HOME.

  2. Create an application server connection to Oracle Application Server - Remote DCM. Make sure to enter the Enterprise Manager OC4J Host Name which contains this DCM servlet when prompted in the JDeveloper Application Server Connection Wizard.

Restarting Enterprise Manager

After deploying oc4j-dcm-servlet.ear to a running Enterprise Manager OC4J instance and editing the orion-web.xml and em-app.xml files (required for Oracle 9.0.2 only), you must restart Enterprise Manager by issuing these commands from ${ORACLE_HOME}/bin/:

emctl stop
emctl start

Note: You will be prompted for the Enterprise Manager password.