...
For more information on Handlers, see Architecture Components.
Allowing publisher to select the predefined sequences
If we have custom sequences with the naming convention as described above we can execute them. But if we want to allow publisher to select the sequences, when he defines the API, now we can do that via publisher webapp.
User can design all sequences using Dev Studio or any other tool, and store the sequence.xml file in the governance registry. We have introduced a new collection called "customsequences" at apimgt governance registry location. Store the InSequence files at apimgt/customsequences/in folder
Eg: If you have a in sequence file named as "testInSequence", you need to save the file here;
/_system/governance/apimgt/customsequences/in/testInSequence.xml
Same like insequence, for Out Sequences, user need to create another folder called "out" parallel to "in" folder.
Eg: If you have a out sequence file named as "testOutSequence", you need to save the file here;
/_system/governance/apimgt/customsequences/out/testOutSequence.xml
After saving the files, these seuences will be visible at publisher webapp, when publisher try to create an API. User has to check the option at the UI to select a custom sequence for InFlow and OutFlow.
Those sequences will be renamed and deployed to synapse when we publish the API to gateway.