Enterprise Integration Zone is brought to you in partnership with:

Mark O'Neill is VP Innovation at Axway. Previously, he was CTO and co-founder at Vordel, acquired by Axway in 2012. He is the author of the McGraw-Hill book "Web Services Security" and is frequent speaker at conferences including Java One, the RSA Security Conference, and Oracle Open World. Mark is based on Boston, Massachusetts. Mark is a DZone MVB and is not an employee of DZone and has posted 65 posts at DZone. You can read more from them at their website. View Full User Profile

Get - Set - Go! - Setting an attribute or variable on the Axway/Vordel API Server

02.10.2013
| 2155 views |
  • submit to reddit
I recently lead a workshop in Australia, covering exciting topics like mashing up APIs together, OAuth 2.0, and API monitoring. However, something the less exciting "How To's" can be important too. One common feature I use in the Axway/Vordel API Server is a simple Get/Set: the ability to set an attribute (i.e. a variable) in a policy then to get the value of that variable. I use the "Copy/Modify Attributes" filter to do the "Set". Below, I am setting an attribute/variable called australia.melbourne.weather to "Warm":


Next I do the "Get". So, I use a "Set Message" filter which is outputting the value of this variable, using ${australia.melbourne.weather} :


Then finally I use a "Reflect Message" filter to return my message to the client with an HTTP Code of 200:


Now, I write this up to a path called "/getWeather", like this:


So now when I call the API Server on the path of "/getWeather", I get the weather for Melbourne.


Of course, you could read the variable from a database or from another API. But in this case, I'm showing how you can set it with a "Copy/Modify Attributes" filter, which can be a useful step to perform in your Axway/Vordel API Server policies.
Published at DZone with permission of Mark O'neill, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)