To run EJB clients, you must have:

• A Java Runtime Environment (JRE) or JDK installation, version 1.4.2 or later. Compatible versions of JDK 1.4 and JDK 1.5 are included in the EAServer client runtime installation.

• An EAServer client runtime installation. The Java class path must contain the EAServer JAR file lib/eas-client-14.jar or lib/eas-client-15.jar to run in JRE 1.4 or JRE 1.5, respectively. If you package these classes in a different archive or location, you must set the djc.home Java system property to indicate the location of the EAServer installation. For example:

  java -Ddjc.home=%DJC_HOME% com.foo.MyClass
  

  If you do not set this property, the client runtime infers the default from the first class path entry that ends with lib/eas-client-14.jar or lib/eas-client-15.jar.

• Stubs for the components that your client invokes.

EAServer generates client stubs on demand. If stubs are not available, the client runtime generates and compiles stub classes when you first invoke a component.

You must have a full JDK installation to generate compiled stubs at runtime. To deploy client applications to run in a JRE installation, you must include the generated stubs. When you deploy an EJB-JAR file, EAServer automatically creates stubs under the genfiles/java/classes subdirectory of the EAServer installation. Stub classes are in the Java package named by appending iiop_stubs to the package name of the interface class. For example, for interface com.sybase.easerver.tutorials.ejb.Query, the Java stub package is com.sybase.easerver.tutorials.ejb.iiop_stubs.