What Happens When You Create an Oracle Mediator for an Event Subscription

Getting Started with Oracle Mediator 18-25 This defines a filter to be applied to the message before a rule is executed. Filters use XPath standards and enable selective execution of Oracle Mediator routing rules. – Semantic Validation This uses the Schematron validation standard to define semantic validation of incoming requests. Semantic validation also verifies that the data is correct. – Transformation This transforms incoming data to a format that is compliant with the called services or published events. Transformation is based on XSL transformation standards. – Assign This manipulates headers and properties for a message to meet the requirements of the called service. ■ Dynamic Routing Rule A dynamic routing rule lets you externalize the routing logic to an Oracle Rules Dictionary, which in turn enables dynamic modification of the routing logic in a routing rule. This feature depends on a decision service and Oracle Rules to obtain the routing logic at runtime.

18.5 Generating a WSDL File

You can generate the WSDL file for a message using an XML schema definition XSD file or using a sample file. When working with Oracle Mediator, you can generate a WSDL file at either of the following times: ■ When you are creating an Oracle Mediator and you select the Interface Definition from WSDL template in the Create Mediator dialog, selecting Generate WSDL from Schemas next to the WSDL URL field opens the Create WSDL dialog. ■ When you have an Oracle Mediator with no interface defined and you click Define Service next to the WSDL URL field in the Mediator Editor, selecting Generate WSDL from Schemas next to the WSDL URL field opens the Create WSDL dialog. The Create WSDL dialog populates standard fields, such as the file name, directory, and namespace; and the dialog changes depending on the interface type you select. You can specify the same or different schema files for the message inputs.

18.5.1 How to Generate a WSDL File

The way you configure a WSDL file depends on the type of interface being defined by the WSDL file. You can define a one-way interface, a synchronous interface, or an asynchronous interface. Note: Oracle recommends using a Unicode database with AL32UTF8 as the database character set for full globalization support in Oracle Mediator. 18-26 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite To generate a WSDL file for a one-way interface from an XSD file: Perform these steps after the Create WSDL dialog appears when you are creating an Oracle Mediator component or when you are defining a service for an Oracle Mediator component. 1. On the Create WSDL dialog, accept the default values or enter the following information for the WSDL file: ■ File Name : A unique name for the WSDL file. ■ Directory : The directory where you want to store the WSDL file. By default, it is stored in the same location as the Oracle Mediator file. This must be the current project directory or one of its subdirectories. If the specified directory does not exist, Oracle JDeveloper creates it. ■ Namespace : A namespace address for the WSDL file; for example, http:oracle.comesbnamespacesMediator. The namespace that you specify is defined as the tns namespace in the WSDL file. ■ Port Type : The name of the port type in the WSDL file that contains the operation to use. ■ Operation : The name of the action to perform; for example, executeQuery.

2. In the Interface Type field, select One-Way Interface.

The Input field appears, as shown in Figure 18–24 . Figure 18–24 Create WSDL Dialog for a One-Way Interface

3. To the upper right of the Input field, click Add a new message part.

Note: Spaces and special characters are not allowed in an operation name or port type. Only alphabetic and numeric characters are supported, and the first character cannot be a number.