The API Manager allows mediation sequences to be added to the processing flow of an API invocation.
BYU has created a number of mediation sequences to allow for customization of message processing to meet our specific needs.
Types of Mediation Sequences
API Manager allows for mediation sequences to be added to the following three processing flows:
in - The input flow of the message. These mediators will be executed before the message is passed to the destination service.
out - The output flow of the message. These mediators will be executed after the message has been passed to the destination service, and before the result is passed back to the consumer.
fault - The fault flow of the message. These mediators will only be executed if there is a fault detected in the processing stream of the message, before the fault is passed back to the consumer.
Currently BYU has only defined in-flow message mediators. The API Manager has provided a number of standard mediation sequences as well.
Legacy System Support
BYU has created the following mediation sequences for support of legacy systems:
AddCFrameworkHeaders - Adds HTTP Headers to the request for use by legacy CFramework and other systems.
AddPeopleSoftWSSecurityHeader - Adds a WS-Security Header to the request for use by PeopleSoft SOAP services.
Specifying a Mediation Sequence
Specifying a mediation sequence is done in the API Manager Publisher tool. To specify a mediation sequence to be included in the processing flow for an API call, select the "Message Mediation" checkbox, and then select the desired mediation sequence from the drop down lists provided.