Setting up a production database

When using the Provisioning Service in a production environment, the Weblogic Server container should be configured to use an Oracle 11g database.

The Oracle database schema you want to use to support the Provisioning Service must be set up before you can begin to use the Provisioning Service. You can use the createDDL.sql script in the Provisioning Service installation package (eidProvisioning.zip) to create the schema.

The domain template used in the basic installation uses a Derby database installed with WebLogic server for its internal database. This database is not suitable for use in a production environment.

To configure WebLogic Server to use an Oracle database:

  1. Log in to WebLogic Administration Console with the user used to install the Provisioning Service. Lock and edit the domain.
  2. In the Domain Structure box, expand the Services node and click on Data Sources
    Administrative Console displays the Summary of JDBC Data Sources dialog.
  3. Select the jdbc/oracle.eid-ps datasource. Click Delete.
    WebLogic Server deletes the selected datasource.
  4. Create a new datasource with the JNDI name jdbc/oracle.eid-ps.
    1. Click New and from the drop menu, choose Generic Data Source.
      The Administration Console displays the JDBC Data Source wizard.
    2. Enter a Name for the datasource. You can use any name you like.
    3. In the JNDI Name field, enter jdbc/oracle.eid-ps. You must use this name.
    4. In the Database Type drop list, choose Oracle.
    5. Click Next.
    6. In the Database Driver drop list, choose the appropriate driver for your database. You must use an XA-type driver.
    7. Consult your database administrator for the appropriate data for the rest of the wizard.
    8. Target the datasource to the Admin Server when asked.
  5. Disable Derby in the WebLogic Server domain environment variables. The environment variables are stored in the file WLSDOMAINHOME/bin/setDomainEnv.cmd on Windows or WLSDOMAINHOME/bin/setDomainEnv.sh on Linux. Change DERBY_FLAG="true" to DERBY_FLAG="false".
  6. Restart WebLogic Server.