Transports and Interfaces: Siebel Enterprise Application Integration > EAI Java Business Service >

Troubleshooting the Java Business Service


A common source of errors is the Java CLASSPATH. Remember the following conventions of the Java CLASSPATH:

  • On UNIX, CLASSPATH entries are separated by a colon (:); on Windows, by a semicolon (;).
  • If .class files are to be used instead of .jar files, the root directory (for example, the one containing the com folder) must be listed in the CLASSPATH.

If the Java business service states that the com.siebel.data.SiebelPropertySet class is not found, then the Siebel.jar files are not correctly specified in the CLASSPATH.

If the Java business service implementation cannot be found, then the .class or .jar file containing its code is not properly specified in the CLASSPATH.

To help troubleshoot CLASSPATH errors, you can use one of the following utilities to see where the Application Object Manager or Web client is looking for the .jar files:

  • Windows: filemon. For more information on filemon, see:

    http://www.microsoft.com

  • UNIX: truss/strace
Transports and Interfaces: Siebel Enterprise Application Integration Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.