4.6 Create Mediator Dialog
Use the Create Mediator dialog to create a Mediator Component. How?
A Mediator component enables you to route data between service consumers and service providers.
Element | Description |
---|---|
Name |
Enter a name for the Mediator component. |
Directory |
Specify a directory to store the Mediator file. You can also click the Browse button to select a directory. The directory must be the current project directory or one of its subdirectories. If the specified directory does not exist, Oracle JDeveloper creates it. |
Template |
Select a template on which you want to base the new Mediator component. A template provides a basic set of default files for the Mediator component. The options following the template field in the dialog vary, depending on the template selected. |
Define Interface Later |
Select this option to create an empty Mediator component with no interface defined. You can later define the interface in the SOA Composite Editor or Mediator Editor by defining the services or subscribing to events. |
Asynchronous Interface |
Select this option to create a Mediator component for asynchronous interaction. When you select this template, the WSDL file and the ports for the request message (Port Type) and the response message (Callback Port Type) are defined for the Mediator component. |
Create Composite Service with SOAP Bindings |
Select this checkbox to create a Mediator component that is automatically connected to an inbound SOAP service-binding component. If you do not select this checkbox, then the Mediator component is created as a standalone component in the SOA Composite Editor. You can explicitly associate the Mediator component with a service later. |
Input |
Accept the default input XSD schema or click Browse Input Elements icon to select a different schema for the input message. By default, singleString schema is used for the input message. |
Output |
Accept the default output XSD schema or click Browse Output Elements icon to select a schema definition file for the output message. By default, singleString schema is used for the output message. |
Synchronous Interface |
Select this option to create a Mediator component for synchronous interaction. When you select this template, the WSDL file and the port (Port Type) for the request and the response message are defined for the Mediator component. |
Create Composite Service with SOAP Bindings |
Select this checkbox to create a Mediator component that is automatically connected to an inbound SOAP service-binding component. If you do not select this checkbox, then the Mediator component is created as a standalone component in the SOA Composite Editor. You can explicitly associate the Mediator component with a service later. |
Input |
Accept the default input XSD schema or click Browse Input Elements icon to select a different schema for the input message. By default, singleString schema is used for the input message. |
Output |
Accept the default output XSD schema or click Browse Output Elements icon to select a schema definition file for the output message. By default, singleString schema is used for the output message. |
One-Way Interface |
Select this option to create a Mediator component for one-way interaction. |
Create Composite Service with SOAP Bindings |
Select this checkbox to create a Mediator component that is automatically connected to an inbound SOAP service-binding component. If you do not select this checkbox, then the Mediator component is created as a standalone component in the SOA Composite Editor. You can explicitly associate the Mediator component with a service later. |
Input |
Accept the default input XSD schema or click Browse Input Elements icon to select a different schema for the input message. By default, singleString schema is used for the input message. |
Interface Definition from WSDL |
Select this option to define the services of a Mediator component from a WSDL file. A WSDL file describes the interface of a Mediator component such as schemas and operations. |
Create Composite Service with SOAP Bindings |
Select this checkbox to create a Mediator component that is automatically connected to an inbound SOAP service-binding component. If you do not select this checkbox, then the Mediator component is created as a standalone component in the SOA Composite Editor. You can explicitly associate the Mediator component with a service later. |
WSDL File |
Specify the URL of the WSDL file. Click the Find existing WSDLs icon to select an existing WSDL file or click the Generate WSDL from schema(s) icon to generate a WSDL file. |
Port Type |
Select a port type. The Port Type dropdown list is populated based on the ports defined in WSDL file. |
Callback Port Type |
Select a callback port type. The callback port is required in case of asynchronous interactions. The Callback Port Type lists all the ports defined in your WSDL file. |
Subscribe to Events |
Select this option to create a Mediator component for subscribing to a business event that is raised when a situation of interest occurs. |
Edit Event Filter Expression |
Click to specify an XPath expression to filter an event. |
Subscribe to a new event |
Click to subscribe to an event. |
Delete the event description |
Click to unsubscribe from an event. |
Event |
Displays the name of the subscribed event. |
Consistency |
Select a level of delivery consistency for the event. If you select one and only one, there is exactly one delivery guaranteed. The event delivery is conducted in a global transaction. If you select guaranteed, at least one delivery is guaranteed. Event delivery is conducted in a local transaction. |
Durable |
If you select yes, events are retained even if the subscriber is not running. If you select no, events are dropped if the subscriber is not running. |
Run as Publisher |
Enter a security role under which an event subscription is run. By default, event subscription runs under the security of the event publisher $publisher. If you select yes, the subscriber has the event publisher's security identity. If you select no, the subscriber does not have the event publisher's security identity. |
Filter |
Double-click to specify a filter expression for the subscribed event. This selection launches the Expression Builder dialog. |
Click to View Selection Description |
Click to view the description of the selected template. |
Related Topics
Creating a Mediator Component in Developing SOA Applications with Oracle SOA Suite