Use one or more of the following
options for transforming and enriching the messages in your message
flows.
- Visual transformation choices
-
- Use the Mapping node
to transform the incoming message, create new output messages, and
interact with information in a database by using a graphical data
map. You can also include the Local Environment tree and transport
headers in the message map to achieve routing and control.
- Use the XSLTransform node
to transform the incoming XML message by using an XSL style sheet.
- Choices for implementing transformation, routing, and integration
by using programming languages
-
- Use the .NETCompute node
to route and transform the incoming message, create a new output message,
or interact with .NET modules by using a the .NET C#, VB or F# programming
languages.
- Use the JavaCompute node
to route and transform the incoming message, create a new output message,
or interact with Java classes by using Java. Optionally use JAXB to
model message data.
- Use the Compute node
to route or transform the incoming message, create new output messages
by using the ESQL language.
- Choices for implementing transformation, routing, and integration
by using scripting languages
-
- Use the PHPCompute node
to route and transform the incoming message by using the PHP scripting
language.
For more information about these options, see Client application programming interfaces. To use some of these options for transforming
and enriching messages, you might need to create a model of the messages
that you want to transform. For information about how to develop a
message model, and why you might want to develop a message model,
see Constructing message models.
For details of the tasks
that are associated with these options, use the instructions in the
following sections:
Last updated Friday, 21 July 2017