Details of the API Connect deployment profiles that are provided for OpenShift and Cloud
Pak for Integration.
API Connect provides
various profiles to suit your capacity and availability requirements.
The API Connect deployment
profiles provide one Management component instance, and one instance of the Portal, Analytics, and
Gateway components.
On
Cloud Pak for Integration:
- The available deployment profiles are presented as tiles in the Platform UI.
- The Portal, Analytics, and Gateway components are automatically registered with the Management
component during installation.
n1xc7.m48: Small - One replica
Best suited for light, noncritical workloads such as small team development and testing. Deploys
1 replica of the Management, Developer Portal, Analytics, and Gateway
components with a minimal
footprint.
Table 1. n1xc7.m48
| Management |
n1xc2.m16 |
| Portal |
n1xc2.m8 |
| Analytics |
n1xc2.m16 |
| Gateway |
n1xc1.m8 |
n1xc16.m72: Medium - One replica
Ideal for medium workloads such as organizational development, testing, and production when in
alignment with business availability requirements. Deploys 1 replica of the Management, Developer
Portal, Analytics, and Gateway
components.
Table 2. n1xc16.m72
| Component
name |
Component
profile |
| APIM |
n1xc4.m16 |
| Portal |
n1xc4.m16 |
| Analytics |
n1xc4.m32 |
| Gateway |
n1xc4.m8 |
n3xc16.m48: Large - Three replicas
Ideal for heavy workloads when business requires redundancy for greater availability &
capacity. Deploys 3 replicas of the Management, Developer Portal, Analytics, and Gateway
components.
Table 3. n3xc16.m48
| Component
name |
Component
profile |
| APIM |
n3xc4.m16 |
| Portal |
n3xc4.m8 |
| Analytics |
n3xc4.m16 |
| Gateway |
n3xc4.m8 |
n1xc12.m64: Medium - One replica - Remote Gateway
Ideal for medium workloads such as organizational development, testing, and production when in
alignment with business availability requirements. Must be configured for use with existing or
independently deployed Gateways. Deploys 1 replica of the Management, Developer Portal, and
Analytics
components.
Table 4. n1xc12.m64
| Component
name |
Component
profile |
| APIM |
n1xc4.m16 |
| Portal |
n1xc4.m16 |
| Analytics |
n1xc4.m32 |
n3xc12.m40: Large - Three replicas - Remote Gateway
Ideal for heavy workloads when business requires redundancy for greater availability &
capacity. Must be configured for use with existing or independently deployed Gateways. Deploys 3
replicas the Management, Developer Portal, and Analytics
components.
Table 5. n3xc12.m40
| Component
name |
Component
profile |
| APIM |
n3xc4.m16 |
| Portal |
n3xc4.m8 |
| Analytics |
n3xc4.m16 |
Deprecated profiles
The
API Connect deployment
profiles presented here existed in previous releases, but are now in a deprecated state and should not be
used for new installations.
Table 6. n3xc11.m48
| Component
name |
Component
profile |
| APIM |
n3xc2.m16 |
| Portal |
n3xc4.m8 |
| Analytics |
n3xc4.m16 |
| Gateway |
n3xc1.m8 |
Table 7. n3xc14.m48
| Component
name |
Component
profile |
| APIM |
n3xc2.m16 |
| Portal |
n3xc4.m8 |
| Analytics |
n3xc4.m16 |
| Gateway |
n3xc4.m8 |
Table 8. n1xc10.m48
| Component
name |
Component
profile |
| APIM |
n1xc2.m16 |
| Portal |
n1xc2.m8 |
| Analytics |
n1xc2.m16 |
| Gateway |
n1xc4.m8 |