Siebel Application Integration for Oracle Fusion Middleware Guide > Working with Web Services Using SAI for Oracle Fusion Middleware >

Configuring JMS Resource Adapters for Outbound Web Services Using SAI for Oracle Fusion Middleware

This topic describes how to configure JMS resource adapters for outbound Web services using SAI for Oracle Fusion Middleware.

This task is a step in Roadmap for Deploying Outbound Web Services Using SAI for Oracle Fusion Middleware.

TIP:   The following procedure is similar to the resource adapter configuration described in Configuring Siebel Server Load Balancing and SSL for SAI for Oracle Fusion Middleware, except that you define outbound configurations for the adapter rather than inbound.

To configure a JMS resource adapter for outbound Web services using SAI for Oracle Fusion Middleware

1. Make sure the Oracle WebLogic Server is up and running.
2. Start Oracle JDeveloper, if 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 a resource adapter name, if you do not want to accept the default. By default, the resource adapter name is SiebelResourceAdapter.

      NOTE:  Each resource adapter has its own log file. The log file name is the same name as the resource adapter name appended with .log (that is, JNDI_ra_name.log). The location of the log file depends on the value you specify in the Deployment Log Directory logging parameter (see description in the following Step b).

   2. Click Edit ra.xml, click the Outbound RA Configuration tab, select the Enable JMS Configuration option, and then click Next.

      Some parameters are described in the following table.

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

      For descriptions of the other XML parameters, see Step 7 in Process of Deploying Siebel Resource Adapters Using SAI for Oracle Fusion Middleware.

8. Follow the prompts until you complete the resource adapter deployment.

   For more information about deploying resource adapters, see Configuring Siebel Server Load Balancing and SSL for SAI for Oracle Fusion Middleware.

9. Click Finish.

   Two new entries are created for Oracle WebLogic Server.