13 JCA Bindings

This chapter describes how to create, locate, edit, and delete JCA Binding resources using the Oracle Service Bus Administration Console.

Oracle SOA Suite lets you integrate with back-end Enterprise Information Systems (EIS) using J2EE Connector Architecture (JCA) adapters. Using Oracle JDeveloper and other supported JCA development environments, you configure the adapters and create the JCA adapter resources (.jca files and abstract WSDLs) used for the back-end integration.

You can communicate with JCA-compliant EIS components through Oracle Service Bus (OSB), which lets you consume the JCA resources in the form of JCA Binding resources. With JCA Bindings, you can generate proxy and business services that use the Oracle Service Bus JCA transport to communicate with the EIS applications through the JCA adapters.

This chapter contains the following topics:

For more information on the JCA transport, see "JCA Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.

For more information on the Oracle SOA Suite JCA adapters, see the Oracle Fusion Middleware User's Guide for Technology Adapters.

13.1 Locating JCA Bindings

The Summary of JCA Bindings page lists the JCA Bindings that you have added to the Oracle Service Bus domain.

  1. Do either of the following:

    • Select Project Explorer to display the Projects View page or the Project/Folder View page. Then navigate through projects and folders to find the JCA Binding.

    • Select Resource Browser > JCA Bindings. The Summary of JCA Bindings page displays the information shown in Table 13-1. For a more detailed description of the properties, see Section 13.1, "Locating JCA Bindings."

  2. To locate a specific JCA Binding:

    • To restrict the number of items in the list, you can filter by name and path before you click Search.

      Path is the project name and the name of the folder(s) in which the resource resides.

    • Click View All to remove the search filters and display all JCA Bindings.

Table 13-1 JCA Binding Information

Property Description

JCA Binding Name

The unique name assigned to the JCA Binding. Click the name to see the View JCA Binding Details page. See Section 13.3, "Editing JCA Bindings."

Path

The project name and the name of the folder in which the JCA Binding resides. Click the name to see the project or folder that contains this resource. See Section 4.1.1, "Qualifying Resource Names Using Projects and Folders."

Action

Contains a Generate icon that lets you generate an Oracle Service Bus WSDL and JCA service from the JCA Binding.

Options

Contains a Delete icon. If a business service or proxy service has been configured to use a JCA Binding, a Deletion Warning icon indicates that you can delete the JCA Binding with a warning confirmation. This might result in conflicts due to unresolved references from the service to the deleted JCA Binding. See Section 13.4, "Deleting JCA Bindings."


13.2 Adding JCA Bindings

The easiest way to create JCA Bindings in Oracle Service Bus is by bulk importing the JCA resources you have created (.jca file, associated WSDL, and TopLink or EclipseLink mapping file). On bulk import, Oracle Service Bus automatically generates a JCA Binding out of .jca files, WSDL resources out of the associated JCA WSDLs, and XML Document resources out of mapping files, and maintains the dependencies among the files.

For more information on importing, see Section 4.15, "Loading Resources from a Zip File.", Section 4.17, "Loading Resources from a URL" and Section 29.1, "Importing Resources."

Once you import your JCA resources, you can generate proxy or business services out of them, as described in Section 20.1.1, "Generating a Proxy Service from a JCA Binding Resource" and Section 19.1.1, "Generating a Business Service from a JCA Binding Resource."

If you do not bulk import your JCA resources, you can manually create JCA Bindings, described in the following steps:

  1. In Oracle JDeveloper create a JCA service WSDL, a corresponding JCA (.jca) file, and, if necessary, other resources such as TopLink or EclipseLink mapping files and XSLT files.

    For more information, see the Oracle Fusion Middleware User's Guide for Technology Adapters.

  2. If you have not already done so, click Create to create a new session in the OSB Administration Console, or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."

  3. In the OSB Administration Console, create or import the JCA resources you created in Oracle JDeveloper, such as the WSDL, XML, and XSLT resources.

  4. Create the JCA Binding.

    1. Select Project Explorer, then select the project or folder location for the JCA Binding. The Project/Folder View page is displayed.

    2. From the Create Resource field, select JCA Binding to display the Create a New JCA Binding Resource page.

    3. In the JCA File field, click Browse to select the JCA file.

      The Resource Name field is automatically populated with the file name (minus the file extension).

      Instead of selecting a file, you can copy and past the contents of a JCA file in the JCA File field text area.

    4. In the Resource Name field, enter or change the name of the JCA Binding. JCA Binding names must be unique.

      Follow the Section 2.3, "Resource Naming Restrictions" for naming guidance.

    5. In the Resource Description field, enter a description of this JCA Binding.

    6. Click Save. The JCA Binding is saved in the current session.

      A validation warning is displayed in the If the JCA Binding does not yet reference required resources, such as a WSDL and a mapping file.

  5. Click the name of the new JCA Binding to display it in the View a JCA Binding page.

  6. Click Edit References.

  7. On the Edit the Reference of a JCA Binding Resource page, Browse to select the JCA Binding's reference resources, such as the WSDL, a TopLink/EclipseLink mapping file, and an XSLT file.

  8. Click Save.

  9. To end the session and deploy the configuration to the runtime, click Activate under Change Center.

After you add JCA Binding resources and configure the resource dependencies (associating a WSDL)—or if you have imported JCA resources that maintain their dependencies—you can generate proxy and business services from JCA Bindings. For more information, see Section 20.1.1, "Generating a Proxy Service from a JCA Binding Resource" and Section 19.1.1, "Generating a Business Service from a JCA Binding Resource."

13.3 Editing JCA Bindings

Use the View JCA Binding Details page to view and change details of a JCA Binding.

  1. If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."

  2. Locate the JCA Binding, as described in Section 13.1, "Locating JCA Bindings."

  3. Click the JCA Binding name. The View a JCA Binding page displays the information shown in Table 13-2.

    Table 13-2 JCA Binding Details

    Property Description

    Last Modified By

    The user who created this JCA Binding or imported it into the configuration.

    Last Modified On

    The date and time that the user created this JCA Binding or imported it into the configuration. Click the date and time link to view the change history of this resource. See Section 4.23, "View Change History Page."]

    References

    Provides a link to the WSDL resource that the JCA Binding references. See Section 4.22, "Viewing References to Resources."

    Referenced by

    The number of objects that reference this JCA Binding. If such references exist, click the numeric link to view a list of the objects. See Section 4.22, "Viewing References to Resources."

    Action icon

    With the Change Center in edit mode, Action lets you generate an Oracle Service Bus WSDL and JCA service from the JCA Binding.

    JCA File

    Displays a read-only view of the JCA Binding.

    Abstract WSDL

    Displays the JCA Binding's associated WSDL. If the JCA Binding does not reference a WSDL, click Edit References to reference the associated WSDL.

    TopLink XML

    Displays the JCA Binding's required TopLink or EclipseLink mapping file. If the JCA Binding resource does not reference the required mapping file, click Edit References to select the required mapping file. This field appears only if the JCA file declares an XML resource.

    XSLT

    Displays the JCA Binding's required XSLT file. If the JCA Binding resource does not reference a required XSLT resource, click Edit References to select the required XSLT file. This field appears only if the JCA file declares an XSLT resource, such as for a socket adapter.


  4. To modify the Description or JCA File, click Edit.

    You cannot change the Resource Name.

  5. Click Save to commit the updates in the current session.

  6. To change the references to the JCA Binding's required resources, or to fix unresolved references, click Edit References and select the appropriate resources.

  7. To end the session and deploy the configuration to the runtime, click Activate under Change Center.

13.4 Deleting JCA Bindings

If any business service or proxy service is based on the JCA Binding, remove the JCA Binding from the business service or proxy service before deleting the JCA Binding.

  1. If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."

  2. Select Resource Browser > JCA Bindings.

  3. Click the Delete icon in the Options field of the JCA Binding you want to delete.

    The JCA Binding is deleted in the current session. If a business service or proxy service has been configured to use a JCA Binding, a Deletion Warning icon indicates that you can delete the JCA Binding with a warning confirmation. This might result in conflicts due to unresolved references from the service to the deleted JCA Binding.

  4. To end the session and deploy the configuration to the runtime, click Activate under Change Center.