Configuring Java Subsystem for Fusion Middleware 10g Integration

In addition to performing the setup tasks for integrating Fusion Middleware in the Siebel installation guide, perform the following procedure.

Note: Paths in this procedure assume you are running the Siebel Server on the Windows operating system. They must be modified whether the Siebel Server is running on a UNIX operating system.

To configure Java subsystem for Fusion Middleware 10g Integration

Extract oc4j-extended.zip the following location to a folder in a computer where the Siebel Server is installed, such as D:\JMS folder.
http://download.oracle.com/otn/java/oc4j/101330/oc4j_extended_101330.zip
Copy Siebel.jar and SiebelJI_enu to D:\JMS folder, these jar files can be found in Siebel Server installation directory\classes folder
Copy jndi.jar file from FMW to D:\JMS\j2ee\home\lib folder.
Copy com/evermind/util/JCAProperties.class from the oc4j-internal.jar file to the D:\JMS folder.
Create a file with name jndi.properties with following details in the path D:\JMS:
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory

java.naming.provider.url=opmn:ormi://IP Address of the FMW server:OPMN Port No:oc4j_soa

java.naming.security.principal=anonymous

For example:
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory

java.naming.provider.url=opmn:ormi:// 152.68.240.154:6009:oc4j_soa

java.naming.security.principal=anonymous
Make sure that there are no extra spaces in the jndi.properties file.

Create a Named Subsystem in the Siebel application through the server management by completing the following steps:

Connect to the server manager from the command prompt from the bin directory of the Siebel installed folder with the following command.
```
Srvrmgr /g gatewayserver /e enterpriseserver /s siebelserver /u userid /p password
```
Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin

Run the following command to create the named subsystem and add the jar file into the class path.

Create named subsystem JAVA for subsystem JVMSubSys with

DLL=C:\Sun\SDK\jdk\jre\bin\server\jvm.dll, CLASSPATH = 
D:\JMS;D:\JMS\Siebel.jar;D:\JMS\rdbms\jlib\aqapi.jar;D:\JMS\jdbc\lib\ocrs12.jar
;D:\JMS\jdbc\lib\ojdbc14dms.jar;D:\JMS\jdbc\lib\orai18n.jar;D:\JMS\SiebelJI_enu
.jar;D:\JMS\j2ee\home\lib\adminclient.jar;D:\JMS\j2ee\home\lib\jndi.jar;D:\JMS\
j2ee\home\lib\jta.jar;D:\JMS\j2ee\home\oc4jclient.jar;D:\JMS\j2ee\home\lib\bcel
.jar;D:\JMS\j2ee\home\lib\jms.jar;D:\JMS\j2ee\home\lib\javax77.jar;D:\JMS\lib\d
ms.jar;D:\JMS\opmn\lib\optic.jar;D:\JMS\j2ee\home\lib\ejb.jar;., VMOPTIONS= 
D:\JMS\log\jms.log

For the UNIX environment the CLASSPATH is separated by : (colon). For the Windows environment it is separated by ; (semicolon). So, the command for the UNIX environment is as follows:

Create named subsystem JAVA for subsystem JVMSubSys with

DLL= /usr/jdk1.5.0_06/jre/lib/sparc/client/libjvm.so, CLASSPATH = /export/home/
qa1/JMS:/export/home/qa1/JMS/Siebel.jar:/export/home/qa1/JMS/rdbms/jlib/
aqapi.jar:/export/home/qa1/JMS/jdbc/lib/ocrs12.jar:/export/home/qa1/JMS/jdbc/
lib/ojdbc14dms.jar:/export/home/qa1/JMS/jdbc/lib/orai18n.jar:/export/home/qa1/
JMS/SiebelJI_enu.jar:/export/home/qa1/JMS/j2ee/home/lib/adminclient.jar:/
export/home/qa1/JMS/j2ee/home/lib/jndi.jar:/export/home/qa1/JMS/j2ee/home/lib/
jta.jar:/export/home/qa1/JMS/j2ee/home/oc4jclient.jar:/export/home/qa1/JMS/
j2ee/home/lib/bcel.jar:/export/home/qa1/JMS/j2ee/home/lib/jms.jar:/export/home/
qa1/JMS/j2ee/home/lib/javax77.jar:/export/home/qa1/JMS/lib/dms.jar:/export/
home/qa1/JMS/opmn/lib/optic.jar:/export/home/qa1/JMS/j2ee/home/lib/ejb.jar:., 
VMOPTIONS= /export/home/qa2/JMS/log/jms.log

Make sure that the path is correct for all the files and that the CLASSPATH ends with a . (dot). Replace qa2 with the appropriate folder name.

Log in to the Siebel application and navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile Configuration view, and complete the following steps:
1. Query for the Profile with Alias Name JAVA in the profile list and make sure the parameters are correct.
2. For the Windows environment, edit the value of VMOPTIONS to:
```
-Djms.log=D:\JMS\log\jms.log
```
3. For the Solaris environment, edit the value of VMOPTIONS to:
```
-Xusealtsigs -Xrs -Djms.log=/export/home/qa2/JMS/log/jms.log.
```
Make sure that the JMS/log folder exists and has the write permission.
Restart the Siebel Server.
Note: For more information, see the Siebel Enterprise Application Integration (EAI) documentation on the Siebel Bookshelf.