Search documentation:
	Help  Advanced
Published 08/08/2002

Chapter 2

Installing Risk Manager Files

This chapter explains how to install Risk Manager files on the WebLogic server.

Adding JAR Files to the Classpath

You must install several Java Archive (JAR) files to support Risk Manager, both on the Administration Server and on the Decision Server. These JAR files must be copied to your server and added to the WebLogic classpath.

1. In WebLogic's lib/ directory, create a new directory called rm.

For Windows:

c:\bea\wlserver6.1\lib\rm

For Solaris:

/bea/wlserver6.1/lib/rm

2. Copy the following files from the thirdparty/ directory on the installation CD into the rm/ directory:
• jakarta-regexp-1.2.jar
• jdom.jar
• jimi.zip
• jregex1.1_02.jar
• rmplugin.jar
• xerces.jar
• xmlrpc-1.1.jar

If you are using SQL Server, you must also copy the following files into the rm/ directory:

• msbase.jar
• mssqlserver.jar
• msutil.jar
3. Using a text editor, open the WebLogic startup script.

On Windows, this file is called startWebLogic.cmd.

On Solaris, this file is called startWebLogic.sh.

4. Add the new JAR files to WebLogic's classpath.

On Windows, if you are using SQL Server, the text will now appear similar to the following:

set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\lib\rm\jakarta—regexp—1.2.jar;.\lib\rm\jdom.jar;.\lib\rm\jimi.zip;.\lib\rm\jregex1.1_02.jar;.\lib\rm\rmplugin.jar;.\lib\rm\xerces.jar;.\lib\rm\xmlrpc—1.1.jar;.\lib\rm\msbase.jar;.\lib\rm\mssqlserver.jar;.\lib\rm\msutil.jar

On Windows, if you are using Oracle, the text will now appear similar to the following:

set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\lib\rm\jakarta—regexp—1.2.jar;.\lib\rm\jdom.jar;.\lib\rm\jimi.zip;.\lib\rm\jregex1.1_02.jar;.\lib\rm\rmplugin.jar;.\lib\rm\xerces.jar;.\lib\rm\xmlrpc—1.1.jar

On Solaris, the text will now appear similar to the following:

CLASSPATH=$WL_HOME:$WL_HOME/lib/weblogic_sp.jar:$WL_HOME/lib/weblogic.jar:$WL_HOME/lib/rm/jakarta—regexp—1.2.jar:$WL_HOME/lib/rm/jdom.jar:$WL_HOME/lib/rm/jimi.zip:$WL_HOME/lib/rm/jregex1.1_02.jar:$WL_HOME/lib/rm/rmplugin.jar:$WL_HOME/lib/rm/xerces.jar:$WL_HOME/lib/rm/xmlrpc-1.1.jar

5. Save and close the WebLogic startup script.

Adding JVM Memory for the WebLogic Server

If additional memory is needed, then increase the amount of heap space the JVM can allocate by adjusting the -mx and -ms settings in the WebLogic start-up script.

Configuring the X Server

If you are running the WebLogic server on Solaris, you must complete several tasks to ensure that the Administration Server can create workflow images.

1. Verify that the machine running the Administration Server is also running an X server.

For example, you can use the ps command to get a list of processes, then display only those with a capital X in their names:

ps -ef | grep X

2. Using a text editor, open the WebLogic startup script, startWebLogic.sh.
3. Add the following two lines to the WebLogic startup script:

DISPLAY=<server name>:<display number>

export DISPLAY

For example, you might type the following:

DISPLAY=localhost:1.0

export DISPLAY

4. Save and close the WebLogic startup script.

Copying DTD Files

If you want to use Risk Manager's document type definition files (DTDs) as a reference, you can copy them to any location on your server. The DTDs specify the format of the Extensible Markup Language (XML) request and reply documents.

The DTDs are available on the installation CD in the dtds/ directory. They are also included in the Risk Manager Developer's Guide.