Configuring Java Subsystem for Fusion Middleware 11g 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 if the Siebel Server is running on a UNIX operating system.

To configure Java subsystem for Fusion Middleware 11g Integration

1. Get the wlfullclient.jar file from the FMW/AIA team. If you cannot get this file, then perform the following steps to create wlfullclient.jar in the FMW server:

   1. WinScp to the SOA server.

   2. Change directories to the server/lib directory. For example, go to the WL_HOME/server/lib.

   3. Execute the command:

      java -jar wljarbuilder.jar
      

      The wlfullclient.jar file is created.

2. Remotely login to the Siebel installed server.

3. Get the files Siebel.jar and SiebelJI_enu.jar from the following directory:

   siebel installation\ses\siebsrvr\classes
   

4. Copy the wlfullclient.jar, Siebel.jar and SiebelJI_enu.jar to the directory D:\JMS. If this directory does not exist, then create it.

5. Prepare the jndi.properties file with the following values:

   java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
   java.naming.provider.url=t3://FMW_HOST:SOA_PORT
   java.naming.security.principal=UserName
   java.naming.security.credentials=Password 
   

   Note: If Oracle Application Integration Architecture is running in a clustered environment and has a setup proxy host, then jndi.properties have following URL: java.naming.provider.url=http://FMW_HOST:PROXY_PORT

6. Create the JAVA Subsystem using the Siebel Web application as follows:

   1. Connect to the server manager from the bin directory of the Siebel installed folder by entering the following command from the command prompt:

      Srvrmgr /g gatewayserver /e enterpriseserver /s siebelserver /u userid /p password
      

      For example:

      srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin
      

   2. Enter the following command to create the named subsystem:

      Create named subsystem JAVA for subsystem JVMSubSys
      

   3. Add parameters with the aliases CLASSPATH, DLL, and VMOPTIONS, as described in the tables that follow.

      The following table specifies the Name, Data Type, and Value values to enter for the parameters with aliases CLASSPATH, DLL, and VMOPTIONS.

      Alias	Name	Data Type	Value
      CLASSPATH	JVM Classpath	String	D:\JMS;D:\JMS\Siebel.jar;D:\JMS\SiebelJ I_enu.jar;D:\JMS\wlfullclient.jar;.
      DLL	JVM DLL Name	String	C:\Sun\SDK\jdk\jre\bin\server\jvm.dll
      VMOPTIONS	JVM Options	String	-Djms.log=D:\JMS\log\jms.log

   The following table specifies the Scope, Type, Description, and Visibility values to enter for the parameters with aliases CLASSPATH, DLL, and VMOPTIONS.

   Alias	Scope	Type	Description	Visibility
   CLASSPATH	Subsystem	JVM Configuration Subsystem	JVM Classpath	Basic
   DLL	Subsystem	JVM Configuration Subsystem	JVM DLL Name	Basic
   VMOPTIONS	Subsystem	JVM Configuration Subsystem	JVM Options	Basic

7. Create the Simulator (with the service name: EAI JMS Transport and Method name: CheckAll).

8. In the Input Argument Section, create Test Case 1 with the values in the following table.

   Type	Property Name	Property Value
   PropertySet	ConnectionFactory	jms/TestQueueCF
   PropertySet	SendQueue	jms/TestQueue

9. Click Run to verify the setup in the simulator.

   No error messages appear after the run.