Skip Headers

Oracle Fusion Middleware Oracle E-Business Suite Adapter User's Guide
Release 14c (14.1.2.0.0)
Part Number F92121-01
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Runtime Configuration for Oracle E-Business Suite Adapter

Overview

Oracle E-Business Suite Adapter is deployed as JCA 1.5 resource adapter within the Oracle WebLogic Server container.

Although Oracle E-Business Suite Adapter is physically deployed as JCA 1.5 resource adapter, the logical deployment of the Adapter involves creating the connection entries for the JCA 1.5 resource adapter. This connection information is for tying up the database connection information provided when you create a partner link or service and is used by iAS at run time in the background.

For the logical deployment changes to take effect, the Oracle WebLogic Server container process must be restarted.

The following topics are included in this section:

Configuring the Data Source in Oracle WebLogic Server

Oracle WebLogic Server consists of a JCA container for hosting JCA resource adapters. JCA defines standard Java interfaces for simplifying the integration of a J2EE server with various back-end applications. All client applications run within the Oracle WebLogic Server environment.

The JCA resource adapter is a WebLogic Server component contained in a Resource Adapter Archive (RAR) file within the applications/directory. An RAR file contains a correctly formatted deployment descriptor. In addition, it contains declarative information about the contract between the Oracle WebLogic Server and resource adapter.

The weblogic-ra.xml file is the deployment descriptor for a WebLogic resource adapter. It contains deployment configurations for deploying resource adapters to Oracle WebLogic Server, which includes the back-end application connection information as specified in the deployment descriptor of the resource adapter, Java Naming and Directory Interface (JNDI) name to be used, connection pooling parameters, security identities, Work Manager properties, logging, and resource principal mapping mechanism and configurations.

Note: A WebLogic resource adapter also uses ra.xml descriptor that describes the resource adapter-related attributes type and its deployment properties using the standard XML schema specified by the JCA 1.5 Specification.

After successfully installing Oracle WebLogic Server, use the following steps to configure the data sources in the Oracle WebLogic Remote Console:

Note: For information on how to install Oracle WebLogic Server and create connection factory, see Oracle Fusion Middleware Installing and Configuring Oracle WebLogic Server and Coherence for details.

  1. Navigate to http://servername:portnumber/rconsole.

  2. In the WebLogic Remote Console, set up the connection to a WebLogic administration server by selecting Add Admin Server Connection Provider or clicking More from the Providers drawer and then selecting Add Admin Server Connection Provider from the options.

    Enter appropriate values and connection settings to make sure that the WebLogic Remote Console is connected to your desired WebLogic administration server.

    The Home page of the Oracle WebLogic Remote Console appears.

    Oracle WebLogic Remote Console Home Page

    the picture is described in the document text

  3. In the Edit Tree, go to Services and then Data Sources.

    The Summary of JDBC Data Sources page is displayed.

    The Summary of JDBC Data Sources Page

    the picture is described in the document text

  4. Click New. The Create a new JDBC System Resource page is displayed.

  5. Enter the values for the properties to be used to identify your new JDBC data source.

    Create a new JDBC System Resource Page

    the picture is described in the document text

    If you want to verify the connection to the database, enable the Test Configuration option to test the database availability and the connection properties you provided.

  6. Click Create.

  7. The Summary of JDBC Data Sources page is displayed. This page summarizes the JDBC data source objects that have been created in this domain. The Data Source that you created appears in this list.

Creating Connection Factory for Oracle E-Business Suite Adapter

The deployment descriptor of the Oracle E-Business Suite Adapter must associate with the Java Naming and Directory Interface (JNDI) name with configuration properties required by the adapter to access the database.

Use the following steps to configure the JNDI and additional settings for Oracle E-Business Suite Adapter through the Oracle WebLogic Remote Console:

  1. Navigate to http://servername:portnumber/rconsole.

  2. In the WebLogic Remote Console, connect to a WebLogic administration server if it is not yet established.

    To do so, click More from the Providers drawer and then select Add Admin Server Connection Provider from the options. Enter appropriate values and connection settings to make sure that the WebLogic Remote Console is connected to your desired WebLogic administration server. The Home page of the Oracle WebLogic Remote Console appears.

  3. In the Edit Tree, go to Deployments, then App Deployments.

  4. Locate an appropriate link for Oracle E-Business Suite Adapter (for example, OracleAppsAdapter) from the summary of deployment table first and then click the link.

    Edit Tree - App Deployments

    the picture is described in the document text

    This displays the deployment information for the selected resource adapter, Oracle E-Business Suite Adapter.

  5. Ensure that Oracle E-Business Suite Adapter is deployed with "Active" state.

    1. In the Monitoring Tree, go to Deployments, then Application Management.

    2. Select OracleAppsAdapter. Notice that the "Active" is shown as the Intended State field for Oracle E-Business Suite Adapter.

      Monitoring Tree - Application Management

      the picture is described in the document text

    3. If Oracle E-Business Suite Adapter is not deployed with "Active" state, select OracleAppsAdapter, then click Start. and then select either the Servicing all requests or Servicing only administration request option.

  6. Set the deployment properties using the following steps:

    1. In the Monitoring Tree, go to Deployments, then Application Management.

    2. Select OracleAppsAdapter.

    3. Click Create Plan.

    4. In the Plan Path field, enter a file path for the new deployment plan, such as /home/user/fmwhome14/soa/soa/connectors/Plan.xml.

    5. Click Done.

  7. In the Monitoring Tree, go to Deployments, then Application Management, then OracleAppsAdapter, then Configuration. This displays the page with overview information about the OracleAppsAdapter or Oracle E-Business Suite Adapter.

    Monitoring Tree - OracleAppsAdapter

    the picture is described in the document text

  8. From the Navigation Tree structure or the Breadcrumb menu, click the Deployment and select Outbound Connection Pool Groups - Configuration to display the Outbound Connection Pool Groups page containing instances for this selected resource adapter, Oracle E-Business Suite Adapter.

    Breadcrumb Menu to Select Outbound Connection Pool Groups - Configuration

    the picture is described in the document text

    Click javax.resource.cci.ConnectionFactory to expand this group and obtain configuration information for a Connection Pool instance.

    Outbound Connection Pool Group "javax.resource.cci.ConnectionFactory"

    the picture is described in the document text

  9. From the Navigation Tree structure or the Breadcrumb menu, click javax.resource.cci.ConnectionFactory and select Outbound Connection Pool Instances - javax.resrouce.cci.ConnectionFactory to expand this group and obtain configuration information for a Connection Pool instance.

    Outbound Connection Pool Instances

    the picture is described in the document text

  10. Click New to create a new instance in this outbound connection pool. For example, enter eis/Apps/Ebiz as the instance name.

    New Page

    the picture is described in the document text

    Click Done.

    The Outbound Connection instance represents a connection pool. The JNDI name can be used to obtain the pool at run time.

  11. From the Navigation Tree structure or the Breadcrumb menu, click the newly-created instance eis/Apps/Ebiz and select Properties - eis/Apps/Ebiz.

    Breadcrumb Menu to Select Properties - eis/Apps/Ebiz

    the picture is described in the document text

    Click "XADataSourceName" and then add the value of datasource JNDI name, such as jdbc/Ebiz against "XADataSourceName".

    Breadcrumb Menu to Select Properties - eis/Apps/Ebiz

    the picture is described in the document text

    Click Save.

  12. You may find some unexpected exception messages populated while processing the request. Use the following steps to resolve the issue:

    1. Click the Adapter link that you selected earlier on the breadcrumb navigation path.

    2. Click the Deployment and the Outbound Connection Pool Groups to display the Outbound Connection Pool groups and instances.

      Click the javax.resource.cci.ConnectionFactory expand node to display the newly-configured JNDI (such as eis/Apps/Ebiz) for the outbound instance.

    3. Click the outbound instance name (such as eis/Apps/Ebiz) to display the outbound connection properties.

    4. Select the 'XADataSourceName' property name to enable the input text box.

      Enter jdbc/AppsDataSource in the Value box, and then click Save to update the deployment plan.

Creating the Application Server Connection

You must establish a connectivity between the design-time environment and the server you want to deploy it to. In order to establish such a connectivity, you must create the application server connection.

Use the following steps to create the application server connection:

  1. From Oracle JDeveloper, select Window > Application Servers to open the Application Servers tab.

  2. Right-click on the Application Servers node and select New Application Server to open the Create Application Server Connection wizard.

  3. In the Usage page, leave the default Standard Server selection unchanged.

    Usage Page

    the picture is described in the document text

    Click Next.

  4. Enter an appropriate name in the Connection Name field. Select WebLogic 12.x as the connection type.

    Name and Type Page

    the picture is described in the document text

    Click Next.

  5. Enter the username (such as weblogic) and password specified during installation and click Next.

    Authentication Page

    the picture is described in the document text

  6. Enter the WebLogic Server connection host name. Enter "soa" in the WebLogic Domain field.

    Configuration Page

    the picture is described in the document text

    Click Next.

  7. Click Test Connection to validate your server configuration. You should find success messages populated in the Status window.

    Test Page

    the picture is described in the document text

    Click Next and Finish to complete the application server connection.