For auto-created destinations, you set default property values in the broker’s instance configuration file.Reference information on auto-create properties is located in Table 14-4.
This chapter explains how to perform the following tasks: object whenever it interact with a physical destination.
For provider-independence and portability, clients typically use administrator-created destination objects, which are called destination administered objects.
You can configure administered objects for use by client applications, as described in Chapter 8, "Managing Administered Objects." You can also set properties when you update a physical destination.
A Message Queue message is routed to its consumer clients by way of a physical destination on a broker.
The broker manages the memory and persistent storage associated with the physical destinations, and sets their behaviors.
In a cluster, you create a physical destination on one broker, and the cluster propagates that physical destination to all brokers.An application client can subscribe to a topic or consume from a queue that is on any broker in the cluster, because the brokers cooperate to route messages across the cluster.Many physical destination properties manage broker memory resources and message flow.For example, you can specify the number of producers that can send to a physical destination, the number and size of the messages they can send, and the response that the broker should take when physical destination limits are reached.The limits are similar to broker-wide limits that broker configuration properties control.The following properties are used for both queue destinations and topic destinations: See Chapter 15, "Physical Destination Property Reference" for full reference information about physical destination properties.