Task 6: How to Configure an Application Server Connection Task 7: How to Deploy the SOA Composite Application

20-2 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

20.2 Working with Multipart Request Messages

This section describes how to work with different types of multipart messages.

20.2.1 How to Work with Multipart Request Messages

This section describes multipart request messages.

20.2.1.1 How to Specify Filter Expressions

If you specify a filter expression for a multipart message, then the Expression Builder displays all message parts under the in variable, as shown in Figure 20–2 : Figure 20–2 Expression Builder for a Multipart Request Source

20.2.1.2 How to Add Validations

If you add a validation for a multiple part message, then the Add Validation dialog displays a list of parts from which you can choose one part, as shown in Figure 20–3 . You specify a Schematron file for each request message part. Oracle Mediator then processes the Schematron files for the parts. Working with Multiple Part Messages in Oracle Mediator 20-3 Figure 20–3 Add Validation Dialog for a Multipart Request Source

20.2.1.3 How to Create Transformations

If you create a new mapper file for a multipart message, then the generated mapper file shows multiple source parts in the XSLT Mapper, as shown in Figure 20–4 : Figure 20–4 XSLT Mapper for a Multipart Request Source

20.2.1.4 How to Assign Values

If you assign values using a source expression, then the Expression Builder shows an in variable for each message part. This is the same as specifying filter expressions.

20.2.2 How to Work with Multipart Reply, Fault, and Callback Source Messages

The method to create transformations and assign values to multipart reply, fault, and callback source messages is the same as working with request source messages. 20-4 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

20.2.3 How to Work with Multipart Target Messages

If a routing target that is, a request, reply, fault, or callback has a multipart message, then the transformation is handled in a slightly different way. This is because the XSLT Mapper does not support multipart targets. In such a case, the Oracle Mediator creates and coordinates a separate mapper file for each target part, as shown in Figure 20–5 : Figure 20–5 Request Transformation Map for a Multipart Routing Target Note: You cannot specify filter expressions or add validations for reply, fault, and callback messages.