Subflows will be generated to log and trace the request, response, and modelled fault messages.
- Log messages in a database: A Subflow with a Message Logger mediation primitive with the Logging type option
set to Database is generated.
- Log messages using custom Java: A Subflow with a Message Logger mediation primitive with the Logging type option
set to Custom is generated.
- Emit messages as common base events to a CEI server: A Subflow with an Event Emitter mediation primitive is generated.
Logging options for the request, response and modelled fault flows are:
- Do not log messages: Logging will not be performed in this flow.
- Log messages on flow entry: Logging will be performed on entry to the flow.
- Log messages on flow exit: Logging will be performed on exit from the flow.
- Log messages on flow entry and exit: Logging will be performed on both entry to the flow and exit from the flow.
Tracing before and after the message tranformation can be enabled for the request, response, and
modelled fault flows:
If Request Flow Tracing is selected, a Subflow containing a Trace mediation primitive
is generated in the request flows to print the request messages to the local server log.
If Response Flow Tracing is selected, a Subflow containing a Trace mediation primitive
is generated in the response flows to print the response messages to the local server log.
If Modelled Fault Tracing is selected, a Subflow containing a Trace mediation primitive
is generated to print modelled fault messages to the local server log.