# queues.conf

This file defines all queues.

The format of the file is:

    [jndi-name1, jndi-name2, ...]queue-name property1, property2, ...

Note: Note that, while including JNDI names is optional, the square brackets [ ] must be included around JNDI names if they are included. For more information about setting JNDI names, see `create jndiname`.

For example, you might enter:

    test store=mystore,secure,prefetch=2

Only queues listed in this file or queues with names that match the queues listed in this file can be created by the applications (unless otherwise permitted by an entry in `acl.conf`). For example, if queue `foo.*` is listed in this file, queues `foo.bar` and `foo.baz` can be created by the application.

Properties of the queue are inherited by all static and dynamic queues with matching names. For example, if `test.*` has the property `secure`, then `test.1` and `test.foo` are also secure. For information on properties that can be assigned to queues, see Destination Properties.

For further information on the inheritance of queue properties, refer to Wildcards * and > and Inheritance of Properties.

Note: In the sample file, a > wildcard at the beginning of the file allows the applications to create valid queues with any name. A > at the beginning of the queue configuration file means that name-matching is not required for creation of queues.

Restrictions and rules on queue names are described in Destination Name Syntax.

Copyright © Cloud Software Group, Inc. All rights reserved.