Deploying Web Applications to WebLogic

A J2EE web module is packaged as a web archive (WAR) file which contains one or more web components (servlets, JSPs) and a deployment descriptor file named web.xml. Once you've created the deployment profile containing the web components and the deployment descriptor file and packages them into a standard J2EE Web Archive (WAR) file, you can proceed to deploy the WAR or EAR to a WebLogic 6.1 or 7.0SP1 application server.

To deploy a web application to WebLogic in JDeveloper :

If not already done, create a deployment profile for web applications (WAR).
If not already done, create a connection to BEA WebLogic before deploying.
Select and right-click <webapp>.deploy profile. The context menu displays these deployment options:
1. Deploy to <Name_of_server_connection>: the web module is packaged as a WAR. JDeveloper deploys the WAR file to the selected WebLogic application server connection which you created earlier.
2. Deploy to WAR file: the web module is packaged as a WAR file and saved to the local directory or mapped network drive you specified in the WAR deployment profile - General Page. Or, you can use the BEA WebLogic Server Console to deploy this WAR file. See your WebLogic Server documentation for more information.
3. Deploy to EAR file: the web module is packaged as an Enterprise Archive (EAR) file and deployed to the selected WebLogic application server. Or, you can use the BEA WebLogic Server Console to deploy this EAR file. See your WebLogic Server documentation for more information.
(Optional) If you want to edit either the <webapp>.deploy profile or the web.xml deployment descriptor settings, right-click its icon and choose Settings.

Notes:

For more information about Servlets 2.3 and JavaServer Pages (JSP) 1.2, refer to the Sun Microsystems Java Servlet Specification, Version 2.3 which you can download from:
http://www.javasoft.com/products/servlet/
Make sure that the web application deployment descriptor is located inside the web archive (WAR) file WEB-INF/web.xml.
WebLogic version 6.1 and 7.0SP1 have been certified by Oracle.
If you are running UIX JSP in your application and an error similar to the following occurs, you may have an issue with virtual paths in WebLogic:
```
     Required XSS file c:\bea\user_projects\jdev\applications\DefaultWebApp\styles\blaf.xss
```
To resolve this issue, you'll need to modify the uix2-install.zip that WebLogic loads from original location <jdev_home>/jdev/redist.

The uix2-install.zip file has a directory structure that includes the cabo directory in all paths. For example, tliner.gif is in cabo/images. The cabo directory must be removed so that WebLogic doesn't confuse it with the virtual directory cabo that exists after you have deployed your application to WebLogic.

Modify uix2-install.zip to remove cabo path:
1. Uncompress the uix2-install.zip file into a temporary directory (for example, c:\temp\). If you are using the jar command, you can use this command:
```
     jar -xf uix2-install.zip.
```
2. Create a new zip file based on all the files in the cabo directory, but do not include the cabo directory in the archive path. If you are using the jar command, cd into the cabo directory, then use this command:
```
    jar cvf uix2-install.zip *
```
3. Copy the new WAR file over the original uix2-install.zip file in your WebLogic server path.