Deploying to the BEA WebLogic Application Server

Deploy your packaged application to the BEA WebLogic 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.

The target WebLogic server must be installed locally or mapped to a network drive.

To deploy to the BEA WebLogic Application Server:

Create a connection to the target application server, the weblogic.jar file in your WebLogic installation directory.
If the project uses ADF Business Components, configure the server for ADF Business Components deployment.
If you are deploying business components JSPs, copy ordhttp.jar to WebLogic's classpath, HtmlServices uses classes inside ordhttp.jar to process multi-part HTTP requests for update and insert. This file is located in <jdev_install>/ord/jlib.
Select the deployment profile in the Navigator, right-click, and choose an option:
- Choose Deploy to | < application server connection> to package the application as an archive file and deploy it via the selected application server connection.
- Choose an archive file option to deploy a module as an archive file. Use the BEA WebLogic Server Console to deploy this archive file to the server. See your WebLogic Server documentation for more information.

Notes:

When developing a Business Components project to be deployed to WebLogic, you must select a connection type and the corresponding SQL dialect, type maps or domains. For more information, see Developing Business Components for Oracle Lite and Non-Oracle Data Sources .
You can access a deployed 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.
When deploying an ADF application to WebLogic, you must also deploy Struts JAR files, either to the common libraries folder, or with each application.
For a web application, make sure that the web deployment descriptor's path in the WAR file is WEB-INF/web.xml.
For an EJB application, make sure that the EJB deployment descriptor's path in the EJB JAR file is META-INF/ejb-jar.xml .

For clients that access EJBs on the WebLogic server, weblogic.jar has to be on the classpath of the client, and the following code is required in the client:

    env.put(Context.INITIAL_CONTEXT_FACTORY, 
            "weblogic.jndi.WLInitialContextFactory");
    env.put(Context.SECURITY_PRINCIPAL, "system");
    env.put(Context.SECURITY_CREDENTIALS, "welcome1");
    env.put(Context.PROVIDER_URL, "t3://localhost:7001");

When deploying to WebLogic, if you use the same EJB in two or more different applications, the second deployment will usually cause a JNDI name collision. Therefore, you must rename the JNDI name of the EJB for the second and any subsequent deployments:

Right-click weblogic-ejb-jar.xml, and select Properties.
Under Enterprise Java Beans, select the relevant ModuleBM bean. The EJB tab is displayed on the right.
In the EJB tab, change the JNDI Name field so that it is different from any other JNDI Name in weblogic-ejb-jar.xml and any other EJBs that are already deployed to WebLogic.
Deploy the application accessing the EJB to WebLogic. During deployment, the IDE automatically fills in the weblogic.xml with appropriate EJB references.

If you are deploying an application that uses UIX, see About UIX Deployment to WebLogic.