Use this panel to view or change the configuration properties of the selected queue destination for use with the WebSphere MQ JMS provider.
A queue destination is used to configure the properties of a JMS queue. Connections to the queue are created by the associated queue connection factory for the WebSphere MQ JMS provider. A queue for use with the WebSphere MQ JMS provider has the following properties.
Note:
To view this administrative console page, click Resources-> WebSphere MQ JMS Provider-> (In content pane, under Additional Properties) WebSphere MQ Queue Destinations-> destination_name
Data type | String |
As a convention, use the fully qualified JNDI name; for example, in the form jms/Name, where Name is the logical name of the resource.
This name is used to link the platform binding information. The binding associates the resources defined by the deployment descriptor of the module to the actual (physical) resources bound into JNDI by the platform.
Data type | String |
Data type | String |
Default | Null |
Data type | String |
Data type | Enum |
Units | Not applicable |
Default | APPLICATION_DEFINED |
Range |
|
Data type | Enum |
Units | Not applicable |
Default | APPLICATION_DEFINED |
Range |
|
If the Priority property is set to Specified, messages sent to this queue have the priority value specified by this property.
Data type | Integer |
Units | Message priority level |
Default | Null |
Range | 0 (lowest priority) through 9 (highest priority) |
Data type | Enum |
Units | Not applicable |
Default | APPLICATION_DEFINED |
Range |
|
Data type | Integer |
Units | Milliseconds |
Default | Null |
Range | Greater than or equal to 0
|
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
This queue manager provides the queue specified by the Base queue name property.
Data type | String |
Units | En_US ASCII characters |
Default | Null |
Range | A valid WebSphere MQ Queue Manager name, as 1 through 48 ASCII characters |
This coded character set identifier (CCSID) must be one of the CCSIDs supported by WebSphere MQ.
Data type | String |
Units | Integer |
Default | Null |
Range | 1 through 65535 |
For more information about supported CCSIDs, and about converting between
message data from one coded character set to another, see the WebSphere
MQ System Administration and the WebSphere MQ Application Programming
Reference books. These are available from the WebSphere MQ messaging
multiplatform and platform-specific books Web pages; for example, at
http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html
,
the
IBM Publications Center
,
or from the WebSphere MQ collection kit, SK2T-0730.
Data type | Enum |
Units | Not applicable |
Default | Cleared |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
Data type | Enum |
Units | Not applicable |
Default | NORMAL |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
Data type | Enum |
Units | Not applicable |
Default | NORMAL |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
Data type | Enum |
Units | Not applicable |
Default | IEEENORMAL |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
Data type | Enum |
Units | Not applicable |
Default | MQSeries |
Range |
|
Data type | String |
Default | Null |
Range | A valid TCP/IP hostname |
Data type | String |
Units | A valid TCP/IP port number. |
Default | Null |
Range | A valid TCP/IP port number. This port must be configured on the WebSphere MQ queue manager. |
Data type | String |
Default | Null |
Range | 1 through 20 ASCII characters |
If you specify a value for the User name property, you must also specify a value for the Password property.
Data type | String |
Default | Null |
If you specify a value for the User name property, you must also specify a value for the Password property.
Data type | String |
Default | Null |
Configuration tab
Resources such as JMS Providers, Namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates which are defined at more general scopes.
Note that no matter what the scope of a defined resource, the resource's properties only apply at an individual server level. For example, if you define the scope of a data source at the Cell level, all users in that Cell can look up and use that data source, which is unique within that Cell. However, resource property settings are local to each server in the Cell. For example, if you set Max Connections to 10, then each server in that Cell can have 10 connections.
When resources are created, they are always created into the current scope selected in the panel. To view resources in other scopes, specify a different node or server in the scope selection form.
Data type | String |