Siebel Application Integration for Oracle Fusion Middleware Guide > Deploying Siebel Resource Adapters by Using SAI for Oracle Fusion Middleware >

Process of Deploying Siebel Resource Adapters Using SAI for Oracle Fusion Middleware

The resource adapter is the core component that provides the link between Siebel Business Applications and the Oracle WebLogic Server for SAI for Oracle Fusion Middleware. You use the Deployment wizard in SAI for Oracle Fusion Middleware to deploy resource adapters. A many-to-many relationship exists between resource adapters and Siebel instances. For more information about resource adapters, see About Resource Adapters.

To deploy a resource adapter using SAI for Oracle Fusion Middleware, perform the following tasks:

1. Make sure the Oracle WebLogic Server is running.
2. Start Oracle JDeveloper if it is not already active.
3. Select File, and then click the New menu item.
4. In the New Gallery dialog box, perform the following:
   1. In the Business Tier category, select Siebel Application Integration for Oracle Fusion Middleware.
   2. Select the Deployment item, and then click OK.
5. At the Welcome to the Deployment Wizard screen, click Next.
6. Select Siebel Resource Adapter as the deployment type, and then click Next.
7. Enter the resource adapter parameters by doing the following:
   1. Enter the Siebel Resource Adapter Name, if you do not want to accept the default.

      By default, the resource adapter name is SiebelResourceAdapter.

   2. Click Edit ra.xml to enter the XML parameters.

      Some settings are described in the following table.

      NOTE:  The Advanced Settings enable you to configure Siebel Server load balancing and Secure Sockets Layer (SSL). The Outbound Resource Adapter settings apply to outbound Web services with JMS and the transport type.

      Parameter	Description
      Siebel Server Parameters
      Siebel Server Host Name	The name of your Siebel Server. By default, this parameter is set to localhost.
      Port	The listening port for the SCBroker server component. By default, this parameter is set to 2321. NOTE:  This field is ignored when using load balancing on the Siebel Server.
      User Name	The name of the Siebel user that is configured for default connections. Use this user name for creating the credential map. Credential mapping is the process whereby a legacy database is used to obtain an appropriate set of credentials to authenticate users with a target resource. Oracle WebLogic Server uses credential mapping to map credentials used by Oracle WebLogic Server users to credentials used in a legacy or remote system. Oracle WebLogic Server then uses the credential maps to log in to a remote system on behalf of a user who has already been authenticated. For more information on credential mapping, see About Protecting User Names and Passwords for SAI for Oracle Fusion Middleware. NOTE:  It is recommended that you assign a user name with minimal credentials, for example, you might assign an anonymous user.
      EAI OM Alias	The alias for the Enterprise Application Integration Object Manager. By default, this parameter is set to EAIObjMgr_enu. Keep this setting unless you have configured the object manager with a different alias.
      Enterprise Name	The name of your Siebel Enterprise Server. By default, this parameter is set to siebel. Keep this setting unless you have a different name for your enterprise.
      B2BMode	This mode enables a connection between Oracle WebLogic Server and the Siebel Server to operate under the auspices of a service user; that is, no impersonation occurs and transactions are run in the context of the service user. By default, B2B mode is not selected, which means requests are executed in B2C mode. For more information, see About Protecting User Names and Passwords for SAI for Oracle Fusion Middleware. You must specify a B2B User Name if this check box is selected.
      B2B User Name	The service user name. Check the B2B Mode check box to enter the user name. Use this user name for creating the credential map. For more information about credential mapping, see About Protecting User Names and Passwords for SAI for Oracle Fusion Middleware.
      Advanced Settings
      Session Timeout	The number of minutes a session can remain inactive before a user is logged out and the session is closed. By default, this parameter is set to 15 minutes.
      Connections per EAI OM	Specifies the number of physical sockets that are created from the resource adapter to the Enterprise Application Integration Object Manager process.
      Session Token Max Age	The total number of minutes that a session can remain open before a user is logged out and the session is closed. By default, this parameter is set to 2880 minutes.
      Session Token Timeout	The number of minutes that a session can be idle before the session is locked. By default, this parameter is set to 15 minutes.
      JNDI Cache Duration	The value of this parameter sets the cache duration for the Java Naming and Directory Interface (JNDI) object. The cached JNDI object is reused for subsequent inbound requests. By default, this parameter is set to 15 minutes.
      Max Anonymous User	Specifies the maximum number of Web service sessions for anonymous users that are permitted. By default, this parameter is set to 10.
      Transport	Specifies the type of transport protocol between Oracle WebLogic Server and the Siebel Server. The choices are: TCP and SSL. By default, this parameter is set to TCP. If you choose SSL, then a Parameters option appears that you can click to specify the SSL-related parameters. For more information about setting these parameters, see Configuring Siebel Server Load Balancing and SSL for SAI for Oracle Fusion Middleware.
      Encryption	Specifies whether encryption is used for data transmission from Oracle WebLogic Server and the Siebel Server. The choices are: None and RSA. By default, this parameter is set to None.
      Compression	Specifies whether compression is used for data transmission from Oracle WebLogic Server and the Siebel Server. The choices are: None and zlib. By default, this parameter is set to None.
      Virtual Hosts	Lists the available virtual servers. Use this parameter when you have more than one Siebel Server. The following is a sample value that you might enter: VirtualServer1=1:localhost:3320,2:sdchs20i183:3320;VirtualServer2=1:xyz.corp.oracle.com:2321,2:ABC.corp.oracle.com:2321
      Logging Parameters
      Siebel Resource Adapter Log Directory	The directory where the Siebel Resource Adapter log files are stored. By default, this parameter is set to: C:\JDeveloper\mywork\SFE or default_JDeveloper_work_directory\SFE where the default log file name is ResourceName.log. The ResourceName.log file contains the run-time logging files during the execution of inbound Web service requests, inbound Enterprise Java Bean requests, and Siebel RESTful Services requests. Use this log file to troubleshoot any run-time issues. If you deploy Siebel Resource Adapter by using message-driven beans, then two more log files are stored in the preceding location: JCAReceiver.log JCASender.log NOTE:  If your deployment is on a remote computer, then make sure Oracle WebLogic Server can access this directory. TIP:   It is recommended that you also check the Oracle WebLogic Server Administration Console for additional, log file information.
      Log Level	The log level determines the amount of information that is written to the log file. The options are the same as the other log levels in SAI for Oracle Fusion Middleware: FATAL, ERROR, WARN, INFO, DETAIL, and DEBUG. By default, the log level is set to ERROR. For more information about log levels, see Setting Log Levels for SAI for Oracle Fusion Middleware.
      Outbound Resource Adapter Configuration
      Queue Connection Factory	The JNDI name for the connection factory queue created on the Oracle WebLogic Server Administration Console.
      Receive Queue	Specify the JNDI name for the configured queue on Oracle WebLogic Server. NOTE:  You use the ReceiveQueue and SendQueue parameters to pass the JNDI name to Oracle WebLogic Server. The JNDI name for ReceiveQueue is the same as SendQueue in the Siebel Server named subsystem.
      Send Queue	Specify the JNDI name for the configured queue on Oracle WebLogic Server. NOTE:  You use the SendQueue and ReceiveQueue parameters to pass the JNDI name to Oracle WebLogic Server. The JNDI name for SendQueue is the same as ReceiveQueue in the Siebel Server named subsystem.
      MDB Parameters
      Initial Free Pool Size	The initial number of beans in the free pool. By default, this value is set to 5.
      Maximum Free Pool Size	The maximum number of beans in the free pool. When an Enterprise Java Bean has been in the free pool for the number of seconds specified in Idle Timeout, and the total number of beans in the free pool approaches the maximum number of beans in the free pool specified in this field, then the idle beans are removed from the free pool. By default, this value is set to 10.
   3. Click Edit weblogic-ra.xml to verify the Java Naming and Directory Interface (JNDI) names, and then click OK.

      Some settings are described in the following table.

      Parameter	Description
      Resource Adapter JNDI Name	This parameter specifies the JNDI name for the resource adapter. The resource adapter bean is registered with this name in the JNDI tree. By default, this parameter is set to: eis/siebel/SiebelResourceAdapter
      Connection Factory JNDI Name	This parameter is the JNDI name for the connection factory that the resource adapter uses. Use this JNDI name for deploying Siebel RESTful Services. By default, this parameter is set to: eis/siebel/SiebelResourceAdapterConnFactory

   4. Choose one of the following security models, and then click Next.
      • DDOnly
      • CustomRolesAndPolicies

        NOTE:  By default, the model is set to DDOnly. If you want to use Oracle WebLogic Server security, then you must choose CustomRolesandPolicies, and also perform some additional configuration. For more information, see Setting Up Security for SAI for Oracle Fusion Middleware on Oracle WebLogic Server.

8. Enter the Oracle WebLogic Server parameters for your environment, and then click Next.

   Some of the parameters are described in the following table.

   Oracle WebLogic Server Parameter	Description
   Host Name	The name of the server where Oracle WebLogic Server is running. By default, this parameter is set to localhost.
   Port	The port number on which Oracle WebLogic Server is configured. By default, this parameter is set to 7001.
   SSL Port	The Secure Sockets Layer (SSL) port number on which Oracle WebLogic Server is configured. By default, this parameter is set to 7002. This setting is available only if you have chosen the Use SSL for this Deployment option.
   SSL Parameters	Click to specify the truststore parameters. This setting is available only if you have chosen the Use SSL for this Deployment option.
   Oracle WebLogic Administration Server	The name of the Oracle WebLogic Administration Server. By default, this parameter is set to AdminServer. TIP:   To find the name of your Oracle WebLogic Server, use the Oracle WebLogic Server Administration Console to select Environment, Deployments, and then Servers.
   Username	The administrator user name for Oracle WebLogic Server.
   Password	The administrator password for Oracle WebLogic Server.

9. Verify the summary and read the applicable notes, and then click Finish to deploy the resource adapter.

   Information about successful and failed resource adapter deployments appears.

10. Follow the procedure in Configuring Credential Mapping for SAI for Oracle Fusion Middleware on Oracle WebLogic Server.
11. Set the deployment order of the resource adapter to a value that is less than 100 by doing the following:
    1. Drill down on the resource adapter.
    2. In the Overview tab, find Deployment Order, enter a number less than 100, and then click Save.

       NOTE:  The deployment order is an integer value that indicates when this unit is deployed during startup, relative to other units on a server. The units with lower values are deployed before those with higher values. If the value is the same for two units, then the alphabetical order sorted by the deployment name is applied. Changes take effect after you redeploy the module or restart the server.

       CAUTION:  The order of deployment matters because if an inbound Web service or Siebel RESTful service becomes active without an active resource adapter, then the deployment fails.