To the upper right of the Input field, click Add a new message part. In the Part Name field, enter a name for the message part. To the right of the URL field, click the browse for schema file icon to browse for

18-32 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 18–31 Add Message Part Dialog

4. In the Part Name field, enter a name for the message part.

5. To the right of the URL field, click the browse for schema file icon to browse for

the URL. The Type Chooser dialog appears and contains a list of the schema files XSD files, as shown in Figure 18–32 . Figure 18–32 Type Chooser Dialog

6. Expand the Type Explorer tree to locate and select the schema element to use.

If the schema you want to use is not located in the project in which you are working, you can import a schema XSD file or WSDL file into the project using the Import Schema File or Import WSDL icon in the upper right corner of the dialog. After you specify a file, Oracle JDeveloper parses it to determine the defined schema elements and displays them in a list from which you can make a selection.

7. Select the root element of the XSD file and click OK.

The Add Message Part dialog reappears with the URL and Schema Element fields populated from the Type Chooser dialog. If you selected an XSD simple type, these fields are replaced by a Simple Type element.

8. Click OK on the Add Message Part dialog.

Note: If you want to use a schema XSD file that resides on your local file system, ensure that the XSD file and any XSD files that it imports all reside in the Oracle JDeveloper project directory. This ensures that the schema is deployed with the project and is made available at runtime. Getting Started with Oracle Mediator 18-33 The input information appears in the Input field of the Create WSDL dialog. 9. Repeat the above steps to define the input message parts for the Callback section. 10. In the Callback section, specify the following information for the response message: ■ 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, executeResponse.

11. Click OK.

To generate the WSDL file based on a sample file: You can generate a WSDL file from a file in a native format such as a comma-separated value CSV file, a fixed-length file, a document type definition DTD file, or a COBOL copybook file. Use the Native Format Builder wizard to generate a WSDL file based on a sample file. The Native Format Builder wizard appears when you click Define Schema for Native Format in the Request, Response, Fault, and Callback tabs of the Create WSDL dialog. A WSDL file is generated after you complete the wizard. For information about the Native Format Builder wizard, see the Oracle Fusion Middleware Users Guide for Technology Adapters.

18.6 Specifying Operation or Event Subscription Properties

After creating an Oracle Mediator, you can use the Mediator Editor to select the Validate Syntax XSD checkbox for an operation or event subscription. You can select this option to validate the schemas of the inbound messages. By default, this checkbox is not selected.

18.7 Modifying an Oracle Mediator Service Component

You can modify the operations or event subscriptions of an Oracle Mediator using the Mediator Editor. Note: The callback input represents the response message and is required in asynchronous transactions. 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. Both of these fields are required. Note: Partner link types are generally used in BPEL, so you do not need to select Generate partnerlinkType extension for Oracle Mediator.