Bookshelf Home | Contents | Index | PDF     

Siebel Application Integration for Oracle Fusion Middleware Guide > Working with Web Services Using SAI for Oracle Fusion Middleware > Process of Deploying Inbound Web Services Using SAI for Oracle Fusion Middleware >

Deploying Enterprise Java Beans Using SAI for Oracle Fusion Middleware

This topic describes how to deploy Enterprise Java Beans using SAI for Oracle Fusion Middleware.

This task is a step in Process of Deploying Inbound Web Services Using SAI for Oracle Fusion Middleware.

To deploy an Enterprise Java Bean using SAI for Oracle Fusion Middleware

  1. Start Oracle JDeveloper.
  2. From the application-level menu, select File, and then click the New menu item.
  3. 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.
  4. In the Welcome to the Deployment Wizard screen, click Next.
  5. Select the Siebel Inbound Services deployment type, and then click Next.
  6. Select EJB Deployment, and then click Next.

    NOTE:  You can select Inbound Web Service or EJB Deployment or both.

  7. Select one or more Siebel inbound services that you want to deploy by moving the services from the Available section to the Selected section, and then click Next.

    NOTE:  The path for the generated code is the XSD File Path you specified in the General tab in the SAI for Oracle Fusion Middleware Preferences.

  8. Enter the inbound deployment parameters for the Enterprise Java Bean.

    Some parameters are described in the following table.

    Inbound Deployment Parameters
    Description

    Version

    This field controls the version of the inbound Web service that is being deployed on Oracle WebLogic Server. For example, if you deployed a Siebel account with version 1.0.0.0, and you want to deploy another Siebel account, then use this field to increment the version (such as 1.0.0.1) to make sure there is no conflict.

    NOTE:  Typically, the Oracle WebLogic Server Administration Console shows older versions as retired.

    Siebel Resource Adapter Name

    Specifies the name for the resource adapter. You can change this value to point to a different resource adapter. By default, the name of the resource adapter that was last deployed appears.

    Siebel Resource Adapter JNDI Name

    Specifies the JNDI name for the connection factory the resource adapter uses. You can change this value to point to a different resource adapter. By default, the name of the resource adapter that was last deployed appears.

  9. Enter the Enterprise Java Bean parameters by doing the following:
    1. Click Edit, and then click the plus sign (+) to enter the parameters.

      The parameters are described in the following table.

      EJB Parameter
      Description

      Business Service Name

      The Siebel business services and Siebel workflow processes that have been selected for deployment.

      TIP:   To select a business service, click in the Business Service Name field, and then choose from the drop-down list.

      JNDI Name

      Enter the Java Naming and Directory Interface name for the Java Enterprise Bean. By default, this parameter is not specified.

      Transaction Timeout

      The transaction timeout value, in seconds. By default, this parameter is set to 600.

      Initial Pool Size

      The initial number of beans in the free pool. By default, this parameter is set to 5.

      Maximum 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 parameter is set to 20.

    2. Click Save (or Cancel) to exit the EJB Parameters dialog box, and then click Next again.

      NOTE:  Click X if you want to remove your selection without existing the EJB Parameters dialog box.

  10. Enter the Oracle WebLogic Server parameters for the service you are deploying, and then click Next.

    For a description of the parameters, see Siebel Application Integration for Oracle Fusion Middleware: Oracle JDeveloper Online Help.

  11. Review the summary information, and then click Finish to deploy.

    NOTE:  If there is an existing archive folder structure with the same name, then a warning appears asking if you want to overwrite it. If you click Yes, then the existing folder structure is overwritten. If you click No, then a dialog box appears in which you can name a new folder structure and save that structure in a directory of your choice.

    Information about successful and failed deployments appears. Click OK to exit.

    NOTE:  If the deployment fails, then check the SiebelDeployExtension.log file. By default, this file is found in C:\JDeveloper\mywork\SFE.

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