• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

IBM JACL and TCL_CLASSPATH.

 
Ranch Hand
Posts: 179
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
reply
    Bookmark Topic Watch Topic
  • New Topic