Getting Started!
This pattern shows some of the built-in functionality in pattern authoring.
The pattern has a single message flow project called Transform which contains an ESQL script and
a message flow. The message flow reads messages from an input queue and writes them straight to an output
queue with no transformation. If the pattern user enables logging, an additional MQOutput node is added
to the message flow which writes every message to a logging queue.
Here are some features to look out for in this pattern:
- The MQInput node has several target properties configured - open the Transform message flow
in the Message Flow editor and you will see the pattern icon next to the MQInput node.
- The Transform message flow also has a UDP called Logging which is configured as a
target property.
- The Queue name pattern parameter uses an XPath expression to concatenate its value with the
Queue prefix and Queue suffix pattern parameters when the pattern user generates a
pattern instance.
- The Queue prefix and Queue suffix pattern parameters use an enablement XPath expression
to conditionally enable them depending on the value of the Configure queue prefix and suffix
pattern parameter. The Configure queue prefix and suffix pattern parameter is a boolean value
and presents a check box to the pattern user rather than the regular text entry field editor.
- The Message domain pattern parameter has an enumerated list of values which configure the
permissible message domains presented to the pattern user. The full list of message domains has been
reduced to just MRM and XMLNSC.
- The Message set pattern parameter uses a message set editor so that the pattern user can
choose a message set from their workspace. Similarly, the Message type and Message format
pattern parameters use message type and message format field editors so that the pattern user can choose
a message type and format from their message set.
- The Message type and Message format pattern parameters use an enablement expression
so they are only enabled when the pattern user chooses MRM as the message domain.
- A PHP template creates an MQSC script which configures the input queue name. This PHP template
is invoked when a pattern instance is generated. The PHP code uses the $_MB super global to
get access to the value of the Queue name pattern parameter.
- A Java class called GettingStarted is invoked whenever a pattern instance is generated.
This Java class checks the value of the Logging pattern parameter and conditionally removes
the Logging MQOutput node from the Transform message flow.