Chapter 2. Reference Architecture Environment
This reference architecture relies on a previous reference architecture application and environment thoroughly described in the paper titled Building Microservices on OpenShift Container Platform with Fuse Integration Services.
This environment installs Red Hat 3scale API Management Platform on OpenShift Container Platform and uses 3scale API Management Platform’s functions to control access to the Fuse gateway service, set rate limits on certain service calls, develop ActiveDocs from the swagger file and display them on Developer Portal of 3scale API Management Platform. A separately deployed Presentation application on OpenShift is used to make various calls to the Fuse gateway service service through 3scale API Management Platform and demonstrate the end to end integration.
The configuration of 3scale API Management Platform for this reference architecture includes creating three APIs in the Admin Portal, based on the Fuse gateway service. These three APIs will be used by three different type of users:
- Internal user: Access to every API exposed by Fuse gateway service, including product, sales, billing and fulfillment.
- Partner user (third party): Access is limited to only product calls, and exclusively to inquiry, add, delete and update of products.
- Public user: Access is limited to only product inquiry, and further limited to just 5 HTTP GET requests per minute

OpenShift Container Platform may be deployed with either a single, or three master hosts for this reference architecture. In both cases, it is assumed that ocp-master1 refers to one (or the only) OpenShift master host and that the environment includes two OpenShift node hosts with the host names of ocp-node1 and ocp-node2.
It is further assumed that OpenShift has been installed by the root user and that a regular user has been created with basic access to the host machine, as well as access to OpenShift through its identity providers.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.