Deploying Web Applications to Other Application Servers

JDeveloper supports direct deployment to standalone OC4J instances, Oracle Application Server, and BEA WebLogic. However, you can also deploy any of the generated J2EE modules including WARs created in JDeveloper to any other third-party application servers. The target server must be installed locally or mapped to a network drive.

The process involves deploying the WAR or EAR file to a remote target server by manually copying these deployment archives to the appropriate deployment location on the target server. Typically, the standard J2EE location for these archives is the /WEB-INF directory on the target server but this location varies depending on the application server. Consult your particular application server's documentation for additional information.

Note: If deploying to Apache Tomcat, see Deploying Web Applications to Apache Tomcat.

To deploy web applications to other application servers:

1. Once you've created the deployment profile for web applications, select and right-click the <webapp>.deploy deployment profile from the Navigator below the specified project.
2. Choose Settings from the context menu to display the WAR Deployment Profile Settings panel.
3. Click the General page node in the left frame.
4. In the WAR file field, specify the deployment location for the WAR file on your target server.
5. In the EAR file field, specify the deployment location for the EAR file on your target server.
6. Click OK.
7. Select and right-click the <webapp>.deploy deployment profile icon. The context menu displays these deployment options:
   1. Deploy to <Name_of_server_connection>: the web module is packaged as a WAR. JDeveloper also generates an EAR file which contains the WAR before deploying to the selected application server connection which you created earlier.
   2. Deploy to New Connection: Launches the Connection Wizard which lets you create a new application server connection.
   3. Deploy to WAR file: the web module is packaged as a WAR and saved to the local directory or mapped network drive you specified earlier in the <webapp>.deploy profile settings.
   4. Deploy to EAR file: the web module is packaged as an EAR and deployed to the local directory or mapped network drive you specified earlier in the <webapp>.deploy profile settings.

Related topics