Administration Console Online Help

Configure general JMS
server properties

After you create a JMS
server, you can define optional general properties for message paging,
specify a template to use when your applications create temporary
destinations, and a desired pausing interval between active scans of
destinations for expired messages.

To configure general configuration properties for a JMS server:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

On the
Summary of JMS Servers page, click the JMS server
you want to configure.

If necessary,
click the Configuration:General tab.

Message
paging is enabled by default, However, you can modify the default
message paging properties:

In
Message Paging Directory, specify where you
want message bodies written to when the size of the message bodies
in the JMS server exceeds the message buffer size. If unspecified,
messages are written to the /tmp directory in the
host server's directory (for example,
domain-name/servers/server-name/tmp).

In
Message Buffer Size, specify the amount of
memory (in bytes) that this JMS server can use to store message
bodies before it writes them to disk. When the JMS server writes
the message bodies to disk, it clears them from memory. The
default value of -1 specifies that the server will automatically
determine a size based on the maximum heap size of the JVM. This
default will be set to either one-third the maximum heap size, or
512 megabytes, whichever is larger.

Temporary
destinations enable an application to create a queue or topic, as
required, without the administrative overhead associated with
configuring and creating a server-defined destination. Temporary
destinations are enabled by default on this JMS server. However, if
you want to create temporary destinations with specific settings, you
need to modify the default Temporary Template values:

In Hosting Temporary Template, specify
whether this JMS server can be used to host temporary
destinations. If this field is enabled and no Temporary
Template Name is defined, then the temporary
destinations created on this JMS server will use all default
destination values. If this field is enabled, then the JMS
template to be used for creating temporary destinations is
specified in the Temporary Template Name
field. If this field is disabled, then this JMS server will not
host temporary destinations.

In
Module Containing Temporary Template,
select the JMS module that contains a template that this JMS
server can use to create temporary destinations. Entering a JMS
module name requires you to specify a valid temporary template
name. However, a module name cannot be specified if the
Hosting Temporary Destinations field is
disabled.

In
Temporary Template Name, specify the name
of an existing JMS template that this JMS server will use to
create temporary queues and topics. Entering a template name,
requires you to specify the JMS module that contains this
template. However, a template name cannot be specified if the
Hosting Temporary Destinations field is
disabled.

To define how
often a JMS server will actively scan its destinations for expired
messages, in Expiration Scan Interval, specify
the number of seconds that the JMS server should pause between its
cycles of scanning its destinations for expired messages to process
(according to the specified Expiration Policy
on the destinations). The default value is 30 seconds. A value of 0
indicates that active scanning is disabled; messages still expire, but
are cleaned up less quickly.