Configuring the ResetContentDescriptor node

When you add a ResetContentDescriptor node to a message flow, configure it to request that the message is reparsed by a different parser.

1. Optional: On the Description tab, enter a Short description, a Long description, or both.
   You can also rename the node on this tab.
2. On the Basic tab:
   1. To use a different parser associated with the message, specify the new domain in the Message domain property:
      • DFDL
      • XMLNSC
      • DataObject
      • JSON
      • BLOB
      • MIME
      • MRM
      • JMSMap
      • JMSStream
      • XMLNS

      You can also specify a user-defined parser if appropriate.

      You must also select the Reset message domain check box.

      If you leave the Message domain property blank and do not select the Reset message domain check box, the domain is not reset. If you leave the Message domain property blank and select the Reset message domain check box, the default value is BLOB.

   2. If the XMLNSC, IDOC, or MRM parser is to reparse the message, specify the other properties of the model that are to be associated with the input message, and select the relevant reset check box beneath each field. If you select a reset check box for a property and you have not specified a value for that property, the value of that property is reset to blank. Alternatively, if you have specified a value for that property, the property is not blank. If you do not select the reset check box for a property, the value for that property is inherited from the incoming message. If the parser is associated with the input message already, specify only the properties that are to change.
      1. Define the Message model. Choose a value from the list of available message models (the name and identifier of the message model are shown), and select the Reset message modelcheck box.
      2. For DFDL and MRM domains, define the name of the message in Message. Enter the name and select the Reset message check box.
      3. For IDOC and MRM domains, define the Physical format. This property specifies the physical format for the parser. You can select one of the formats from the list (which lists the names of those formats that you have defined on the Message model specified previously), and select Reset physical format.

      These actions are taken only if suitable headers exist. If the message does not have an MQRFH2 header, the node does not create one.

3. On the Parser Options subtab:
   1. Parse timing is, by default, set to On Demand, which causes parsing of the message to be delayed.

      For more information, see Parsing on demand.

   2. Select Use MQRFH2C compact parser for MQRFH2 header if you want the MQRFH2C parser to be used. By default, this check box is cleared, which means that the compact parser is not used.
   3. If you are using the XMLNSC parser, set values for the properties that determine how the XMLNSC parser operates. For more information, see Manipulating messages in the XMLNSC domain.
4. On the Validation tab, set the validation properties if you want the parser to validate the body of messages against the Message set. (If a message is propagated to the Failure terminal of the node, it is not validated.)

   For more information, see Validating messages and Validation properties.