##################################################################

# Java Virtual Machine configuration

#

##################################################################

##

# The classpath for the JVM. This classpath is appended to the front

# of the WebSphere Runtime classpath. This classpath should contain

# the JVM Classes and any user classes. The WebSphere classpath is

# built dynamically from the contents of the \lib

# directory

Java.classpath=/opt/jdk118/lib/classes.zip:/opt/IBMWebAS/classes:/opt/IBMWebAS/w

eb/classes:/usr/IBMdb2/V6.1/Java/db2Java.zip:

/opt/domino/NCSO.jar

Figure 45. Adding the NCSO.jar classpath to bootstrap.properties

4. Restart the IBM HTTP server with the following commands:

killall Java

/etc/rc.d/init.d/ibmhttpd stop

/etc/rc.d/init.d/ibmhttpd start

2.4.6.3 Verifying WebSphere to access Domino server.

To verifying the WebSphere to access the Domino database, we need a

simple Java servlet program. We create a simple servlet on WebSphere that

trying to open session to the Domino server and shows the title of sample

database.

1. We write a servlet TestDomino that is provided in Appendix C.1,  Java

servlet TestDomino  on page 159.

2. Compile the servlet with Java compiler.

3. Put the servlet class file to WebSphere servlets directory.

4. Configure the WebSphere to load the servlet.

5. To verify the connection between WebSphere and Domino, run the servlet

from the Web browser. We use the URL:

http://bdtest2/servlet/TestDomino?db=homepage&host=bdtest3&port=8000

where homepage is the homepage.nsf database file that is available by

default in a Domino server.

The result is similar to Figure 46 on page 51.

50

Linux Web Hosting with WebSphere, DB2, and Domino