This service enables you to integrate applications with a standards-based web service using the Simple Object Access Protocol (SOAP) over HTTP. Web services are described in the WSDL file.

Dragging a web service into a swimlane of the SOA Composite Editor invokes the Create Web Service dialog for specifying configuration properties.

For more information about web services, see How to Define the Interface (WSDL) for a Web Service.

For information about adding Message Transmission Optimization Mechanism (MTOM) attachments to web services, see Sending and Receiving MTOM-Optimized Messages to SOA Composite Applications.

The HTTP binding service enables you to integrate SOA composite applications with HTTP binding.

You drag the HTTP service from the Components window into a swimlane of the SOA Composite Editor to invoke the HTTP Binding Wizard. This addition enables you to configure HTTP binding as follows:

• As a service binding component in the Exposed Services swimlane to invoke SOA composite applications through HTTP POST and GET operations

• As a reference binding component in the External References swimlane to invoke HTTP endpoints through HTTP POST and GET operations

JCA adapters enable you to integrate services and references with the following technologies:

• Databases

• File systems

• FTP servers

• Message systems such as Advanced Queueing (AQ) and Java Messaging Systems (JMS)

• IBM WebSphere MQ

• TCP/IP sockets

• Third-party adapters (SAP, JDE World, and others)

• Oracle User Messaging Service

• Lightweight Directory Access Protocol (LDAP) server

• Coherence cache

Dragging a JCA adapter into a swimlane of the SOA Composite Editor invokes the Adapter Configuration Wizard for specifying configuration properties.

The Oracle applications adapter provides connectivity to Oracle Applications. The adapter supports all modules of Oracle Applications in Release 12 and Release 11i, including selecting custom integration interface types based on the version of Oracle E-Business Suite.

The Oracle BAM 11g adapter enables you to integrate Java EE applications with an Oracle BAM 11g server to send data. This adapter can only connect to an Oracle BAM 11g server.

Dragging a BAM 11g icon into a swimlane of the SOA Composite Editor invokes the Adapter Configuration Wizard for specifying configuration properties.

The Oracle B2B service enables you to browse B2B metadata in the MDS repository and select document definitions.

Oracle B2B is an e-commerce gateway that provides for the secure and reliable exchange of transactions between an organization and its external trading partners. Oracle B2B and Oracle SOA Suite are designed for e-commerce business processes that require process orchestration, error mitigation, and data translation and transformation within an infrastructure that addresses the issues of security, compliance, visibility, and management.

Dragging a B2B icon into a swimlane of the SOA Composite Editor invokes the B2B Configuration Wizard for specifying configuration properties.

The Oracle Healthcare adapter enables you to create an end-to-end health care integration process in a SOA composite application. The Healthcare adapter establishes the connection between a SOA composite application and the external health care applications with which data is shared or with an internal topic or queue, where data can be made available internally or to other systems. You can use other Oracle SOA Suite components in your composite application, including BPEL processes, Oracle Mediator components, a variety of adapters, and so on.

The Healthcare Configuration Wizard in Oracle JDeveloper lets you add health care integration binding components to a SOA composite application as follows:

• The component is used as a service (inbound) to receive messages from external systems and deliver them to SOA composite applications. Oracle SOA Suite for health care integration is the entry point to the SOA composite application.

• The component is used as a reference (outbound) to send messages from the SOA composite application to external applications.

As you follow the steps in the Healthcare Configuration Wizard, you are prompted to select a document definition created in Oracle SOA Suite for health care integration.

You can launch Oracle SOA Suite for health care integration from the wizard to create a document definition if the right one does not already exist. This is the payload, or message, that you are receiving from or sending to external systems.

Oracle MFT enables you to transfer files to and from many endpoint types, such as the following:

• Embedded FTP or sFTP server

• Remote FTP or sFTP server

• Directories

• SOAP web service endpoints

• Oracle SOA Suite SOAP web service endpoints

• Oracle Service Bus web service endpoints

• Oracle B2B partners and Oracle Healthcare endpoints

• Oracle Data Integrator web service endpoints

The ADF-BC service enables you to integrate Oracle Application Development Framework (ADF) applications using service data objects (SDOs) with SOA composite applications.

Dragging an ADF-BC icon into a swimlane of the SOA Composite Editor invokes the Create ADF-BC Service dialog for specifying configuration properties.

For more information about Oracle ADF, see the following:

• Delegating XML Data Operations to Data Provider Services

• Using Standalone SDO-based Variables

• Developing Fusion Web Applications with Oracle Application Development Framework

• Developing Web User Interfaces with Oracle ADF Faces

The EJB adapter enables Enterprise JavaBeans and SOA composite applications to interact by passing Java interfaces (does not use a WSDL file to define the interface) or SDO parameters (uses a WSDL file to define the interface).

SDOs enable you to modify business data regardless of how it is physically accessed. Knowledge is not required about how to access a particular back-end data source to use SDO in a SOA composite application. Consequently, you can use static or dynamic programming styles and obtain connected and disconnected access.

Enterprise JavaBeans are server-side domain objects that fit into a standard component-based architecture for building enterprise applications with Java. These objects become distributed, transactional, and secure components.

Java interfaces eliminate the need for WSDL file definitions. This type of integration provides support with the following objects:

• Native Java objects

• Java Architecture for XML Binding (JAXB)

Dragging an EJB icon into a swimlane of the SOA Composite Editor invokes the Create EJB Service dialog for specifying configuration properties.

For more information, see Integrating Enterprise JavaBeans with Composite Applications.

The direct binding adapter uses the Direct Binding Invocation API to invoke a SOA composite application in the inbound direction 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.

You can also invoke an Oracle Service Bus flow or another SOA composite application in the outbound direction.

Dragging a Direct icon into a swimlane of the SOA Composite Editor invokes the Create Direct Binding dialog for specifying configuration properties.

For more information about direct binding, see Using Direct Binding to Invoke Composite Services.

For information about the Direct Binding Invocation API, see Java API Reference for Oracle SOA Suite Infrastructure Management.

For more information about Oracle Service Bus, see Developing Services with Oracle Service Bus.

REST is an architecture for designing network applications. RESTful applications use HTTP requests to post data (create and update), get data (for example, make queries), and delete data. REST provides an alternative to using web services. A SOA composite can be REST-enabled or invoke an existing REST service through the REST adapter.

For more information, see Integrating REST Operations in SOA Composite Applications.

The cloud adapters enable you to send and receive messages from a cloud server. See the following guides for more information:

• Using Ariba Adapter

• Using Oracle Eloqua Cloud Adapter

• Using Oracle ERP Cloud Adapter

• Using the NetSuite Adapter

• Using Oracle RightNow Cloud Adapter

• Using Oracle Sales Cloud Adapter

• Using Salesforce Adapter

• Using ServiceNow Adapter

• Using SuccessFactors Adapter

1. From the Technology section of the Components window, drag a binding component to the appropriate swimlane. The swimlane in which to drag the component is based on the action you want to perform. Not all adapters can be dropped in both swimlanes. If an adapter is only available for references, then you cannot drop it into the services swimlane.

   • If you want to provide the outside world with an entry point to the SOA composite application, drag the binding component to the Exposed Services swimlane.

   • If you want to enable messages to be sent from the SOA composite application to external services in the outside world, drag the binding component to the External References swimlane.

   Figure 35-6 shows a SOAP web service being dragged into the composite. This action invokes a dialog for specifying various configuration properties.

Figure 35-6 Integration of a Web Service Binding Component into a Composite

Description of "Figure 35-6 Integration of a Web Service Binding Component into a Composite"

For more information about adding binding components, see Adding Service Binding Components and Adding Reference Binding Components.

1. In Oracle JDeveloper, access the SOA composite application in which to create tokens.
2. Above the SOA Composite Editor, click the Binding URL Tokenizer icon. Figure 35-7 provides details.

   Figure 35-7 Binding URL Tokenizer Icon

   
   Description of "Figure 35-7 Binding URL Tokenizer Icon"

   The Binding URLs dialog appears, as shown in Figure 35-8.

   • Binding URLs of each external reference that has a binding.ws element with a location attribute in the composite.xml file that starts with the following entries are automatically displayed:

     • http

     • https

     • ${ (for a URL that uses tokens in place of the hardcoded HTTP protocol, host, or port values)

     • callbackServerURL

   • Binding URLs for REST references with the location attribute of the binding.rest element are automatically displayed.

   Figure 35-8 Binding URLs Dialog

   
   Description of "Figure 35-8 Binding URLs Dialog"

   The Service2 reference in Figure 35-8 also includes an override of the callback location using a reference property such as callbackServerURL:

   <property name="callbackServerURL" type="xs:string" many="false">
   ${protocol}://${myhost1}:${myport1}/soa-infra/services/default/service/
   bpelprocess1_client_ep</property>
   

   The callbackServerURL property can be tokenized as shown in Figure 35-8.

3. Double-click a row or select the row and click the Edit icon to create tokens for the HTTP protocol, host, and port values in the binding URLs of external references.

   The Binding URL Tokenization dialog appears, as shown in Figure 35-9.

   Figure 35-9 Binding URL Tokenization Dialog

   
   Description of "Figure 35-9 Binding URL Tokenization Dialog"
4. Provide values appropriate to your environment, as described in Table 35-4, and click OK.

   Table 35-4 Binding URL Tokenization Dialog

   Field	Description
   Token File	Perform either of the following options: Click the Browse button to access a dialog for selecting the token file that includes the token names and values. The file can be on the local file system. The names and values specified in this file replace the hardcoded names and values for protocol, host, and port in the binding.ws element. This field is automatically populated with your file selection on subsequent invocations of this dialog. If you specify a token file from the file system, it must be an XML file that follows this format: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> <properties> <comment> URL Resolver file used by the Metadata manager to resolve $<variable> in URLs </comment> <entry key="protocol">oramds</entry> <entry key="host">MyHost</entry> <entry key="port">80</entry> </properties> Skip this field entirely if you want to manually enter new token names and values in the Token and Current Values fields, respectively. Tokens that are not saved to a file are only placed in the location attribute of the binding.ws element in the composite. It is expected that you supply a token file at runtime that has tokens matching those manually entered at design time.
   Reference	Displays the external reference you selected in Step 3.
   Protocol	Displays the field in which to specify the protocol token name. Click the Browse icon to select the token name to use from the Token Picker dialog. The Token Picker dialog is populated with the token names that appear in the token file you imported in the Token File field. The token name you select (for example, port1) and its default value (for example, 80) are added to the Token and Current Value fields, respectively. If the token file is writable (meaning an unprotected file in the file system), you can change the current value of the token name. See Step 5 for details about accessing the Token Picker dialog. If the file is read-only, you are warned with a message and allowed to cancel the operation and continue. Manually enter the token name and value to use. You can manually enter information in these fields regardless of whether you imported a file in the Token File field. If you imported a file that is writable in the Token File field and manually enter a token name, it is added to the file if it does not already exist. The current value for the new token name defaults to the value in the URL that is being tokenized.
   Host	Displays the field in which to specify the host token name. See the description of the Protocol field for details about how to specify information.
   Port	Displays the field in which to specify the port token name. See the description of the Protocol field for details about how to specify information.
   Apply these tokens to other References which have the same Current Values	Deselect this check box if you do not want other external references with the same protocol, host, and port values to be replaced with the same tokens. If this check box is selected and you tokenize just one or two of the URL objects, then the references for only those objects are modified. For example, if you only tokenize the host (with a current value of host1.us.oracle), all references that have that same host value are updated.

5. If you selected the Browse button in the Protocol, Host, or Port fields, the Token Picker is displayed, as shown in Figure 35-10. This dialog lists all the tokens that you have defined in the file imported in the Token File field of the Binding URL Tokenization dialog.

   Figure 35-10 Token Picker Dialog

   
   Description of "Figure 35-10 Token Picker Dialog"
6. Select the token name to use through one of the following options:

   • Scroll through the list and select the token.

   • Begin entering the name in the Token field until the name is automatically completed and the token is selected in the list.

7. Click OK.

   You are returned to the Binding URL Tokenization dialog with the selected token name and value displayed in the Token and Current Value fields, respectively.