Apply DFDL Transformation Assertion

The
Apply DFDL Transformation
assertion parses message/data using a saved-parser generated from a pre-compiled DFDL schema and produces an XML or JSON infoset as its output (Parsing) and also unparses XML or JSON infoset back to its original form (Unparsing).
For instructions on how to install this assertion, see Install the Apply DFDL Transformation Assertion. After it is installed, this assertion is available from both
Message Validation/Transformation
and
Custom Assertions
palettes.
Using the Assertion:
  1. Do one of the following:
    1. To add the assertion to the policy development window, see Add an Assertion. You can also right-click anywhere in the policy development window and then select Add 'All' Folder. This creates an assertion folder in the policy window.
    2. To change the configuration of an existing assertion, proceed to Step 2 below.
  2. When adding the assertion, the
    DFDL Transformation Properties
    dialog automatically appears; when modifying the assertion, right-click Apply DFDL Transformation in the policy window and select
    DFDL Transformation Properties
    or double-click the assertion in the policy window. The assertion properties are displayed.
  3. Configure the properties as necessary to parse/unparse message/data into/from XML and JSON infoset with a saved DFDL parser:
    1. Select the
      DFDL Processor
      that you need to use to parse or unparse from the drop-down menu.
    2. Choose if the
      Operation
      is to parse or unparse.
      Default:
      Parse
    3. Enter the context variable of the
      Input Message
      .
      Default:
      request
    4. Enter the context variable of the
      Output Message
      .
      Default:
      response
    5. Select the
      Content Type
      of the output variable from the drop-down menu. For Unparse operation, you can enter context variable in this field.
  4. Click
    OK
    to save.
Cluster Properties
Name
Description
dfdlProcessorPoolSize
Defines the maximum number of DFDL schema data processors in the cache. If this number is reached, the least recently used data processor is removed from the cache.
Default:
100
dfdlProcessorPoolItemIdleTimeout
Defines the time (in milliseconds) that the item in the cache is kept unused.
Default:
300000
Limitations
The
Apply DFDL Transformation
assertion utilizes the daffodil library to read and parse message/data using a saved-parser generated from a pre-defined DFDL schema. The saved-parser does not contain any information about the original DFDL Schema and so validation is not supported. To validate the output against the original DFDL schema, see Validate XML Schema Assertion.