Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Policy Checkpoint on Apigee for TMForum REST API

2,032 views

Published on

Shows an example of a policy checkpoint for a TMForum REST API. The API implementation is on JElastic, the API Proxy and the policy checkpoint are on Apigee. Used to provide self-service support to API users - so they learn how to use the API effectively.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Policy Checkpoint on Apigee for TMForum REST API

  1. 1. Interactive Self-Service Support for APIs on API Platforms With Policy Checkpoints from Nomos
  2. 2. “API Platform” Companies
  3. 3. API Platforms • Companies put APIs on API Platforms in order to – Control access to the API (security etc) – Publicise, provide easy access to, and ‘monetize’ their APIs – Get analytics on API usage (e.g. what customers use it most)
  4. 4. What Nomos does • Provides ‘interactive support’ / sandbox capability on API Platforms • By adding in ‘policy checkpoints’ for APIs • API users get feedback on how to use the API correctly : self-service support
  5. 5. Example Policy Checks
  6. 6. Apigee Example Policy Checkpoint for TMForum ProductOrder Telecoms REST API, JSON API Proxy on Apigee API Implementation hosted on JElastic Policy Checkpoint built with RuleX from Nomos Using Chrome REST Console 4.0.2
  7. 7. The Flow 1. Order Product API Users API Proxy on Apigee 3. Order Product 2. Apply Policy Product Order Policy Checkpoint Read the blogs: http://nomos-software.com/blog/apis-hackathon-and-apigee-integration http://nomos-software.com/blog/apis-and-hackathoning-again TMForum Product Order API Implementation
  8. 8. Submit Correct Order – REST Client URI: http://nomos1-test.apigee.net/v1/nomosrulexvalidationservice2 Method: POST Content Type: application/json Content Type: Correct Product order request
  9. 9. Apigee Trace for Correct Order Request received from client Policy checkpoint executed Response sent to Jelastic service (no screenshot of response included) Product Order created Response received from Jelastic Final response sent to client
  10. 10. Response for Correct Order – REST Client Response shows the product order that was created
  11. 11. Submit Incorrect Order URI: http://nomos1-test.apigee.net/v1/nomosrulexvalidationservice2 Method: POST Content Type: application/json Content Type: An incorrect Product order request
  12. 12. Trace for Incorrect Order Request received from client Policy checkpoint executed : Fails checkpoint. Transaction aborted Response from policy checkpoint sent to client
  13. 13. Response for Incorrect Order Response gives details of errors in the request, including exact line number of error
  14. 14. Learn more about RuleX? Integrate with another API Platform? Contact us nomos-software.com +353 – 21 - 4928945 @nomossoftware

×