Main - Broker - Queue
Allows an existing queue to bind to an existing exchange. Select one or more exchanges from the list and enter the exchange key and other required information. Each exchange type has different required information.
The exchanges listed default to all available exchanges. To view only "Active" exchanges, select the Active option above the list.
Allows the creation of a new queue and optionally allows binding to an existing exchange. A new queue requires a name and has several attributes:
Optionally, a queue can be bound to one or more exchanges. Select an exchange from the list and enter the exchange key and other required information. Each exchange type has different required information.
The exchanges listed default to all available exchanges. To view only "Active" exchanges, select the Active option above the list.
Allows the creation of a new exchange. An exchange name is required. Choose one of the exchange types listed.
Allows the creation of a new link between brokers. An broker address is required. It can be an IP address or a host name. A port, username and password are optional. If a port is entered, it must be a numeric value.
A durable link survives after a broker is restarted.
Closes the links between the current broker and all selected brokers. If a linked broker has link routes (also known as bridges), they will be abandoned.
Adds a Route to an existing Broker Link. Messages are exchanged with a linked broker based on Routes. A Route requires an exchange and a routing key.
Optionally, a tag and exclude list can be supplied.
Closes and deletes a route between the current broker and a linked broker.
There are three types of job attributes that can be edited:
If a non-numeric value is entered in a numeric field, the
surrounding box changes to red dashes and an error message is displayed.
A blank value in a numeric field is considered an error.
If the initial value of a text field is longer than forty characters, a larger input box is provided.
The following actions can be performed on a job:
When any of these actions are performed on a job group, the action is performed on all the jobs in the group.
Change the maximum number of jobs that can be run concurrently using a limiter.
A Limiter is a resource that must be allocated to a job before the job can run.