Bookshelf Home | Contents | Index | PDF     

Siebel Application Integration for Oracle Fusion Middleware Guide > Installing, Configuring, and Upgrading SAI for Oracle Fusion Middleware > Process of Configuring SAI for Oracle Fusion Middleware for Outbound Web Services >

Configuring the Siebel Server to Use SAI for Oracle Fusion Middleware for Outbound Web Services

This topic describes how to configure the Siebel Server to use SAI for Oracle Fusion Middleware for outbound Web services. It describes how to set the CLASSPATH, VMOPTIONS, and DLL parameters for the EAIOutboundJvmSubsys JVM (Java Virtual Machine) outbound named subsystem.

This task is a step in Process of Configuring SAI for Oracle Fusion Middleware for Outbound Web Services.

NOTE:  This task is only applicable if you are using outbound Web services in your deployment.

The parameters are described in the following table:

Parameter
Description

CLASSPATH

It sets the JAR file names in the classpath so that the Siebel Server JVM loads the required classes.

VMOPTIONS

It sets the EAIOutboundlogFile and EAIOutboundlogLevel parameters for the Siebel outbound Web service log file.

TIP:   You can also use VMOPTIONS to pass extra arguments that are related to the JVM, for example, heap size, stack size, and so on.

DLL

It sets the jvm.dll that handles the JVM on a Siebel Server. That is, the value in this parameter points to the DLL on a Windows computer that handles the JVM for the Siebel Server.

To configure Siebel Business Applications to use SAI for Oracle Fusion Middleware

  1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile Configuration view.
  2. In the Profile Configuration list, query the Alias field for:

    EAIOutboundJvmSubsys OR EAIOutboundSubsys

  3. Provide values for the EAIOutboundJvmSubsys profile (named subsystem) parameters as shown in the following table.
    Parameter
    Value

    Classpath

     

    SIEBEL_HOME\CLASSES\Siebel.jar;SIEBEL_HOME\CLASSES\jaxws-rt.jar;SIEBEL_HOME\CLASSES\wlfullclient.jar;SIEBEL_HOME\CLASSES\
    SiebelJI_    language.jar;SIEBEL_HOME\CLASSES\xml.jar;SIEBEL_HOME\CLASSES\xmlparserv2.jar;SIEBEL_HOME\CLASSES\webserviceclient+ssl.jar

    where:

    • SIEBEL_HOME is the installation directory for Siebel Business Applications software.
    • xml.jar and xmlparserv2.jar come from the Oracle WebLogic Server installation directory (ORACLE_HOME).
    • SiebelJI_language.jar is specific to your environment.
    • webserviceclients+ssl.jar is specific to SSL configuration.

    TIP:   For Windows, use a semicolon (;) as the separator; for UNIX, use a colon (:).

    DLL

     

    path_DLL_uses_to_set_load_jvm.dll

    NOTE:  This value is the path pointing to the jvm.dll that is loaded by the Siebel Server to handle the JVM of the Siebel Server.

    VMOPTIONS

    -Xrs -Djava.compiler=NONE -DEAIOutboundlogFile=EAIOutbound
    -DEAIOutboundlogLevel=DEBUG

  4. Provide values for the EAIOutboundSubsys profile (named subsystem) parameters as shown in the following table.
    Parameter
    Value
    Description

    EAI Outbound Context Factory

    weblogic.jndi.WLInitialContext Factory

    An initial context factory class that obtains the reference to an Enterprise Java Bean deployed for each outbound proxy service on Oracle WebLogic Server.

    EAI Outbound Provider URL

    t3://weblogicserver:7101

    URL used to connect to Oracle WebLogic Server. The communication protocol is t3.

    EAI Outbound Security Credentials

    ********* (asterisks)

    The password used for authentication on Oracle WebLogic Server.

    EAI Outbound Security Principal

    weblogic

    The user name used for authentication on Oracle WebLogic Server.

    EAI Outbound ConnectionFactory

    Connection Factory JNDI Name

    If the transport type is JMS, then this parameter specifies the queue connection factory JNDI name.

    EAI Outbound ReceiveQueue

    Receive Queue JNDI Name

    If the transport type is JMS, then this parameter specifies the receive queue JNDI name from which messages are read by the Siebel application.

    EAI Outbound ReceiveTimeout

    3000

    If the transport type is JMS, then this parameter specifies the time the JMS service waits for the response to be received from Oracle WebLogic Server before the server times out.

    EAI Outbound SendQueue

    Send Queue JNDI Name

    If the transport type is JMS, then this parameter specifies the send queue JNDI name on which messages will be sent by the Siebel application.

    EAI Outbound Transport Type

    RMI or JMS

    This parameter specifies the communication type between the Siebel application and Oracle WebLogic Server. Transport types supported are RMI and JMS.

    EAI Outbound Server Type

    Weblogic

    This parameter specifies the application server.

    NOTE:  The following parameters are specific to JMS: EAIOutboundConnectionFactory, EAIOutboundReceiveQueue, and EAIOutboundSendQueue.

    
Siebel Application Integration for Oracle Fusion Middleware Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.