1.21 Create Direct Binding Dialog

Use with the Direct Binding API to invoke a SOA composite application and exchange messages over a remote method invocation (RMI). This option supports the propagation of both identities and transactions across JVMs and uses the T3 optimized path. Both synchronous and asynchronous invocation patterns are supported.

Element Description

Name

Enter a name or accept the default name of Servicenumber. This becomes the name for this service in the SOA Composite Editor.

Type

Select the direction in which you want the direct binding to operate.

  • Service: Creates an inbound direct binding in the Exposed Services (left) swimlane that provides the Direct Binding API with an entry point to the SOA composite application. This direction is selected by default if you dropped the direct binding service into the Exposed Services swimlane. More

  • Reference: Creates an outbound direct binding in the External References (right) swimlane that provides the Direct Binding API with an output point from the SOA composite application.

Reference Target

Select the reference target where you want the direct binding to operate:

  • Oracle SOA Composite: Creates a direct binding with Oracle SOA Composite as a reference target.

  • Oracle Service Bus: Creates a direct binding with Oracle Service Bus as a reference target.

WSDL URL

Select the Web Services Description Language (WSDL) file to use with this web service. This file describes the capabilities of the service that provides an entry point into a SOA composite application. A service is defined by a port type and optionally a callback port type. The WSDL file can define more capabilities (port types) of the target web service, but a service only uses the one defined by the port type. The WSDL can be abstract or concrete.

Note: Do not manually update the WSDL location in your file in Source View. This action is not supported. Only updates made in Design View are supported.

Find existing WSDLs icon

Click to select an existing WSDL file.

Generate WSDL from schemas icon

Click to create a WSDL file from a schema. This field is displayed if Service is selected from the Type menu.

Port Type

Select the port type or use the automatically specified value.

Callback Port Type

Select the callback port type for asynchronous processes.

Reference Binding Details

The following reference binding details get populated automatically.

  • Address: The Address field is automatically populated when the WSDL is concrete and it has at least one binding that is direct.

  • Provider URL: The Provider URL field is automatically populated when the WSDL is concrete and it has at least one binding that is direct.

Use local JNDI Provider

Select to use the local JNDI provider.

copy wsdl and its dependent artifacts into the project

Select this checkbox to copy a remote WSDL and its dependent artifacts into the project.

Note: Oracle recommends that you select this checkbox only for situations such as offline designing. This is because maintaining a copy of a remote WSDL may result in synchronization issues if the remote WSDL is updated.

Related Topics

What Happens When You Create a SOA Application and Project in Developing SOA Applications with Oracle SOA Suite

Using Direct Binding to Invoke Composite Services in Developing SOA Applications with Oracle SOA Suite