Deploying to the Oracle Application Server or Standalone OC4J

Deploy your packaged application to the Oracle Application Server through an application server connection. A packaged application will contain a deployment profile that names the files to be deployed, describes their organization, and specifies the target server.

To deploy to the Oracle Application Server:

Create a connection to the target application server.
If the project uses Business Components, install the runtime libraries on the target server.
If deploying to older versions of Oracle Application Server, see the release notes for additional configuration steps that may be required.
For web application applications, make sure that the server connection for connecting to deployed business components is properly configured in the bc4j.xcfg file. This file defines all of the deployment configurations of a particular application module in the business components project and permits data tags and data web beans to access a specific view object belonging to the application module.
Select the deployment profile in the Navigator, right-click, and choose Deploy to | <application server connection>. The application will be packaged as an archive file and be deployed via the selected application server connection.

Notes:

Web modules are deployed to the target deployment directory. See OC4J Deployment Application Directory Structure or refer to the Oracle Application Server Containers for J2EE User's Guide provided with the Oracle Application Server documentation library for information on the deployed location of the application files including the WAR and EAR files.
After successful deployment, you can access the web application in a browser by entering the application URL. For example: http:// <hostname>:<portnumber>/<virtual_path> /<main>.uix where <virtual_path> is the context root you specified in the deployment profile.
The web container in Oracle Application Server provides full support for Servlets 2.3 and JavaServer Pages (JSP) 1.2. For more information, refer to the Sun Microsystems Java Servlet Specification, Version 2.3 which you can download from java.sun.com/products/servlet/.
After the EJB JAR is deployed to Oracle Application Server, a Java client can access it using this procedure:
1. In the Oracle Application Server Enterprise Manager, you must provide a fixed port number for the specific OC4J instance in which the EJB JAR was deployed. Specify this port number in Enterprise Manager | OC4J Instance | Server Properties. For example: 3103.
2. Restart this specific OC4J instance as appropriate.
3. In JDeveloper, create a Java client which will access the EJB JAR.
4. Run the Java client using the same RMI port number that you specified for the OC4J instance in Enterprise Manager (port 3103).

If you deploy the business logic to the web module, the business component files are also added to the web module. However, if you deploy the business logic as an EJB session bean, then the web module only contains the client application files. In both cases, the client application files including the WAR and EAR files are included in the web module and deployed to the target OC4J deployment directory. The server.xml and default-web-site.xml are updated accordingly.
When deploying UIX web modules directly from JDeveloper, the UIX runtime JARs and installable resources are automatically bundled into the EAR if the JDeveloper UIX version does not match the UIX version on the server. This ensures that your deployed application has the correct UIX version to run on the target application server. To enable your deployed application to use the UIX runtime Jars on its local classpath, you may have to override the application's access to UIX files on the global classpath. For example, on OC4J, you can do this by setting the search-local-classes-first parameter to "true" in the application's orion-web.xml. If the target application server is installed with the same UIX version as JDeveloper's, you may exclude the UIX installable resources and runtime Jars from the WAR deployment profile.
If deploying to a standalone OC4J instance, make sure you use the admin.jar that is shipped with the OC4J. If you use an admin.jar that doesn't match the version of the OC4J to which you are deploying, deployment may fail. You can configure deployment to use the admin.jar of the OC4J standalone instance when setting up the connection with the JDeveloper Application Server Connection Wizard.
When JDeveloper deploys an EAR file to a standalone OC4J server connection, it also updates the server configuration files server.xml, and default-web-site.xml or http-web-site.xml accordingly.