Siebel CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide > Installing and Configuring the Integration > Process of Configuring Siebel Business Applications >

Configuring JMS for Outbound Web Services Using Advanced Queuing

When updates are made in Siebel CRM to accounts or contacts, either a Siebel run-time event or a workflow policy is triggered to send the updated data to Oracle FLEXCUBE Universal Banking. The run-time event or workflow policy in turn causes one of the following Siebel workflows to be invoked:

• FINS BIB Account Info Update FC Workflow
• FINS BIB Contact Info Update FC Workflow

When each of these workflows is invoked, it submits a request, using the EAI JMS Transport business service, to the JMS queue hosted by Oracle FLEXCUBE Universal Banking. This topic describes how to set up the Java environment for the Integration and how to configure and test the EAI JMS Transport business service used in the Siebel outbound Web services.

This task is a step in Process of Configuring Siebel Business Applications.

Installing and Configuring the Java Environment

The following procedure describes how to set up your Java environment.

To install and configure your Java environment

1. Verify that Java Runtime Environment (JRE) 1.6 is installed on the computer on which your Siebel Server runs.

   For information on downloading JRE, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

2. Install the required JAR files:
   1. Copy the following Siebel JAR files from the SIEBSRVR_ROOT\CLASSES directory to D:\JMS.
      • Siebel.jar
      • SiebelJI_enu.jar

        where SIEBSRVR_ROOT is the installation directory for Siebel Server.

        NOTE:  If this directory is not present, then create it.

   2. Copy the Wlfullclient.jar file to D:\JMS.

      The wlfullclient.jar file is provided by Oracle FLEXCUBE Universal Banking, the Web service provider.

3. Create the jndi.properties file on the Siebel Server in the D:\JMS directory. The jndi.properties file specifies the connection values that the Siebel Server uses to look up queues and their connection factories dynamically. Specify the following values for the jndi.properties file:

   java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory

   java.naming.provider.url=FLEXCUBE ipaddress and port name

   java.naming.security.principal=weblogic

   java.naming.security.credentials=weblogic#1

   where FLEXCUBE ipaddress and port name is the remote method invocation (RMI) URL used to connect to Oracle FLEXCUBE Universal Banking.

4. Create the JVM subsystem used in Siebel CRM, and specify the profile parameters for the subsystem as shown in the following table.

   Name	Alias	Data Type	Value
   JVM Classpath	Classpath	String	D:\JMS\Siebel.jar;D:\JMS\SiebelJI_enu.jar;D:\JMS\wlfullclient.jar;.;D:\JMS
   JVM DLL Name	DLL	String	The path to the JVM library file, for example, in a Windows environment: C:\Sun\SDK\jdk\jre\bin\server\jvm.dll
   JVM Options	VMOPTIONS	String	JVM-specific options for the log file, for example: -Djms.log=D:\JMS\log\jms.log

   For detailed information on creating a JVM subsystem, see Transports and Interfaces: Siebel Enterprise Application Integration.

5. Stop and restart the Siebel Server for the changes to take effect.

Configuring and Testing the EAI JMS Transport Business Service

This topic describes how to configure and test the connection and queue information specified for the EAI JMS Transport business service. This service is invoked by the workflows that send updated contact and account data to Oracle FLEXCUBE Universal Banking from Siebel CRM.

The following procedure describes how to run the Business Service Simulator to test the EAI JMS Transport business service configuration.

To configure and test the EAI JMS Transport business service

1. Log in to the Siebel Financial Services application.
2. Navigate to the Administration - Business Service screen, then the Simulator view.
3. In the Simulator list, click New, and specify the values shown in the following table.

   Field	Value
   Service Name	EAI JMS Transport
   Method Name	CheckAll

4. In the Input Arguments list, specify the input parameters for the Business Service method by clicking New and specifying the values shown in the following table.

   Field	Value
   Test Case #	1
   Type	PropertySet
   Property Name	ConnectionFactory
   Property Value	JNDI name of the JMS connection factory, for example: java:comp/env/jms/MDBQCF Oracle FLEXCUBE Universal Banking provides this value.

5. To create an additional property set, click New again and specify the values shown in the following table.

   Field	Value
   Test Case #	1
   Type	PropertySet
   Property Name	SendQueue
   Property Value	JNDI name for the JMS queue. For example: MDB_QUEUE_DA Oracle FLEXCUBE Universal Banking provides this value.

6. Click Run to run the simulator for the business service.

Updating Queue and Connection Factory Details for Outbound Web Services

After verifying the queue and connection factory details using the Business Service Simulator, you must update the Integration workflows for outbound Web services with this information.

To update queue and connection factory details for outbound Web services

1. In Siebel Tools, navigate to the Workflow Processes Object List Editor.
2. Query for each of the following workflows in turn:
   • FINS BIB Account Info Update FC Workflow
   • FINS BIB Contact Info Update FC Workflow
3. For each of the workflows, perform the following steps:
   1. Change the status of the workflow to In Progress.
   2. Right click the workflow, then select Edit Workflow Process.
   3. In the Send Message to JMS Queue step of the workflow, change the values for the following process properties to the values tested in Configuring and Testing the EAI JMS Transport Business Service:
      • ConnectionFactory
      • SendQueue
   4. Save the changes.
   5. Publish and activate the workflow by clicking the Publish/Activate button on the WF/Task Editor toolbar.

      For detailed information on editing workflows using Siebel Tools, see Siebel Business Process Framework: Workflow Guide and Using Siebel Tools.