Configuring WebLogic for ADF Applications Deployment

Before deploying an ADF Business Components or ADF TopLink project to a WebLogic server, make sure that the server has met the following setup prerequisites:

Install the ADF runtime libraries on the server.
Define your JDBC data sources for distributed transactions on WebLogic.
To create a connection pool for an Oracle database, add connection information similar to this sample:
```
    Connection Pool Name : orclConnectionpool

      URL : jdbc:oracle:thin:username/password@hostname:1521:orcl

      Driver Classname : oracle.jdbc.driver.OracleDriver

      Properties : dll=ocijdbc9 protocol=thin        
```
Note: Make sure ORACLE_HOME/bin is in the path. Also, because the URL value is case sensitive, you may wish to test the URL using the JDeveloper Connection Wizard. For more information about using custom JDBC URLs, see the context-sensitive help in the Connection Wizard.

To create a data source, use this sample, and note the connection pool name from the sample above:
```
    Datasource Name : orclDatasource JNDI Name : jdbc/OracleDS Pool

    Name : orclConnectionpool

          
```
For more information, see the WebLogic Server Administration Guide which can be found at e-docs.bea.com.

Before starting the WebLogic application server, you must set the ADF libraries into the WebLogic server's classpath. You can easily accomplish this task by inserting the call setupadf.cmd line into the WebLogic command script startWebLogic.cmd:


    echo off

    SETLOCAL



    @rem ADF JAR setup

    call setupadf.cmd



    @rem Initialize the common environment.

    set WL_HOME=D:\bea\weblogic81

    @rem Set Production Mode.  When this is set to true, the server starts up in

    @rem production mode.  When set to false, the server starts up in development

    @rem mode.  If it is not set, it will default to false.

    set PRODUCTION_MODE=

    ...

Start the WebLogic application server using the modified startWebLogic.cmd.