Copyright © 2002, Oracle International Corporation. All Rights Reserved.

Oracle is a registered trademark and Oracle9i is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.

Oracle9i Business Intelligence Beans

Setting Up a Separate OC4J Instance for a BIBeans Application -- Windows

Version 9.0.3

November 2002

Oracle9i Business Intelligence Beans (hereinafter referred to as "BI Beans") uses the 9.2 JDBC drivers, while Oracle9i Application Server (9.0.2 or 9.0.3) uses the 9.0.1 JDBC drivers. Therefore, to deploy an application built with BI Beans to the same Oracle9i Application Server as other applications, you must create a separate instance of OC4J. This document describes the process for Windows platforms. You may also want to consult the Oracle9iAS Contrainers for J2EE User�s Guide.

Note: In general, Oracle9i Application Server components and applications are not certified using the 9.2 JDBC drivers. However, BI Beans is certified against the 9.2 drivers.

This document uses ias_home to refer to the directory where Oracle9i Application Server is installed (for example, d:\ora9ias). If you are using the Oracle JDBC Thick (OCI) driver, then you will also need the full path for the ORACLE_HOME and PATH environment variables.

Setting up and configuring a separate OC4J instance:

1. Log into Oracle Enterprise Manager for Oracle9i Application Server. Oracle Enterprise Manager is installed as part of Oracle9i Application Server.
2. Navigate to the Oracle9i Application Server where you want to create the OC4J instance.
3. Click Create OC4J Instance.
4. In the OC4J instance name field, enter the new OC4J instance name, then click Create.
5. Click OK to acknowledge the confirmation message. You will see the new instance name (for example, oc4j_bibeans) in the Application Server System Components section. You can go to the home page of the instance by clicking on its link.

   Note: This document uses oc4j_bibBeans to refer to this instance. In addition, a new directory with the same name as the instance will be created under ias_home\j2ee. This document uses new_oc4j_instance to refer to this directory. That is, new_oc4j_instance is equivalent to ias_home\j2ee\oc4j_bibeans.

6. Update the VM level properties of the OC4J instance as follows:
1. Access the oc4j_bibeans home page and scroll down to Administration. In the Instance Properties section, click Server Properties.
2. (Optional) If you want to use a different JDK, then enter the path to the Java executable.
3. In the OC4J Options field, enter
-properties new_oc4j_instance\config\oc4j.properties.
4. In the Java Options field, enter
-mx256m -Djava.ext.dirs=ias_home\jdk\jre\lib\ext;new_oc4j_instance\jdbc.
7. Log into the machine where Oracle9i Application Server is running. You must log in as the user who installed Oracle9i Application Server. If you are using the Oracle JDBC Thick (OCI) driver, then you must have either the Oracle9i Release 2 database client or the Oracle9i Release 2 database server on this same machine.
8. Configure the application general parameters. To do so, edit application.xml (in new_oc4j_instance\config) and comment out all the <library path> elements except <library path = "..\..\home\lib">.
9. Add application level properties to the OC4J server. To do so, edit oc4j.properties (in new_oc4j_instance\config) and add the following properties:

oc4j.userThreads=true
jbo.server.in_oc4j=true

10. Create a new directory named jdbc under new_oc4j_instance, then copy the Oracle9i Release 2 versions of classes12.jar and nls_charset12.jar to this new directory. These driver files are installed with both the Oracle9i server and client.
11. At the command prompt, type emctl stop to shut down Oracle Enterprise Manager.
12. If you want to use the Oracle JDBC Thick (OCI) driver, then configure the new instance of OC4J as described in Configuring OC4J to use the Oracle JDBC thick (OCI) driver. Otherwise, skip this step.
13. The configuration changes that you made manually in the previous steps will take effect only after you update the DCM repository. To do so, at the command prompt, type dcmctl updateConfig to update the DCM repository with the configuration changes.

    Note: dcmctl is a DCM utility, which is located in %ORACLE_HOME%/dcm/bin/dcmctl. The syntax for this utility is dcmctl command [options].

14. Type dcmctl shutdown to shut down DCM.
15. Type dcmctl start to restart DCM.
16. Type emctl start to restart Oracle Enterprise Manager.

You are now ready to deploy your application to Oracle9i Application Server. For information about deployment, consult the following sources:

• To deploy using Oracle9i JDeveloper -- In the JDeveloper Help system, search for the topic "Deploying Web Applications to Standalone OC4J or Oracle9iAS."
• To deploy using Oracle9i Enterprise Manager -- Consult the Oracle9iAS Containers for J2EE User's Guide, which is available on the Oracle9i Application Server (9.0.3) documentation CD.

Tip: The default port number for Oracle9i Application Server is 7777.

Configuring OC4J to use the Oracle JDBC thick (OCI) driver:

If you want to use the Oracle JDBC Thick (OCI) driver for a BI Beans application, then you must have either the Oracle9i Release 2 database client or the Oracle9i Release 2 database server on that machine. In the following procedure, assume that Oracle9i Release 2 (client and server) is installed under d:\oracle92.

1. At the command prompt, navigate to ias_home (shown in the example below as d:\ora9ias).
2. Navigate to the opmn\conf directory, then open opmn.xml in a text editor.
3. Under the <process-manager> XML element, locate the entry for the OC4J instance that you just created. For example, you would find the following XML element for the instance name oc4j_bibeans:

<oc4j maxRetry="3" instanceName="oc4j_bibeans"
gid="oc4j_bibeans" numProcs="1">

4. Add the <environment> element, as shown below. If it already exists, than add the <prop> elements to it:

<environment>
<prop name="ORACLE_HOME" value="d:\oracle92"/>
<prop name="PATH" value="d:\oracle92\bin;d:\ora9ias\bin: <any other paths you wish to include>"
</environment>

Notes:

• In the PATH property, the database value must be first.
• You may add any other environment variables (name and value as above) to the <environment> element.
• You must also reset the value of the JdbcDriverType in each application's configuration file, as described in the release notes.

Copyright © 2002 Oracle Corporation. All Rights Reserved.