Identifying outbound messages that require transformation

Add a transformation to outbound messages that are destined for endpoints that have specific format requirements.

About this task

When an endpoint requires a specific format, you must define a transformation for your outbound message.

Note: When you have event types with inheritance in your business model definitions, the outbound transformation is applied to all subtypes of the event type that is named in the outbound binding, unless otherwise specified. For example, if your business model definition defines an urgent response event is a response event and the outbound binding specifies a transformation for "response event", then all response events and urgent response events are transformed using the response events transformation. To apply the transformation to the response event only and not to the urgent response event, you must add the urgent response event to the binding, which overwrites the "parent" rendering.

Procedure

Start creating the outbound binding. For example:

define outbound binding 'binding1' 
   using 
      message format application/xml , 
      protocol JMS ,

For each event type, specify a transformation if applicable. For example:

delivering events :
   - fraud alert , transformed using "fraudalert.xsl"
   - credit limit reached , transformed using "creditlimit.xsl" .

Finish creating the binding.
Save your work.

Example

define outbound binding 'binding1' 
   using 
      message format application/xml , 
      protocol JMS , 
   delivering events :
      - fraud alert , transformed using "fraudalert.xsl"
      - credit limit reached , transformed using "creditlimit.xsl" .

What to do next

You can specify message header properties if necessary, and then specify the outbound endpoints.