Parsing Step

The parsing step can be used to pre-process a facade operation request.

The parse step is an optional preprocessing of the facade request used for both content validation and for identifying and normalizing control data. Using the parse step you can enhance the downstream processing by setting or overwriting predefined parameters that are derived either from the request message content or the request transport context. The parsing of the request is done using an XSLT- based transformation file configured in the New ProcessBody Transform or ProcessBody Transform field on the ROUTING > Facade Operations tab of the Config UI.

The transformation (XSLT) file defined in the parsing step is used for the following purposes:

  • Setting a partner identity for the requester that is derived from the payload content or transport context of the request
  • Setting a routing key that is used to identify the route for the request to the appropriate target operation endpoint
  • Enriching the transaction audit trail logging information of the request
  • Validating the request content with the ability to set an error code and error message when a request does not pass the content validation rules
  • Setting a metric increment for content-based throttles
  • Setting sticky key for load-balancing with StickyResourceAffinity routing algorithm type.