Third-party Java Components

The Websydian Java run-time makes use of a log component from the Apache Software Foundation (http://www.apache.org/):

log4j-1.2.9.jar: Copyright (C) 1999 The Apache Software Foundation. All rights reserved.

Log4j gives an administrator the possibility of enable logging at run-time without modifying the binary modules. The log4j module is designed so the disabled logging statements remain in the shipped code without incurring a heavy performance cost.

With Websydian and log4j it is possible to log to a file, NT Event logger, or a mail server. More information about log4j can be found at http://jakarta.apache.org/log4j/docs/index.html.

In order to log to a mail server the following run-time libraries must also be included in the class path:

mail-1.3.jar

Mail API from Sun (http://java.sun.com/products/javamail/).

activation-1.0.2.jar

JavaBeans^TM Activation Framework extension (http://java.sun.com/beans/glasgow/jaf.html).

All these components are shipped with the Websydian installation file.

Classpath

When a Websydian Java application, the Websydian Server, or the Relay Service is executed all the above libraries should be included in the classpath. E.g:

java -cp WsydDwa21.jar;log4j-1.2.9.jar;mail-1.3.jar;activation-1.0.2.jar websydianserver-f websydianserver.prop

In the documentation the string "WsydDwa21.jar;log4j-1.2.9.jar;mail-1.3.jar;activation-1.0.2.jar" will be referred to as classpath. If the jar files are not present in the current library or in the default classpath then each library file should be specified with a full path definition.