PaaS – How to Manage and Access an API with Oracle API Platform Cloud (Part 3) by Onkar Shoker

In this post, I will cover the following:

• Create a simple REST based service.
• Deploy the service to a separate WebLogic Managed server instance (used to host deployed applications).
• Create the API entry within the Oracle API Platform Cloud instance and point to the service on the application WebLogic Managed server.
• Allow the Oracle API Gateway to poll the Logical Gateway / ‘phone home’ and fetch the API, Policies etc.
• Attempt to access the service via the Oracle API Gateway Node.
• If all goes well, we will be routed to the deployed service and will use the Analytics tool on the API Management Portal to confirm the end-to-end activity.

Notes:

• I am covering a simple end to end. No additional Policies are applied to the API.
• I am using the main Administrator user (weblogic) for all activities. Ideally, we would have users assigned to x and y roles to perform respective tasks.
• The IP addresses of the Application managed server and Gateway Node are being used rather than Load Balancer URL’s – Ideally, the servers will be placed behind an LB and the LB URL will be utilised in the API Management implementation.

Firstly, create and deploy an API service to an Application server

1. I have created a REST service – I won’t go in-depth too much in terms of the coding, but I have used JDeveloper to create a simple service and when invoked, will return a JSON response: Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress