Deploying a Messaging server by using the CLI

Use the CLI to deploy a Messaging server, which is an instance type that supports a tailored set of messaging use cases. For more information about Messaging servers, see Using a Messaging server.

Procedure

  1. Log into your OpenShift cluster with your OpenShift user credentials:

    oc login
  2. Create a messagingserver.yaml file. Update the following values:

    • spec.license.accept - set as true if you accept the Cloud Pak for Integration license agreement. For more information, see Licensing.

    • spec.queueManager.storage.defaultClass - configure the storage class. Replace <RWO_STORAGE_CLASS> with a block storage class that supports ReadWriteOnce (RWO) volumes. For more information, see Storage considerations.

    • Any other configuration values as needed.

      apiVersion: integration.ibm.com/v1beta1
      kind: MessagingServer
      metadata:
        name: messagingserver
      spec:
        license:
          accept: false
          license: L-VEMB-RABZSN
          use: CloudPakForIntegrationNonProduction
        queueManager:
          storage:
            defaultClass: <RWO_STORAGE_CLASS>
        version: 16.2.0
  3. Apply the YAML file to the OpenShift cluster:

    oc apply -f messagingserver.yaml
  4. Confirm the status of the messaging server by running the following command:

    oc get messagingserver

    The status is Pending until deployment is complete, at which point the status changes to Ready.

What to do next

Use the Messaging server to create and configure channels, queues, and users. For more information, see Using a Messaging server.