Response Pipeline Processing

After the response is received from the southbound service, the response document is processed for any transformations required from the service response message to the canonical response message. Whether the mapping is required for this request operation or not, it is configured using the Response Transform Mapping field on the ROUTING > Target Operations tab. The transformation details are defined in the Mappings tab of the Config UI.

By default, if no mappings are defined, then the response message is just copied as the output response message at this stage.

Using the reverse northbound mapping, you can transform the canonical response message to the northbound response message. Whether the mapping is required for this request operation or not, it is configured using the Reverse Mapping field on the Operations tab. The transformation details are defined in the Mappings tab of the Config UI.

This mapping can be used for the censor response policy. Using the censor response policy, you can hide certain fields from the response message so that they are not exposed to the requestor.

The response message is finally sent back to the original requestor in this stage.

Generate Transaction

After the request and response messages are processed, the Core Engine generates the events to audit log the transaction details. The Central Logger component receives the events and logs the transaction details in a database.