Book Image

Implementing Oracle API Platform Cloud Service

By : Andrew Bell, Sander Rensen, Luis Weir, Phil Wilkins
Book Image

Implementing Oracle API Platform Cloud Service

By: Andrew Bell, Sander Rensen, Luis Weir, Phil Wilkins

Overview of this book

Implementing Oracle API Platform Cloud Service moves from theory to practice using the newest Oracle API management platform. This critical new platform for Oracle developers allows you to interface the complex array of services your clients expect in the modern world. First, you'll learn about Oracle’s new platform and get an overview of it, then you'll see a use case showing the functionality and use of this new platform for Oracle customers. Next, you’ll see the power of Apiary and begin designing your own APIs. From there, you’ll build and run microservices and set up the Oracle API gateways. Moving on, you’ll discover how to customize the developer portal and publish your own APIs. You’ll spend time looking at configuration management on the new platform, and implementing the Oauth 2.0 policy, as well as custom policies. The latest finance modules from Oracle will be examined, with some of the third party alternatives in sight as well. This broad-scoped book completes your journey with a clear examination of how to transition APIs from Oracle API Management 12c to the new Oracle API Platform, so that you can step into the future confidently.
Table of Contents (12 chapters)

Summary

This chapter starts by explaining the high-level features of API Fortress and continues to explain some of the features in more detail by testing the MRA Media Catalogue API. This includes the creation of two test cases. The assertions of one test case are created using an existing Postman Collection from Chapter 4, Building and Running the Microservice and the other test case assertions are created from importing the interface definition from Apiary as designed in Chapter 3, Designing the API.

The test cases created include additional assertions to validate the HATEOAS links in the response, and include the use of variables to dynamically update the request payload with unique identifiers to ensure the resources of Artist, Album, and Song can be re-run without receiving an error that the resource already exists. The Vault is used to forward the artist id that has been...