Deploying BC4J UIX Applications

Important: Before deploying your BC4J web application, ensure that you've met all the prerequisites including creating a connection to an OC4J server before deployment and defining server connection information to deployed business components 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.

See About Deploying on Oracle9i Application Server for information on deploying to an Oracle9i Application Server using the Oracle Enterprise Manager and BC4J Setup and Deployment Prerequisites for more information.

To deploy and then access BC4J UIX applications:

Right-click <myappwar>.deploy from the Navigator.
Choose one of the following deployment options from 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 OC4J server instance.
- Deploy to New Connection: Launches the Connection Wizard which lets you create a new application server connection.
- Deploy to JAR file: the web module is packaged as a JAR file and saved to the local directory or mapped network drive specified when you created the deployment profile.
- Deploy to EAR file: the web module is packaged as an Enterprise Archive (EAR) file and saved to the local directory or mapped network drive specified when you created myappwar.deploy. See About Deploying on Oracle9i Application Server for information on deploying the EAR file to an Oracle9i Application Server using the Oracle Enterprise Manager.
After successful deployment, you can access the web application in a browser by entering its application URL. For example:
http://hostname:<portnumber>/<virtual path>/<sitename>/Main.uix
where <virtual path> is the context root you specified in the deployment profile.

Notes:

Make sure that the Web deployment descriptor is located inside the Web Application Archive (WAR) file as follows:
WEB-INF/web.xml
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. For OC4J, see OC4J Deployment Application Directory Structure or refer to the "Oracle Application Server Containers for J2EE User's Guide" Part Number B10322-01 provided with the Oracle Application Server documentation library for information on the deployed location of the application files including the JAR and EAR file.