21 Working with Multiple Part Messages in Mediator

This chapter describes how to use multiple part (multipart) messages with Oracle Mediator (Mediator) service component.

This chapter includes the following section:

• Section 21.1, "Introduction to Mediator Multipart Message Support Feature"

21.1 Introduction to Mediator Multipart Message Support Feature

Oracle Application Server 11g release includes support for importing multipart WSDL files in the JDeveloper Mediator Editor.

Oracle Mediator supports working with multipart source and target messages, which include multipart filter expression building, multipart schema validation, and transformations between multipart source and target messages for requests, replies, faults, and callbacks.

The Mediator Editor for a multipart source looks like Figure 21-1.

Figure 21-1 Mediator Editor for a Multipart Source

Description of "Figure 21-1 Mediator Editor for a Multipart Source"

This section covers the following sections:

• Section 21.1.1, "Working with Multipart Request Messages"

• Section 21.1.2, "Working with Multipart Reply, Fault, and Callback Source Messages"

• Section 21.1.3, "Working with Multipart Target Messages"

21.1.1 Working with Multipart Request Messages

This section deals with multipart request messages. It contains the following sections:

• Section 21.1.1.1, "Specifying Filter Expressions"

• Section 21.1.1.2, "Adding Validations"

• Section 21.1.1.3, "Creating Transformations"

• Section 21.1.1.4, "Assigning Values"

21.1.1.1 Specifying 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 21-2:

Figure 21-2 Expression Builder for a Multipart Request Source

Description of "Figure 21-2 Expression Builder for a Multipart Request Source"

21.1.1.2 Adding Validations

If you add a validation for a multipart message, then the Add Validation dialog displays a list of parts, from where you can choose one part. You specify a Schematron file for each request message part and then Mediator processes the Schematron files for the parts. This is shown in Figure 21-3, Figure 21-4, and Figure 21-5:

Figure 21-3 Add Validation Dialog for a Multipart Request Source

Description of "Figure 21-3 Add Validation Dialog for a Multipart Request Source"

Figure 21-4 Add Validation Dialog for a Multipart Request Source

Description of "Figure 21-4 Add Validation Dialog for a Multipart Request Source"

Figure 21-5 Validations Dialog for a Multipart Request Source

Description of "Figure 21-5 Validations Dialog for a Multipart Request Source"

21.1.1.3 Creating 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 transformation tool as shown in Figure 21-6:

Figure 21-6 XSLT Mapper transformation tool for a Multipart Request Source

Description of "Figure 21-6 XSLT Mapper transformation tool for a Multipart Request Source"

21.1.1.4 Assigning 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. Figure 21-7, Figure 21-8, and Figure 21-9 illustrate how you can assign values to a multipart message.

Figure 21-7 Assign Values Dialog for a Multipart Request Source

Description of "Figure 21-7 Assign Values Dialog for a Multipart Request Source"

Figure 21-8 Assign Value Dialog for a Multipart Request Source

Description of "Figure 21-8 Assign Value Dialog for a Multipart Request Source"

Figure 21-9 Expression Builder for a Multipart Request Source

Description of "Figure 21-9 Expression Builder for a Multipart Request Source"

21.1.2 Working with Multipart Reply, Fault, and Callback Source Messages

The method to create transformations and assigning values to multipart Reply, Fault, and Callback source messages, is the same as working with request source message.

Note: You cannot specify filter expressions or add validations for Reply, Fault, and Callback messages.

21.1.3 Working 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 transformation tool does not support multipart targets. So, in such a case, the Mediator creates and coordinates a separate mapper file for each target part as shown in Figure 21-10:

Figure 21-10 Request Transformation Map for a Multipart Routing Target

Description of "Figure 21-10 Request Transformation Map for a Multipart Routing Target"