The IBM JACL implementation does not pick up the TCL_CLASSPATH
variable.

For example; adding the Derby Java database jars.

lappend x C:/IBM/Cloudscape_10.1/lib/derby.jar
lappend x C:/IBM/Cloudscape_10.1/lib/derbyclient.jar
lappend x C:/IBM/Cloudscape_10.1/lib/derbynet.jar
lappend x C:/IBM/Cloudscape_10.1/lib/derbytools.jar

set env(TCL_CLASSPATH) $x

The jacl command "java::import org.apache.derby.jdbc.EmbeddedDriver"

generates

WASX7017E: Exception received while running file
"c:\scripts\websphere\jacl\getJ
VMINFO.tcl"; exception information: com.ibm.bsf.BSFException: error
while eval'i
ng Jacl expression: can not import class
"org.apache.derby.jdbc.EmbeddedDriver",
it does not exist

The work around is to add the required jar files to the WAS_CLASSPATH
in the WSADMIN bat file.

....................
....................
:runcmd

set WAS_CLASSPATH=C:\IBM\Cloudscape_10.1\lib\derby.jar;%WAS_CLASSPATH%

"%JAVA_HOME%\bin\java" %javaoption% %CONSOLE_ENCODING% %DEBUG%
"%CLIENTSOAP%" "%CLIENTSAS%"
"-Dcom.ibm.ws.scripting.wsadminprops=%WSADMIN_PROPERTIES%"
-Dcom.ibm.ws.management.standalone=true
"-Duser.install.root=%USER_INSTALL_ROOT%"
"-Dwas.install.root=%WAS_HOME%" "-Dwas.repository.root=%CONFIG_ROOT%"
"-Dserver.root=%WAS_HOME%" "-Dlocal.cell=%WAS_CELL%"
"-Dlocal.node=%WAS_NODE%" "-Dcom.ibm.itp.location=%WAS_HOME%\bin"
"-classpath" "%WAS_CLASSPATH%;%WAS_HOME%\lib\jython.jar"
"-Dws.ext.dirs=%WAS_EXT_DIRS%" com.ibm.ws.bootstrap.WSLauncher
com.ibm.ws.scripting.WasxShell %*
...............
...............

This allows use of the Derby database for WAS performance data logging.



Regards.


PATRICK FINNEGAN.
WebSphere Consultant.

[ Post a follow-up to this message ]

In article <1131434168.479276.61200@g44g2000cwa.googlegroups.com>,
Patrick Finnegan <chppxf1@yahoo.com.au> wrote:
>The IBM JACL implementation does not pick up the TCL_CLASSPATH
>variable.
>
>For example; adding the Derby Java database jars.

[ Post a follow-up to this message ]