5.3. ServerPeer methods

Used to programmatically deploy a queue. If the queue exists but is undeployed, it will be deployed. Otherwise, it is created and deployed.

The name parameter matches a destination to deploy.

The optional jndiName parameter represents the full JNDI name of the location to which a destination will be bound. If this is not specified, the destination will be bound in <DefaultQueueJNDIContext>/<name>.

There are two overloaded versions of this operation. The first deploys the destination with default paging parameters. The second deploys the destination with the paging parameters specified. For more information about paging parameters, refer to Section 5.9, “Configuring Destinations”.

Used to programmatically undeploy a queue. Queues are not removed from persistent storage. This operation returns true if the queue is successfully undeployed. Otherwise, it returns false.

Used to programmatically destroy a queue. Queues are undeployed and all of their data is removed from the database and destroyed.

This operation returns true if the queue was destroyed successfully. Otherwise, it returns false.

Used to programmatically deploy a topic. There are two overloaded versions of this operation. The first deploys already existing topics with the default paging parameters. The second creates and deploys topics with specified paging parameters. For more information about destinations, refer to Section 5.9, “Configuring Destinations”.

The name parameter represents the name of the destination to deploy.

The jndiName represents the full JNDI name of the location to which the destination will be bound. If this is not specified, the destination will be bound in <DefaultTopicJNDIContext>/<name>.

Used to programmatically undeploy a topic. Topics are undeployed, but not removed from persistent storage. This operation returns true if the topic is undeployed successfully. Otherwise, false is returned.

Used to programmatically destroy a topic. Topics are undeployed and all data is removed from the database and destroyed. This operation returns true if the topic is successfully destroyed. Otherwise, it returns false.

Returns message counters in a simply-displayed HTML format.

Resets all message counters to zero.

Enables all message counters for all destinations. Message counters are disabled by default.

Disables all message counters for all destinations. Message counters are disabled by default.

Retrieves a list of the XIDs for all transactions currently in a prepared state on the node.

Retrieves a list of the XIDs for all transactions currently in a prepared state on the node in an easily-displayed HTML format.

Displays the details of all prepared transactions.

Displays the details of all prepared transactions where the transaction ages are equal to or older than a specified time.

Displays the details of a message. The message ID is used to specify the message to display.

Manually commit a prepared transaction. The transaction ID is used to specify the transaction to commit.

Manually roll-back a prepared transaction. The transaction ID is used to specify the transaction to roll-back.