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

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

Figure 12-9 WebSphere MQ JMS Provider Queue configuration window

Chapter 12. Configuring WebSphere 249

In the Queue Destination configuration window, we specify the following

parameters for the queue:

򐂰 Scope: The scope of the Queue Destination identifies the location for the

configuration file. This value is static and depends on the server selection

made in the WebSphere MQ JMS Provider window.

򐂰 Name: The required display name for the queue destination. This name is

used when defining the queue on the JMS server.

򐂰 JNDI Name: The resource name, this name is used to locate the Queue in

the JNDI context.

򐂰 Description: An optional description for the resource.

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

the resource.

򐂰 Persistence: It specifies whether the messages sent to the destinations are

persistent, non-persistent, or defined by the application.

򐂰 Priority & Specified Priority: It defines the message priority for the

destination of the application defined or specified. 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.

򐂰 Base Queue Name: The name of the queue to which messages are sent or

received.

򐂰 Base Queue Manager Name: The name of the WebSphere MQ queue

manager where the base queue resides.

򐂰 CCSID: The coded character set identifier for use with the WebSphere MQ

queue manager.

򐂰 Native Encoding: If checked, the native encoding for the queue manager is

used. Otherwise the Integer, Decimal and Floating Point Encoding settings

will be used.

򐂰 Integer Encoding: It defines whether the integer encoding is Normal or

Reversed.

򐂰 Decimal Encoding: It defines whether the integer encoding is Normal or

Reversed.

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

򐂰 Floating Point Encoding: It defines the type of floating point encoding.

򐂰 Target Client: It defines whether the receiving application is JMS-compliant

or a traditional WebSphere MQ application.

If the connection to this queue destination is created without a queue connection

factory, the following settings are required:

򐂰 Queue Manager Host: The name of the host for the queue manager where

the queue destination is created.

򐂰 Queue Manager Port: The number of the port used by the queue manager

on which the queue is defined.

򐂰 Server Connection Channel Name: The name of the channel used to

connect to the queue manager.

򐂰 User ID: The user ID used to connect to the queue manager.

򐂰 Password: The password for this user ID.

If the WebSphere MQ Queue is a local queue, some queue settings can be

changed using the WebSphere Administration Console by clicking the

MQ

Config

link at the bottom of the Queue Destination configuration window.

Chapter 12. Configuring WebSphere 251

Figure 12-10 WebSphere MQ queue configuration window