This subsection describes how to set up JAR files in the class path of the EJB client application. The method of setting the JAR file to the class path differs depending upon the command used to invoke the EJB client application.

• Using the cjclstartap command
  When using the cjclstartap command, set up the JAR files in the class path with the option definition file (usrconf.cfg) of the EJB client application.
  For details on usrconf.cfg (option definition file for Java application), see 14.2 usrconf.cfg (option definition file for Java application) in the uCosminexus Application Server Definition Reference Guide.
  
• Using the vbj command
  When using the vbj command, set up the JAR files with the batch file or shell script file, or with the command arguments.
  

The following table describes the JAR files required for executing an EJB client application:

Table 3-12 JAR files required for executing the EJB client application

JAR file name	[Type]#1 JAR file location	Contents included	Commands
			cjclstartap	vbj
hitj2ee.jar	[Fixed] In Windows Cosminexus-installation-directory\CC\lib In UNIX /opt/Cosminexus/CC/lib	Class provided with the product	--	Y
HiEJBClientStatic.jar	[Fixed] In Windows Cosminexus-installation-directory\CC\client\lib In UNIX /opt/Cosminexus/CC/client/lib	Class provided with the product	--	Y
vbjorb.jar vbsec.jar	[Fixed] In Windows Cosminexus-installation-directory\TPB\lib In UNIX /opt/Cosminexus/TPB/lib	Class provided with the product	--	Y
cprf.jar	[Fixed] In Windows Cosminexus-installation-directory\PRF\lib In UNIX /opt/Cosminexus/PRF/lib	Class provided with the product	--	Y
hntrlibMj.jar or hntrlibMj64.jar #2 #3	[Fixed] In Windows Program-files\Hitachi\HNTRLib2\classes In UNIX /opt/hitachi/HNTRLib2/classes	Class provided with the product	--	Y
tpotsinproc.jar	[Transaction used] In Windows Cosminexus-installation-directory\TPB\lib In UNIX /opt/Cosminexus/TPB/lib	Class provided with the product	--	O
ejbserver.jar	[Transaction used] In Windows Cosminexus-installation-directory\CC\lib In UNIX /opt/Cosminexus/CC/lib		O	O
stubs.jar	[RMI-IIOP stubs] Either download from the J2EE server, or use dynamic class loading	RMI-IIOP stubs Stubs of the EJB object Stubs of the EJB home object Classes in which the stubs are referenced	O	O
numeric-value.jar	[RMI-IIOP interfaces] Download from the J2EE server	RMI-IIOP interfaces Remote interface Home interface Classes in which interfaces are referenced	Y	Y
User-created JAR file	User-created class	This is a user-created class used in the EJB client application. If the unique Filter class, the Formatter class or the Handler class created by the user is used in the user log functionality of the EJB client application, specify these classes also in the class path.#3	Y	Y

Legend:

Y: Must be specified in the class path.

O: If necessary, specify in the class path.

--: Need not be specified in the class path.

#1

The JAR files include the following types:

• [Fixed]
  The file name and location of the specified JAR file are fixed, irrespective of the number of applications invoked from the EJB client application or the contents.
  
• [Transaction used]
  If a transaction is used in the EJB client application, specify the corresponding JAR file. For details, see 3.20 Points to be considered when starting a transaction in the EJB client applications in the uCosminexus Application Server Common Container Functionality Guide.
  
• [RMI-IIOP stubs]
  Specify the JAR file corresponding to each application invoked from the EJB client application. Need not be specified when using dynamic class loading.
  
• [RMI-IIOP interfaces]
  If the RMI-IIOP interfaces are not obtained in the EJB client application, download and specify the JAR file corresponding to each application. If the RMI-IIOP interfaces are already obtained in the EJB client application, specify the obtained classes or the JAR files.
  

#2

Use a JAR file corresponding to the OS you are using. For HP-UX (IPF) and Linux (IPF), specify hntrlibMj64.jar. For other operating systems, specify hntrlibMj.jar. Note that if these JAR files are specified, output mode of the system log changes to a shared subdirectory mode. For details on the shared subdirectory mode, see 3.8.2 Output destination subdirectory of the system log.

#3

Specify for using the user log output functionality of the EJB client application. For details on how to specify the user log output settings for the EJB client applications, see 9.8 User log output settings for J2EE applications in the uCosminexus Application Server Expansion Guide.

Note

• When you use uCosminexus Client to create the EJB client environment, replace Cosminexus-installation-directory\CC in the storage directory with Cosminexus-installation-directory\CCL.
• When you use uCosminexus Client to create the EJB client environment, you cannot use the transactions of the EJB client application.
• When setting up JAR files in the class path, pay attention to the setup order of the JAR files.
  When using a transaction, set up tpotsinproc.jar and ejbserver.jar in the class path. In such a case, set up HiEJBClientStatic.jar even before ejbserver.jar.
  When using the performance analysis trace functionality, set up cprf.jar in the class path. In such a case, set up cprf.jar before setting up HiEJBClientStatic.jar.
  If you set up these files in the reverse order, an attempt to initialize the performance analysis trace will fail. Furthermore, if you specify these files in the reverse order, the message KDJE51008-W will be output with the reason code -4 when the log level of the EJB client application is set to Warning or higher. Note that when an attempt to initialize the performance analysis trace fails, the performance analysis trace will not be output, but you can continue with the processing of the EJB client application.