Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator

242 Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator

– Description: An optional description for the resource.

–

Category: An optional category string that can be used to classify or

group the resource.

–

Persistence: This parameter lets you specify whether the messages sent

to the destinations are persistent, non-persistent, or defined by the

application.

–

Priority & Specified Priority: This defines the message priority for the

destination if the application is defined or specified. In the last case, the

Specified Priority parameter must be a number in the range 0 through 9,

where 0 is the lowest priority and 9 the highest priority.

–

Expiry & Specified Expiry: This defines the conditions when a message

sent to this destination will expire. It accepts three possible values:

• Application defined: the JMS client will be responsible for specifying

the expiry conditions for every message sent to this destination.

• Unlimited: messages to this destination will not expire.

• Specified: messages to this destination will expire after the amount of

milliseconds specified in the Specified Expiry parameter.

12.2.3 Define the queue for the JMS server

The following steps show the queue definition for the embedded JMS server in

WebSphere V5:

1. Start the WebSphere Administrative Console and log in.

2. Queues (as well as topics) are finally defined in the JMS server component.

To define the queue, click

Servers -> Application Servers.

3. Select the server you want to create the queue for, for example select

server1.

4. Click the

Server Components link.

5. Select the

JMS Server component.

6. On the following window, list the queue names you want to use with the JMS

server.