The Application Invoker job invokes a static JMS application which name must be specified as a job parameter. It requires that the static JMS application has a shutdown method defined, otherwise the job cannot stop it. Either the JMS application must have the attribute "main-return-is-stop" set to true (SwiftMQ 5.0.0 and above) or a maxmimum run time must be specified in the schedule, otherwise the job runs forever.
The implementation of the Application Invoker job is quite simple. It sets the "enabled" attribute to "true" on job start and to "false" on job stop. Therefore, a static JMS application which should run as a job should be disabled initially.
| Parameter | Mandatory | Description |
|---|---|---|
| Application Name | Yes | Name of the static JMS application. |
The Queue Cleanup job removes expired messages from queues. The queues are determined from a single parameter which contains a SQL-Like predicate. For example, a predicate of "tmp$%" performs a cleanup on all temporary queues, "rt$%" on all routing queues, "test%" on all queues starting with "test" like testqueue and so on. The Queue Cleanup job provides more flexibility than to use the interval-based cleanup processes. Keep in mind that you should set the cleanup intervals (default or per queue) to 0 if you use the Queue Cleanup job.
| Parameter | Mandatory | Description |
|---|---|---|
| Queue Name Predicate | Yes | SQL-Like predicate to select queue names |
This job works like the Queue Cleanup job except that it moves expired messages to the router's deadletter queue "routerdlq" for further processing.
| Parameter | Mandatory | Description |
|---|---|---|
| Queue Name Predicate | Yes | SQL-Like predicate to select queue names |
The Queue Mover job moves messages from a source queue to a target queue. The target queue may reside on a remote router. An optional message selector can be specified to select messages on base of JMS properties out of the source queue. This job is excellent for tasks like end of day processing to move all unprocessed messages to a queue on another router for further processing.
| Parameter | Mandatory | Description |
|---|---|---|
| Source Queue | Yes | Name of the source queue |
| Target Queue | Yes | Name of the target queue |
| Message Selector | No | Optional SQL92 message selector |
The Queue Purger job removes messages from a single queue, optionally based on a message selector.
| Parameter | Mandatory | Description |
|---|---|---|
| Queue Name | Yes | Queue name |
| Message Selector | No | Optional SQL92 message selector |
The Multi Queue Purger job removes messages from multiple queues, optionally based on a message selector. Use this job carefully!
| Parameter | Mandatory | Description |
|---|---|---|
| Queue Name Predicate | Yes | SQL-Like predicate to select queue names |
| Message Selector | No | Optional SQL92 message selector |
The Delete Durable job deletes durable subscribers (incl. all messages) which are selected by 2 SQL-Like predicates, client id and durable name, specified as job parameters. For example, a client id predicate of "sales" and a durable name predicate of "%" will delete all durable subscribers of client id "sales" whereas a client id predicate of "s__es%" and a durable name predicate of "dur%" will delete those from "saukesta" and "dur2003". If you set both parameters to "%", it will match all durable subscribers and therefore all durable subscribers are deleted.
| Parameter | Mandatory | Description |
|---|---|---|
| Client Id Predicate | Yes | SQL-Like predicate for client ids. |
| Durable Name Predicate | Yes | SQL-Like predicate for durable names. |
This job takes the name of the routing connector as parameter. It enables the connector at job start and disables it at job stop. Therefore, a connector should be configured as being disabled if it should be used in a job:
Example:
<connectors>
<connector name="acme"
enabled="false"
hostname="chb.acme.com"
port="17884"
socketfactory-class="com.swiftmq.net.JSSESocketFactory"
password="let_me_in"
retry-time="120000"/>
</connectors>
The "Routing Connector" should have a specified maximum runtime in its schedule, otherwise it will not be disabled. If the connector will be enabled during job start and the connection cannot be established, the retry behavior will be executed as described in the section above. Retry ends at job stop.
This job can be used to schedule a backup at a specific time of a day. It has no parameters.
This job can be used to schedule a shrink of the data store at a specific time of a day. It has no parameters.
The Outbound Bridge job activates an outbound bridge on job start and deactivates it on job stop. The name of the bridge must be specified as parameter. The job requires to set a maximum runtime to deactivate the bridge. Otherwise it would be active forever.
The implementation of the Outbound Bridge job is quite simple. It sets the "enabled" attribute to "true" on job start and to "false" on job stop. Therefore, an outbound bridge which should run as a job should be disabled initially.
| Parameter | Mandatory | Description |
|---|---|---|
| Bridge Name | Yes | Name of the outbound bridge. |
The Inbound Bridge job activates an inbound bridge on job start and deactivates it on job stop. The name of the bridge must be specified as parameter. The job requires to set a maximum runtime to deactivate the bridge. Otherwise it would be active forever.
The implementation of the Inbound Bridge job is quite simple. It sets the "enabled" attribute to "true" on job start and to "false" on job stop. Therefore, an inbound bridge which should run as a job should be disabled initially.
| Parameter | Mandatory | Description |
|---|---|---|
| Bridge Name | Yes | Name of the inbound bridge. |
The Server Bridge job activates server bridge on job start and deactivates it on job stop. The name of the bridge must be specified as parameter. The job requires to set a maximum runtime to deactivate the bridge. Otherwise it would be active forever.
The implementation of the Server Bridge job is quite simple. It sets the "enabled" attribute to "true" on job start and to "false" on job stop. Therefore, a server bridge which should run as a job should be disabled initially.
| Parameter | Mandatory | Description |
|---|---|---|
| Bridge Name | Yes | Name of the server bridge. |