This topic contains the following sections:
Use the ResetContentDescriptor node to request that the message is reparsed by a different parser. If the new parser is MRM, you can also specify a different message template (message set, type, and format). This node does not reparse the message, but the properties that you set for this node determine how the message is parsed when it is next reparsed by the message flow.
The node associates the new parser information with the input message bit stream. If the message has already been parsed to create a message tree, and the contents of the tree have been modified (for example, by a Compute node), the ResetContentDescriptor node must invoke the current parser associated with the message to parse the message and recreate the bit stream.
If your message flow has updated the message before it is received by the ResetContentDescriptor node, you must ensure that the changed message contents are still valid for the current parser. If this is not the case, the parser generates an error when it attempts to recreate the bit stream from the message tree, and the ResetContentDescriptor node raises an exception. For example, if you have added a new field to a message in the MRM domain, and the field is not present in the model, the recreation of the bit stream fails.
The ResetContentDescriptor node does not:
The ResetContentDescriptor node is represented in the workbench by the following icon:
For an example of how to use this node, assume that you want to swap between the BLOB and the MRM domains. The format of an incoming message might be unknown when it enters a message flow, so the BLOB parser is invoked. Later on in the message flow, you might decide that the message is predefined as a message in the MRM domain, and you can use the ResetContentDescriptor node to set the correct values to use when the message is parsed by a subsequent node in the message flow.
The following table shows typical ResetContentDescriptor node properties.
Property | Value |
---|---|
Message Domain | MRM |
Reset Message Domain | Selected |
Message Set | DH53CU406U001 |
Reset Message Set | Selected |
Message Type | m_MESSAGE1 |
Reset Message Type | Selected |
Message Format | CWF |
Reset Message Format | Selected |
The Message Domain is set to MRM, and the MRM parser is invoked when the message is next parsed. The message set, type, and format are the message template values that define the message model, and all the reset check boxes are selected because all the properties need to change.
The ResetContentDescriptor node causes the BLOB parser associated with the input message to construct the physical bit stream of the message (not the logical tree representation of it) which is later passed to the MRM parser. The MRM parser then parses the bit stream using the message template (Message Set, Message Type, and Message Format) specified in this ResetContentDescriptor node.
When you have put an instance of the ResetContentDescriptor node into a message flow, you can configure it. Right-click the node in the editor view and click Properties. The node's basic properties are displayed.
All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk on the properties dialog.
Configure the ResetContentDescriptor node as follows:
You can also specify a user-defined parser if appropriate.
Select the Reset Message Domain check box.
These properties set the domain, set, type, and format that you want in the message header of the message that you want to pass through the ResetContentDescriptor node. However, this only happens if suitable headers already exist. If the message does not have an MQRFH2 header, the node does not create one.
Click Cancel to close the dialog and discard all the changes that you have made to the properties.
The ResetContentDescriptor node terminals are described in the following table.
Terminal | Description |
---|---|
In | The input terminal that accepts a message for processing by the node. |
Failure | The output terminal to which the message is routed if an error is detected by the node. |
Out | The output terminal to which the message is routed if a new parser is identified by the properties. |
The following tables describe the node properties; the column headed M indicates whether the property is mandatory (marked with an asterisk on the properties dialog if you must enter a value when no default is defined), the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).
The ResetContentDescriptor node Basic properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Message Domain | No | No | The message domain associated with the message that you want to reparse. | |
Reset Message Domain | Yes | No | Cleared | Whether to reset the message domain. If you select the check box, this action is performed. |
Message Set | No | No | The message set associated with the message that you want to reparse. | |
Reset Message Set | Yes | No | Cleared | Whether to reset the message set. If you select the check box, this action is performed. |
Message Type | No | No | The message type associated with the message that you want to reparse. | |
Reset Message Type | Yes | No | Cleared | Whether to reset the message type. If you select the check box, this action is performed. |
Message Format | No | No | The message format associated with the message that you want to reparse. | |
Reset Message Format | Yes | No | Cleared | Whether to reset the message format. If you select the check box, this action is performed. |
The ResetContentDescriptor node Description properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Short Description | No | No | A brief description of the node. | |
Long Description | No | No | Text that describes the purpose of the node in the message flow. |
Related concepts
Message flows
Parsers
Message modeling
Related tasks
Deciding which nodes to use
Handling errors in message flows
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac04810_ |