Designing an Integration with the Adapter Configuration Wizard

You use the Adapter Configuration Wizard to include the Oracle Sales Cloud adapter in a SOA composite application or an Oracle Service Bus business service.

The Adapter Configuration Wizard consists of configuration pages that enable you to select the artifacts required to communicate with the Oracle Sales Cloud application. You can configure the adapter in the inbound (source) direction or the outbound (target) direction.
  • Inbound (source) direction:

    • The Basic Info page prompts you to enter a meaningful name and optional description.

    • The Connection page prompts you to specify the WSDL, security policy (username password token), and CSF authentication key to use. The authentication key is created by clicking the Add icon to specify the key name, user name, and password.

      You can also test the connection to the Oracle Sales Cloud application on the Connection page. This enables you to confirm that the URL to the service catalog service and credentials are correct. Status is displayed that indicates whether the connection is successful and whether the credentials are authenticated by the Oracle Sales Cloud application. Any errors that occurred during the attempt to connect are also displayed.

    • The Request page prompts you to select the business object or event subscription to receive as a request from the Oracle Sales Cloud application.

      Note:

      • When you select a business object in the inbound direction, a description is displayed below the table, but life cycle information about the selected object (for example, active or deprecated) is not displayed. In the outbound direction, life cycle information for the business object is displayed.

      To get all available data objects in the Oracle Sales Cloud instance, the adapter first reads the schema document (.XSD) that is referenced in the service’s WSDL. The adapter then parses this XSD to obtain the list of all schema imports and shows them as data objects.

      For example, the adapter displays the opportunity business object and its useful metadata first by reading the opportunity service’s WSDL and the referenced schema OpportunityService.xsd file. The XSD in turns imports another schema Opportunity.xsd in which the opportunity business object is defined. The metadata for the opportunity business object is defined in this schema.

      A search facility is provided that enables you to filter the display of business objects for quick selection. When you enter a search string, the list renders only the matching business objects in the list browser instead of showing all objects.

    • The Summary page displays your selections from the previous pages.

  • Outbound (source) direction:

    • The Basic Info page prompts you to enter a meaningful name and optional description. This is the same page that is displayed in the inbound direction.

    • The Connection page prompts you to specify the WSDL, security policy (none, basic authentication, or username password token), and CSF authentication key to use. This is the same page that is displayed in the inbound direction.

      The Operations page prompts you to select a business object or service and the operation to perform on your selection.

      A search facility based on service names is also provided. To quickly select a business service, you type a search string. The list renders only matching business services in the list browser instead of showing all services.

    • The Summary page displays your selections from the previous pages.
The following artifacts are created for each adapter instance and displayed in the Applications window in Oracle JDeveloper:
  • WSDL file: Provides a simplified user experience in terms of creating data mappings, while integrating with the Oracle Sales Cloud application services. For example, an abstract WSDL defines strongly-typed types, the name of the operation and business object selected, and the request and response structures.

  • JCA file: Contains the internal implementation details used by the adapter during runtime. It contains the different interaction and connection properties used by the adapter.

When application configuration is complete, you can deploy the application from Oracle JDeveloper to the runtime environment.

Note:

The wizard does not support the creation of response message callbacks. As an alternative, you can design your BPEL process to include activities that support callbacks.

For information about the details to specify in the fields of the wizard pages, see Configuring Oracle Sales Cloud Properties.