Deploying BC4J Web Applications to Standalone OC4J or Oracle Application Server

Important: Before deploying your BC4J web application, ensure that you've met all the requirements in BC4J Setup and Deployment Prerequisites.

To deploy BC4J web applications to a standalone OC4J or Oracle Application Server instance:

If not already done, create a deployment profile for BC4J web applications.
Important: When creating a deployment profile for BC4J web applications, if you chose to deploy the business logic to the web module, the business component files are also added to the web module. However, if you chose to 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 or Oracle Application Server instance.
If not already done, create an application server connection to the target application server before deploying the WAR file.
(Optional) If you want to edit either the deployment profile <myappwar>.deploy or the corresponding deployment descriptor settings in web.xml, right-click the name of the file you wish to edit and choose Settings. Alternatively, you can choose XML Editor to edit web.xml or Open Externally to edit <myappwar>.deploy directly if you are knowledgeable about the format.
(Optional) If you want to create another WAR deployment profile in this project, right-click web.xml and choose Create WAR Deployment Profile.
To deploy the client application project to the target application server, right-click <myappwar>.deploy and choose Deploy to <application_server_connection>. See "Deployment Options" below for more information.
You can access the web application in a browser by entering its application URL. For example:
http://<hostname>:<portnumber>/<virtual_path>/<sitename>/main.html
where virtual_path is the context root you specified in the deployment profile.

Deployment Options

JDeveloper lets you deploy in the following locations:

From the Navigator, select and right-click <myappwar>.deploy.
You can also choose from the following deployment options in the context menu:
- Deploy to <application_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 standalone OC4J or Oracle Application Server connection you created earlier.
- Deploy to New Connection: Launches the Connection Wizard which lets you create a new application server connection.
- 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.
- Deploy to EAR file: the web module is packaged as an EAR file and saved to the local directory or mapped network drive you specified in the deployment profile.

Notes:

If you require further assistance for any field on any page, click Help.
Make sure that the Web deployment descriptor is located inside the Web Application Archive (WAR) file as follows:
WEB-INF/web.xml