...
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 Publisher is allowed to select the predefined 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 registry collection to store the sequences file. For sequences, create "customsequences" at collection at apimgt governance registry location. The registry path will be like " /_system/governance/apimgt/customsequences".
In the "customsequences" collection , user has to create two collections "in" and "out" for InSequences and OutSequences.
Note: If registry collection is not available, user has to create the collection prior to store the sequences.
Store the InSequence files at apimgt/customsequences/in folder folder .
| Info | ||
|---|---|---|
|
...
If you have a in sequence file named as "testInSequence", you need to save the file |
...
in the following location ; /_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: Store the OutSequence files at apimgt/customsequences/out folder .
| Info | ||
|---|---|---|
| ||
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 these sequences 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 with the naming convention as described above and deployed to synapse when we publish the API to gateway.
...