Map your request and response operations, add a persistent property
to the correlation context and transform the message so that it matches the
requester and provider interfaces.
- In the Business Integration view, expand the XSLTransform module.
- Open the Assembly Editor by double-clicking Assembly
Diagram .
- In the module assembly diagram, right-click on the XSLTransform_MediationFlow component
and choose Generate Implementation.

- Click OK to generate the mediation flow
in XSLTransform. This action opens XSLTransform_MediationFlow in
the mediation flow editor.
- In the Operation connections section, wire StockQuoteRequester interface's getQuote operation
to StockQuoteServicePartner interface's getStockQuote operation.
You will see the request flow with an input and a callout for the operation.
- Add the CustomerInformation business object to the correlation
context of the input getQuote : StockQuoteService. This will allow
the property customerID to persist in the message flow. Click on Input:
getQuote : StockQuoteService and switch to the Details tab in the Properties
view. In the Correlation Context field, click Browse. Select CustomerInformation under
matching data types, and click OK.

- {http://CorrelationContext}CustomerInformation now appears
in the Correlation Context field.

- Select an XSL Transformation primitive from
the palette, drop it onto the request flow canvas, and name it TransformToStockQuoteService.
- In the request flow canvas, wire the output terminal of getQuote
: StockQuoteService to the input terminal of TransformToStockQuoteService.
- Wire the output terminal of TransformToStockQuoteService to
the input terminal of getStockQuote : StockQuoteServicePartner.

- Set the properties for the XSL Transformation primitive TransformToStockQuoteService:
- Select the TransformToStockQuoteService primitive
in the request flow canvas. Switch to the Details tab
in the Properties view.
- Click on the New button next to the Mapping
File field. In the Specify Message Types wizard, change the message
root to / . Click Finish.
- In the Source section of the mapping editor, expand tns:smo
> body [0..1] > getQuote. In the Target section, expand tns:smo
> context > correlation [0..1] and tns:smo > body [0..1]
> getStockQuote.
- Click on customerID in the body section of the Source, then
click on customerID [0..1] in the context section of the Target. Right-click,
and select Create Mapping. This action maps the value
of the customerID in the message body to the correlation context so that it
is persisted throughout the request and response flows.
- Click on symbol in the Source, then click on stockSymbol in
the Target. Right-click, and select Create Mapping
- Because we selected / as root, we need
to manually map the remaining fields. Click on smo in the Source, then click
on smo in the Target. Right-click, and select Match Mapping.
All remaining fields should now be mapped.

- Save your changes and close the mapping editor.
- The he mapping file and its associated XSL are shown in the
properties view of the primitive.

- Save your changes in the mediation flow editor.