Using LISA with IBM WebSphere

Document ID : KB000048483
Last Modified Date : 14/02/2018
Show Technical Document Details

This note has been developed specifically for WebSphere Application Server (WAS) versions 5.x and 6.0.

When is this needed?

For LISA to test web sites, web services, and database access, no additional configuration is needed. You can use LISA with our supplied Java runtime.

For those of you who need to test EJBs, Messaging, or go in-container, the following information is very important.

IBM JDK Required

Please insure you are running LISA in the IBM JVM or you have installed the appropriate pluggable client into your compliant non-IBM JVM.
You can tell LISA to run the IBM JDK by setting an environment variable LISA_JAVA_HOME=(AN IBM JDK HOME).

If you have installed LISA on a computer that also has WAS installed, the right setting might look like this:

set LISA_JAVA_HOME=c:\program Files\ibm\websphere\appserver\java


Note that LISA needs the IBM JDK, not a JRE. The biggest difference for LISA is that we need the tools.jar that is supplied in the JDK but is not packaged in the JRE.
If LISA gives you a dialog box asking for the tools.jar file then you are not running the IBM JDK.

EJB & MQ Support files

LISA will need the Websphere client drivers to test native WAS functionality. These files change from version to version of WAS and are not redistributable by vendors other than IBM.

As of WAS 5.x or 6.0, the following files were needed. The example we are showing is a way to make these files available to WAS via an environment variable:

# this is an example, your directory with these files will likely be different!
set WAS_LIB=c:\program Files\ibm\websphere\appserver\java\lib

set LISA_PRE_CLASSPATH=%WAS_LIB%\bootstrap.jar;%WAS_LIB%\ecutils.jar;%WAS_LIB%\ffdc.jar;%WAS_LIB%\hlcbe101-13.jar;%WAS_LIB%\ibmorb.jar;%WAS_LIB%\idl.jar;

Additional Steps

There are a few more steps I've had to take in order to get the latest versions of LISA to work with the IBM JDK. Setting up this environment is tricky. I've needed to do all of these at some point, but maybe not all of them at the same time.
Copy the IBM JDK and change some settings In some cases the IBM JDK's default SSL settings interfere with LISA's ability to reach the license server.

  1. Create a copy of the IBM JDK directory; this is necessary because we don't want to try running WebSphere with these settings. An easy way to do this is to rename LISA_HOME/jre to something like LISA_HOME/jre.bak, and copy the IBM JDK into LISA_HOME/jre
  2. Edit IBM_JRE_HOME/lib/security/
    Comment out these lines:
    Uncomment these lines:

CORBA ORB system property If you're using JNDI then you will probably need to override the default CORBA ORB class.

  1. Add the following to the LISA_MORE_VM_PROPS:

ext.dirs property Occasionally some class conflicts can only be solved by adding WebSphere's classes to the JDK's boot classpath.

  1. Add the following to the LISA_MORE_VM_PROPS:
    "-Djava.ext.dirs=C:\Program Files\IBM\WebSphere\AppServer\lib"
    Replace 'C:\Program Files\IBM\WebSphere\AppServer' with the location of your WebSphere install.

Batch file launcher The Install4j launcher can still mess the environment we're working to create. To work around this you can create your own launcher batch file.

  1. Make batch file, LISA_HOME/bin/runlisa.bat
  2. Add one line to the batch file:
    @call lisa.bat com.itko.lisa.gui.TestManager