Adding a message queue

Update the analytics-extra-values.yaml file to enable a message queue and increase reliability in the analytics data pipeline in your IBM® API Connect Analytics deployment.

Before you begin

This task is only needed if you do not want to enable the message queue using the default values:
  • storageClassName set to local-storage
  • volumeSize set to 5Gi
If you want to use the default values, skip this task.

About this task

For information about using a message queue in your Analytics deployment, see Planning to add a message queue.

Procedure

  1. Open the analytics-extra-values.yaml file for editing.
  2. Add the mq section to the file as shown in the following example:
    mq:
      enabled: true
      kafka:
        volumeClaimTemplate:
          storageClassName: $STORAGE_CLASS
      zk:
        volumeClaimTemplate:
          storageClassName: $STORAGE_CLASS

    where $STORAGE_CLASS is the Kubernetes storage class to be used for persistent volume claims (for more information, see Planning the Analytics profile and storage).

  3. Save the file.
  4. Optional: If you want to increase the message size limit for the message queue, see Overriding size limits for message queue on VMware.

What to do next

If you do not want to add any more configuration options, skip to the topic on Defining your internal storage space, which is the last step before running the installation.

Otherwise, continue adding configuration options to the file as explained in the following topics.