Download

To download a WCT jar please go to:

Jars directory

and choose the version you like.

External Dependencies

The WCT product in its current version (1.3.1) makes use of some external libraries in its operations. Namely it depends on set of java libraries:

  • axis-1.3.jar provided by The Apache Software Foundation
  • axis-jaxrpc-1.3.jar provided by The Apache Software Foundation
  • axis-saaj-1.3.jar provided by The Apache Software Foundation
  • log4j-1.2.8.jar library provided by The Apache Software Foundation
  • wsdl4j-1.4.jar library provided by The Apache Software Foundation
  • jdom-1.0.jar xml parsing library provided by Jason Hunter and Brett McLaughlin
  • gomclient-20060508.jar library released with K-WfGrid license by ACC CYFRONET AGH
  • gworkflowdl-1.0.1.jar library released with The Fraunhofer FIRST license agreement by Fraunhofer FIRST
  • jena-2.3.jar semantic toolkit library released with special Jena license
  • junit-3.8.1.jar library provided by JUnit.org
  • kowariclient-1.1.jar library released with K-WfGrid license by ACC CYFRONET AGH
Further dependencies needed by the above software:
  • activation-1.0.2.jar
  • commons-codec-1.3.jar
  • commons-discovery-0.2.jar
  • commons-httpclient-3.0.jar
  • commons-logging-1.0.3.jar
  • concurrent-1.3.4.jar
  • gom-client-api-1.0.jar
  • icu4j-2.6.1.jar
  • mail-1.3.3_01.jar
  • servlet-api-2.3.jar
  • stax-1.1.1-dev.jar
  • stax-api-1.0.jar
  • xercesImpl.jar
  • xfire-all-1.0.jar
All the above software is provided for use free of charge on the basis of open source licenses, either: In general, one may reuse all the libraries any way for the scientific or educational purposes (in same cases in order to use them fom commercial purposes there is a need to acquire the written consent of their respective authors).

Configuration

In order to tweak some functions of WCT you may need to modify wct.props file. This is located in the main directory of the WCT jar file - you should be able to easily access and modify its contents. However if not, you may extract the file, modify it and then be sure to its location in the classpath when you run Java with WCT. The contents of the new copy should overwrite the older ones.

Here is a list of the configuration options one can find useful:

  • TODO :)

You may also change the level of WCT's verbosity with the usual log4j.properties file (also located in the main WCT jar). Simple switch of the log4j.logger.net.kwfgrid.wct logger to WARN mode should do the job (and leave you with just the most important logging).

Manual WCT Build

In order to build the WCT manually you need:

  • maven Java build tool in its 1.x version
  • access to http://cvs.ui.sav.sk/cgi-bin/cvsweb.cgi/ CVS code repository
When you extract the kwfgrid/wct project to your local filesystem and setup the maven environment correctly, the simple command of:

$> maven jar

should download all the needed jar dependencies, compile, test and build your very own WCT release in target subdirectory.