Bookshelf Home | Contents | Index | PDF     

Siebel Communications Guide > Overview of Siebel Communications > Configuring Communications, Order-to-Cash, and Master Data Management Integration >

Advanced Queue Configuration

The subtopics in this topic describe how to perform advanced queue configuration.

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

  1. Extract oc4j-extended.zip from http://download.oracle.com/otn/java/oc4j/101330/oc4j_extended_101330.zip to a folder in a computer where the Siebel Server is installed, such as D:\JMS folder.
  2. Copy Siebel.jar and SiebelJI_enu to D:\JMS folder, these jar files can be found in Siebel Server installation directory\classes folder
  3. Copy jndi.jar file from FMW to D:\JMS\j2ee\home\lib folder.
  4. Copy com/evermind/util/JCAProperties.class from the oc4j-internal.jar file to the D:\JMS folder.
  5. 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.

  6. Create a Named Subsystem in the Siebel application through the server management by completing the following steps:
    1. 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

    1. 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\dms.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 above command for UNIX environment 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.

  7. 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

    1. 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.

  8. Restart the Siebel Server.

    NOTE:  For more information, see the Siebel Enterprise Application Integration (EAI) documentation on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.

Configuring Corresponding Web Services for Advanced Queue

This topic contains information about how to configure corresponding Web services for AQ. AQ configuration involves configuring JMS messaging between Siebel Business Applications and the Oracle SOA suite using Oracle Advanced Queuing. For more information about this configuration, see Transports and Interfaces: Siebel Enterprise Application Integration.

Use the following procedure to configure corresponding Web services for AQ.

To configure corresponding Web services

  1. Navigate to the Administration - Web Services screen, then the Outbound Web Services view and query for SWI*.
  2. Change the transport to JMS and address as:

    jms://queue name@connection factory

    queue name is in the following format:

    java:comp/resource/ Resource Provider Name as configured/Queues/queue name

    connection factory is in the following format:

    java:comp/resource/Resource Provider Name as configured/QueueConnectionFactories/QCF

    Queues must have been created as part of Oracle Application Integration Architecture installation. Refer the queue name in this step.

  3. To locate the Connection Factory Name, log in to Application Server control, and navigate to oc4j_soa ' Administration, then Database Persistence.

    Here you can find the Resource Provider Name if it is configured.

    Example: jms://java:comp/resource/AIA_JMS_RP/Queues/AIA_SALESORDERJMSQUEUE@java:comp/resource/AIA_JMS_RP/QueueConnectionFactories/QCF

  4. After changing the address, click Clear Cache.
  5. If you are using the Communications PIP or the Order To Cash PIP, then proceed to one of the following steps:
    • Communications PIP. Go to Step 6.
    • Order To Cash PIP. Go to Step 7.
  6. For the Communications PIP, configure the following Web services:
    • SWICreateAdjustment

      Example for FMW 10g:

    jms://java:comp/resource/AIA_JMS_RP/Queues/AIA_CMUREQADJIOJMSQUEUE@java:comp/resource/AIA_JMS_RP/QueueConnectionFactories/QCF

    Example for FMW 11g:

    jms://jms/aia/AIA_CMUREQADJIOJMSQUEUE@jms/aia/COMMS_ADJUSTMENT_CONSUMER

    • SWISpecialRatingList

      Example for FMW 10g:

    jms://jms/aia/AIA_SPECIALRATINGJMSQ@jms/aia/COMMS_SPECIALRATINGLIST_CONSUMER

    Example for FMW 11g:

    jms://jms/aia/AIA_SPECIALRATINGJMSQ@jms/aia/COMMS_SPECIALRATINGLIST_CONSUMER

    • SWISubmitOrder

      Example for FMW 10g:

    jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER

    Example for FMW 11g:

    jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER

  7. For the Order To Cash PIP, configure the following Web services:
    • SWISubmitOrder_o2c

      Example for FMW 10g:

    jms://java:comp/resource/DBConnect/Queues/JMSUSER.AIA_QUOTEJMSQUEUE@java:comp/resource/DBConnect/QueueConnectionFactories/QCF

    Example for FMW 11g:

    jms://jms/aia/AIA_SiebelSalesOrderJMSQueue@jms/aia/AIASiebelCF

    • SWISubmitQuote_o2c

      Example for FMW 10g:

    jms://java:comp/resource/DBConnect/Queues/JMSUSER.AIA_QUOTEJMSQUEUE@java:comp/resource/DBConnect/QueueConnectionFactories/QCF

    Example for FMW 11g:

    jms://jms/aia/AIA_SiebelQuoteJMSQueue@jms/aia/AIASiebelCF

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

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

    Create named subsystem JAVA for subsystem JVMSubSys

    1. 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\SiebelJI_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.

    
Siebel Communications Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.