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
Deploying Applications to BEA WebLogic Server
Version 9.0.3
November 2002
Oracle Corporation supports the deployment of applications that are built with
Oracle9i Business Intelligence Beans (hereinafter referred to as "BI
Beans") to BEA WebLogic server. Not all configurations have been tested,
but the steps that are presented in this document have been verified to work
for BEA WebLogic Server 7.0 on Windows NT using the Oracle9i Release
1 database or the Oracle9i Release 2 database.
Process: Deploying a BI Beans application to BEA WebLogic Server
The process that is described in this section provides an overview of the steps
that are required to deploy a BI Beans application to BEA WebLogic Server. The
remaining sections of this document provide details for each step in the deployment
process. The final section includes sample URLs for starting the deployed application.
The summary process is as follows:
In JDeveloper, create a uix-config.xml file in your BI Beans
project. This file identifies a specific directory in the BEA WebLogic Server
that will be used in Step 3.
Important: This additional file is required only for deployment
to BEA WebLogic Server. When the entire deployment process is completed,
remove the uix-config.xml file from your project before you
perform additional development work on your application. If you attempt
to run the project in JDeveloper before this file is removed, then you will
encounter problems.
In JDeveloper, create a deployment profile and a WAR file for your project.
(This task is identical to the creation of a deployment profile for any
BI Beans application.)
Extract the required installables from the WAR file into the BEA WebLogic
Server directory that you specified in the uix-config.xml file.
This step is required because BEA WebLogic Server does not extract the
contents of the WAR file to the file system on the server. However, BI Beans
needs a location on the server file system to create a cache for images,
styles, and other components.
Change the JDK default VM.
Include a VM parameter that points to the location of the appropriate JDBC
JAR files on the server file system.
Perform the final deployment to BEA WebLogic Server.
Step 1: Creating a uix-config.xml file in your BI Beans project
In JDeveloper, create and add a uix-config.xml file to your project.
Save this file in the public_html\WEB-INF directory of your project.
For additional information about creating a uix-config.xml file,
consult the "UIX Developer's Guide" in the JDeveloper Help system.
The following sample uix-config.xml files contain the variable
Folder_on_Server_File_System that refers to a directory on the file
system of the server. Later in the deployment process, you will extract the
WAR file for the application into this directory. Note that spaces are not allowed
in the name of this variable.
The following uix-config.xml is a sample file for use in a servlet
or a JSP application:
<?xml version="1.0" encoding="ISO-8859-1"?>
<configurations xmlns="http://xmlns.oracle.com/uix/config">
<default-configuration>
<base-directory>
<full-path>Folder_on_Server_File_System</full-path>
<full-uri>/cabo/</full-uri>
</base-directory>
<!-- Use local JSPs -->
<jsps-directory>
<context-uri>/cabo/jsps</context-uri>
</jsps-directory>
</default-configuration>
</configurations>
The following uix-config.xml is a sample file for use in a uiXML
application. This sample includes the required application-configuration element:
In JDeveloper, use the following procedure to create a deployment profile and
produce a WAR file:
In the System-Navigator, select the project that you want to deploy.
From the File menu, choose New to create a
new JDeveloper object within that project. The JDeveloper New
Wizard appears.
Under categories, select Deployment Profiles.
Select the item WAR file - J2EE Web Module
and choose OK. The Save Deployment Profile dialog
box appears.
In the Save Deployment Profile dialog box, accept the default or enter
a name such as webapp.deploy and choose Save.
The WAR Module Deployment Profile Settings dialog box appears.
Select General, choose Specify
the J2EE Web Context Root, and enter the desired root.
Select WEB_INF/lib and, in the Which libraries
are involved in dependency analysis box, select the following libraries:
BIBeans Runtime
BC4J Runtime
UIX Runtime
JSP Runtime
Oracle JDBC
Either OLAP API 901 or OLAP
API 92 depending on whether your application uses an Oracle9i
Release 1 (OLAP API 901) database or an Oracle9i Release 2
(OLAP API 92) database.
Choose OK to complete the definition of the
profile, which appears as a .deploy file in your project.
Right-click the .deploy file and choose Deploy to
WAR.
Step 3: Extracting the required installables from the WAR file
From the WAR file, extract the cabo directory into the server
directory that you specified in the Folder_on_Server_File_System
variable in the uix-config.xml file.
Note: The cabo directory contains the uiXML and BI Beans installables.
Step 4: Changing the JDK default VM
By default, JDK1.3 uses client HotSpot VM. In order to run a BI Beans application,
change the VM type to server or classic for BEA WebLogic Server.
Step 5: Include a VM parameter that points to the location of the appropriate
JDBC JAR files
The deployed application must use the same version of the JDBC JAR files that
it used when it was run in JDeveloper.
To specify the appropriate JDBC JAR files, use the following procedure:
Create a directory on the server file system to hold the JDBC JAR files.
Copy the following JDBC JAR files from the jdev_home\jdbc\lib
directory (where jdev_home represents the directory in which
JDeveloper is installed) to the directory that you created in Step 1:
classes12.jar
nls_charset12.jar
Add the following parameter to the JAVA_OPTIONS environment variable where
jdk_home is the home directory of the JDK installation on the
server, ext is the JRE extensions directory, and jdbc_jar_directory
is the full path of the directory that you created in Step 1.
To complete the deployment of your application, use the following procedure:
Ensure that BEA WebLogic Server is running.
In the JDeveloper System-Navigator, right-click the .deploy
file in your project and choose Deploy to Name_of_Connection,
where Name_of_Connection represents an existing application server
connection for BEA WebLogic Server.
Note: If you have not already created an application server
connection for BEA WebLogic Server, then choose New Connection
and complete the Connection wizard so that you can deploy to the desired
server.
Starting the application
To start the application from a Web browser, enter the application URL
using the following guidelines:
The format of the URL is: http://<web-server-name>:<port>/<virtual-path>/<application-name>
The following substitutions are used in the URL:
<web_server_name> -- The network host
name of the production machine.
<port> -- The port number of the web
server.
<virtual-path> -- Includes the Web application
context root that you specified in the deployment profile.
<application-name> -- The servlet package
and class, JSP file name, or uiXML file name.
The following samples demonstrate URLs that you might use for different
types of applications. The samples assume that 7001 represents
the port number of BEA WebLogic Server and that workspace1-project1_webLogic-context-root
represents the Web application context root.
Bookmark
