In the second part of this two part blog post, I will describe the actual creation of the API definition in API Platform Cloud Service (shortened to APIPCS), the service callout to an external microservice (conveniently located in the Oracle Application Container Cloud Service) using a custom Groovy script policy and testing the flow created. The first part discussed the use case for which we used Oracle API Platform Cloud Service (shortened to APIPCS from now on) as an outbound API Gateway, offering lookup services and centralizing outbound access. This part also described a simple Node.js microservice we created to perform the translation of an internal identification into the API key required by the external API.
My first experience with Oracle API Platform Cloud Service – part 2
23 juni 2017
