In this section: |
This section explains how to use Oracle WebLogic 11gR1 application server with or without Apache HTTP Server. It is assumed that WebLogic is installed at this time. Refer to Oracle documentation if you need to install WebLogic.
How to: |
Before deploying the WebFOCUS web application, perform the following procedures.
Before deploying the WebFOCUS web application, you should create a WebLogic domain. If you already have a domain, proceed to How to Configure WebLogic for WebFOCUS Graphs.
/WL_HOME/wlserver_nnn/common/bin
where:
Is the path to the Oracle WebLogic installation directory. This abbreviation is used throughout the following procedures.
Is your WebLogic release number.
./config.sh
The WebLogic Configuration Wizard opens.
To generate graphs, WebFOCUS Servlets either need access to an X Windows Server (through the DISPLAY variable), or they can use the Java VM headless option.
/WL_HOME/wlserver_nnn/common/bin/commEnv.sh
/WL_HOME/user_projects/domains/yourDomain/startWebLogic.cmd
or
/WL_HOME/user_projects/domains/yourDomain/bin/startWebLogic.cmd
DISPLAY=xserver_host:0.0
export DISPLAY
TERM=xterm
export TERM
where:
Is the hostname or IP Address of a machine that is running an X Server.
Note: Graphs are not actually displayed on the machine you set to DISPLAY, but WebFOCUS Servlets must access this X Server to generate graphs. After finishing the configuration, be sure to review the tests to verify graphs in Verifying and Troubleshooting Server Side Graphics (PCHOLD).
export JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.awt.headless=true"
Before a WebFOCUS application can connect to the WebFOCUS repository, you must first modify the CLASSPATH of the application server. This is set in your server startup script or the common script called by all server instances.
/WL_HOME/wlserver_nnn/common/bin/commEnv.sh
/WL_HOME/user_projects/domains/yourDomain/startWebLogic.cmd
or
/WL_HOME/user_projects/domains/yourDomain/bin/startWebLogic.cmd
WEBLOGIC_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}
${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}
${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}
${WL_HOME}/server/lib/ojdbc15.jar":/db2home/db2j
cc.jar:/db2home/db2jcc_license_cisuz.jar
export WEBLOGIC_CLASSPATH
or
CLASSPATH="${WEBLOGIC_CLASSPATH}:${POINTBASE_CLASSPATH}
:${JAVA_HOME}/jre/lib/rt.jar:${WL_HOME}/server/lib/webservices.jar
:${CLASSPATH}":/db2home/db2jcc.jar:/db2home/db2jcc_license_cisuz.jar
export CLASSPATH
To start and stop your domain, use the startWebLogic.sh and stopWebLogic.sh scripts. These scripts are located in:
/WL_HOME/user_projects/domainname
or
/WL_HOME/user_projects/domainname/bin
Note: If you run into problems, ensure environment variables are properly set.
How to: |
Use the WebLogic Console to deploy the WebFOCUS web application. The number of web applications you deploy depends on your configuration. Repeat this procedure for each web application you need to deploy.
The web applications are located in the following directory:
/install_directory/ibi/WebFOCUS80/webapps
Determine which web applications you should deploy.
Web Application | Purpose |
---|---|
webfocus.war | Always deploy this web application. |
ibi_help.war | Always deploy this web application. |
approot.war | Deploy this web application if you are using an application server only configuration. |
You deploy web applications using the WebSphere Admin Console. However, the WebLogic Admin Console does not prompt you to set the context root when you deploy a web application. You can set the context root before you deploy the WAR files by renaming them to the context root names (for example, ibi_apps.war, ibi_help.war, approot.war).
/install_directory/ibi/WebFOCUS80/webapps
Default Name |
New Name |
---|---|
webfocus.war |
ibi_apps.war |
ibi_help.war |
ibi_help.war |
approot.war |
approot.war |
redirect.war |
redirect.war |
For example:
cp webfocus.war ibi_apps.war
Note:
To deploy web applications to WebLogic 11gR1:
http://hostname:port/console
where:
Is the hostname of the machine where WebLogic is running.
Is the port for the domain you are using. The port for the default domain is 7001.
For example:
http://localhost:7001/console
A logon page opens. If the page does not open, ensure your domain is started, and you used the correct port.
A page appears where you can specify the location of the file or directory you wish to deploy.
/install_directory/ibi/WebFOCUS80/webapps
ibi_apps.war
ibi_help.war
or
approot.war
The State of the web application should be Active.
How to: |
If you are not using Apache HTTP Server, proceed to Verifying the WebFOCUS Configuration With Oracle WebLogic Servers.
You can use the Apache HTTP Server in two ways:
Alias /approot/ "/install_directory/ibi/apps/"
For example:
Alias /approot/ "/home/iadmin/ibi/apps/" Alias /icons/ "/usr/apache2/icons/"
LoadModule weblogic_module /PATH_TO_FILE/mod_wl_20.so <IfModule mod_weblogic.c> WebLogicHost weblogic_hostname WebLogicPort weblogic_port </IfModule> <Location /approot> SetHandler weblogic-handler </Location> <Location /ibi_help> SetHandler weblogic-handler </Location>
where:
Is the path to the WebLogic module. This is usually installed with WebLogic and the directory varies by platform. For example:
/WL_HOME/wlserver_nnn/server/lib/linux/i686
The name of the file may vary depending on your platform and Apache HTTP Server release. For Apache 1.3, it may be named mod_wl.so. If it is not installed for your platform, contact Oracle.
Is the hostname for the WebLogic Server.
Is the port for the WebLogic Server. If you are using the default WebLogic domain, this is 7001.
How to: |
After finishing the configuration, run test calls to verify operability.
Be aware that you may need to increase your Java memory settings if you use InfoAssist. You can do this later, as explained in Java Memory Issues.
WebFOCUS |