Question & Answer
Question
Answer
On Demand Consulting
Author: Uday Pilai
Overview
Intended Audience
Administrators planning to build a highly available API Connect CloudKey Components in an API Connect Topology
By configuring multiple Management servers and multiple Gateway servers, your cloud benefits from high availability (HA). When you define more than one Management server, configure an external load balancer. Then, if one server is removed for planned maintenance or an unplanned failure, your users can continue to access the cloud. The more servers that you add the greater the ability of your cloud to withstand outages and continue to provide processing capability.Gateway Servers
Process and manage security protocols and stores relevant user and appliance authentication data. The Gateway servers also provide assembly functions that enable APIs to integrate with various endpoints such as databases or HTTP-based endpoints.
Management Servers
Manage the operations of the various servers in the API Cloud. The Management servers also provide analytic functions that collect and store information about APIs and API users.
Advanced Developer Portal
The Advanced Developer Portal enables API providers to build a customized developer portal for their application developers.
Collective Servers
A collection of runtime environments for APIs that have been created. The collective is also used as the runtime for the Micro Gateway.

Typical API Connect Production Topology
Common "production like" environments will include:
- Management Service: 2 Management Servers
- Developer Portal Service: 3 Advanced Developer Portal Servers
- DataPower Service: 2 AppliancesDataPower
API Connect Topology - Data Center View

Typical Non-Production (DevtestQA) API Connect topology
- Management Server
- Developer Portal
- DataPower Gateway (virtual appliance)

Was this topic helpful?
Document Information
Modified date:
26 March 2019
UID
ibm10773011