Requirements for Implementing a Java Business Service

To implement a Java business service, the following software must be installed and properly configured on each Siebel Server or Siebel Mobile and Developer Web Clients:

A Java Runtime Environment (JRE)
All necessary Java code
A configured named subsystem of type:
- JavaContainerSubSys for a 64-bit JRE

The named 64-bit subsystem supplies the following parameters to the JBS: CONTAINERURL, CLASSPATH, and OPTIONS. These parameters are described as follows.

CONTAINERURL. The URL to the Java Web Container server for all the JBS requests.
CLASSPATH. The classpath used by the JVM.
The classpath must include the location of the jndi.properties file.
Ensure that the file contains the file name of the jndi.properties file.
With 64-bit Java, the required JAR files for the execution of JMS and any call to a custom Java Business Service must reside on the Java Web Container server. The Siebel.jar and SiebelJI_enu.jar files are packaged within the WAR file. All other JMS provider JAR files, or customer-created Java Business Service .jar files depending on customer usage, must be placed in the lib subdirectory of the applicationcontainer_internal directory on the Siebel Server installation.

For example, if you have created a custom Java Business Service and have packaged it in a .jar file named MyCustomJBS.jar, you would place this .jar file in the following directory, \applicationcontainer_internal\lib\MyCustomJBS.jar.

Note: If you have different versions of your .jar file with different (or even the same) functionality but with the same name, you cannot put them in the same directory. The operating system will not allow it. Consider consolidating all the functionality in a single .jar file or naming the .jar files differently to reflect their differing functionality. You will not be able to put them in separate directories and specify them in the CLASSPATH variable. This will not work with the Siebel application as the lib directory (as specified previously) is the only location you can place custom .jar files.
OPTIONS. In the Java 64-bit subsystem, OPTIONS is not used. Therefore, OPTIONS must be set using the CATALINA_OPTS option in the setenv.bat or setenv.sh file of the javacontainer based on the operating system. An example is as follows:
Windows:
```
javacontainerX\bin\setenv.bat
set CATALINA_OPTS=-Djava.compiler=NONE
```
UNIX:
```
File: javacontainerX/bin/setenv.sh
CATALINA_OPTS="-Djava.compiler=NONE"
```

The following topics are also discussed here: