Changing deployment profiles on OpenShift

You can change an API Connect installation to use different deployment profiles.

Before you begin

This task assumes that you have already deployed an API Connect cluster as explained in Deploying on OpenShift and Cloud Pak for Integration. If you are changing from a development profile to a production profile, ensure that you have production profile hardware (3 nodes) available.

About this task

Important considerations:

While it is possible to use a non-production profile installation in a production deployment, it is not recommended.
Based on the resources configured for each microservice in the profile, there might be downtime during the profile change.
For a list of supported profiles, see the "Deployment profiles" section in Basic configuration settings.
If you enabled the analytics message queue feature, you must disable it before changing to another deployment profile. You can re-enable the message queue feature after the profile change is complete.
To disable the message queue:
1. Edit the top-level APIConnectCluster CR.
2. In the spec.analytics section, locate the mq subsection and change the enabled setting to false.
```
spec:
    analytics:
      mq:
        enabled: false
```
3. Save and apply the change.
To re-enable the message queue:
1. Edit the top-level APIConnectCluster CR.
2. In the spec.analytics section, locate the mq subsection and change the enabled setting to true.
3. Save and apply the change.

Procedure

Verify that the API Connect cluster is in the Ready state by running the following command:
```
oc get apiconnectcluster -n <APIC_namespace>
```
Update the API Connect Cluster CR:
1. Open the API Connect Cluster CR in edit mode by running the following command:
```
oc edit apiconnectcluster <APIC-instance-name> -n <APIC_namespace>
```
2. In the CR, change the spec.profile value to the profile that you want to use.
  
  For example, to switch from the development profile to the production profile, change n3xc4.m16 to n12xc4.m12.
3. Save the change by running the following command: :wq
Wait for microservice to scale up, or scale down, as needed.
Verify that the API Connect cluster is in the Ready state by running the following command:
```
oc get apiconnectcluster -n <APIC_namespace>
```