Configuring Topic Endpoints

A topic endpoint on an event broker attracts guaranteed messages for a single topic. For general information about topic endpoints, see Topic Endpoints and Queues, and for in-depth information, see Queues.

To configure a topic endpoint, perform these steps: 

  1. Open Broker Manager. For instructions, see Using PubSub+ Broker Manager.
  2. In Broker Manager, in the left navigation bar, select Queues.
  3. Click the Topic Endpoints tab.
  4. Click + Topic Endpoint.
  5. Enter the name for the topic endpoint and click Create.
  6. Set the following options for the topic endpoint:

    Setting Description

    Incoming

    Specifies whether messages can be written to the topic endpoint.

    Outgoing

    Specifies whether messages can be consumed from the topic endpoint.

    Access Type

    Specifies how messages are delivered when multiple consumer flows are bound to the topic endpoint.

    • Exclusive specifies that only one consumer can receive a message at any one time, while additional consumers may be connected as standby. Only the first consumer to bind can receive messages. If the first consumer disconnects, the second consumer receives data, and so on. Exclusive topic endpoints always deliver messages in the order they are received.
    • Non-Exclusive specifies that multiple consumers can bind to the topic endpoint, which enables load balancing and consumer auto-scaling. Each consumer is serviced in a round-robin fashion. If a connection fails, unacknowledged messages are delivered to another consumer with the re-delivered flag set. In this way, messages can be delivered to consumers out of order.

    Messages Queued Quota

    Specifies the maximum amount of message data, in MB, that can be spooled in the topic endpoint.

    Owner

    The topic endpoint owner has full unlimited permissions for the topic endpoint. The owner can consume, delete, or modify topics in the topic endpoint. By default, users with access to PubSub+ Broker Manager have ownership privileges. You can also give ownership to client applications.

    Non-Owner Permission

    Specifies the access level given to client applications other than the topic endpoint owner:

    • No Access—Disallows all access.

    • Read Only—Read-only access to the messages.

    • Consume—Consume (read and remove) messages.

    • Modify Topic—Consume messages or modify the topic or selector.

    • Delete—Clients can consume messages, modify the topic or selector, and delete the client created endpoint altogether.

    Maximum Consumer Count

    Specifies the maximum number of consumer flows that can bind to the topic endpoint.

  7. Click Apply.