WebSphere MQ Provider queue connection factory settings
for application clients
Use this panel to view or change the configuration properties of
the selected queue connection factory for use with the MQSeries product Java
Messaging Service (JMS) provider. These configuration properties control how
connections are created to the associated JMS queue destination.
To view this Application Client Resource Configuration Tool (ACRCT) page,
click File > Open. After you browse for an EAR file, click Open.
Expand the selected JAR file > JMS Providers > JMS provider instance.
Right click MQ Queue Connection Factories, and click New. The
following fields are displayed on the General tab.
A queue connection factory creates JMS connections to queue destinations.
The queue connection factory is created by the MQSeries product JMS provider.
A queue connection factory for the JMS provider has the following properties.
Note:
- The property values that you specify must match the values that you specified
when configuring MQSeries for JMS resources. For more information about configuring
MQSeries product JMS resources, see the MQSeries Using Java book,
located in the WebSphere MQ Family library.
- In MQSeries, names can have a maximum of 48 characters, with the exception
of channels which have a maximum of 20 characters.
- Name
- The name by which this queue connection factory is known for administrative
purposes within IBM WebSphere Application Server. The name must be unique
within the JMS connection factories across the WebSphere administrative domain.
- Description
- A description of this connection factory for administrative purposes
within IBM WebSphere Application Server.
Data type |
String |
Default |
Null |
- JNDI Name
- The application client run time uses this field to retrieve configuration
information. The name must match the value of the Name field on the
General tab in the Application Client Resource Reference section of the Assembly
Tool.
- User
- The user ID used, with the Password property, for authentication
if the calling application does not provide a userid and password explicitly.
If you specify a value for the User ID property, you must also specify
a value for the Password property.
The connection factory User ID and Password properties are
used if the calling application does not provide a userid and password explicitly;
for example, if the calling application uses the method createQueueConnection().
The JMS client flows the userid and password to the JMS
server.
- Password
- The password used, with the User ID property, for authentication
if the calling application does not provide a userid and password explicitly.
If you specify a value for the User ID property, you must also specify
a value for the Password property.
Data type |
String |
Default |
Null |
- Re-Enter Password
- Confirms the password.
- Queue Manager
- The name of the MQSeries queue manager for this connection factory.
Connections created by this factory connect to that queue manager.
- Host
- The name of the host on which the WebSphere MQ queue manager runs
for client connection only.
Data type |
String |
Default |
Null |
Range |
A valid TCP/IP host name |
- Port
- The TCP/IP port number used for connection to the WebSphere MQ
queue manager, for client connection only.
This port must be configured on the WebSphere MQ queue manager.
Data type |
Integer |
Default |
Null |
Range |
A valid TCP/IP port number, configured on the WebSphere MQ queue
manager. |
- Channel
- The name of the channel used for connection to the WebSphere MQ
queue manager, for client connection only.
Data type |
String |
Default |
Null |
Range |
1 through 20 ASCII characters |
- Transport type
- Specifies whether the WebSphere MQ client connection or JNI bindings
are used for connection to the WebSphere MQ queue manager. The external JMS
provider controls the communication protocols between JMS clients and JMS
servers. Tune the transport type when you are using non-ASF nonpersistent,
nondurable, nontransactional messaging or when you want to satisfy security
issues and the client is local to the queue manager node.
Data type |
Enum |
Units |
Not applicable |
Default |
BINDINGS |
Range |
- BINDINGS
- JNI bindings are used to connect to the queue manager. BINDINGS is a shared
memory protocol and can only be used when the queue manager is on the same
node as the JMS client and poses security risks that should be addressed through
the use of EJB roles.
- CLIENT
- WebSphere MQ client connection is used to connect to the queue manager.
CLIENT is a typical TCP-based protocol.
- DIRECT
- For WebSphere MQ Event Broker using DIRECT mode. DIRECT is a lightweight
sockets protocol used in nontransactional, nondurable and nonpersistent Publish/Subscribe
messaging. DIRECT is only works for clients and message-driven beans using
the non-ASF protocol.
- QUEUED
- QUEUED is a standard TCP protocol.
|
Recommended |
- Queue connection factory transport type
- BINDINGS is faster by 30% or more, but it lacks security. When you have
security concerns, BINDINGS is more desirable than CLIENT.
- Topic connection factory transport type
- DIRECT is the fastest type and should be used where possible. Use BINDINGS
when you want to satisfy additional security tasks and the queue manager is
local to the JMS client. QUEUED is the fallback for all other cases. WebSphere
MQ 5.3 before CSD2 with the DIRECT setting can lose messages when used with
message-driven beans and under load. This loss also happens with client-side
applications unless the broker maxClientQueueSize is set to 0. You can set
this to 0 with the command:
#wempschangeproperties WAS_nodeName_server1 -e default -o DynamicSubscriptionEngine -n maxClientQueueSize -v 0 -x executionGroupUUID where executionGroupUUID can be found by starting the broker and looking
in the Event Log/Applications for event 2201. This value is usually ffffffff-0000-0000-000000000000.
|
- Client ID
- The JMS client identifier used for connections to the MQSeries
queue manager.
- CCSID
- The coded character set identifier for use with the WebSphere MQ
queue manager.
This coded character set identifier (CCSID) must be one of the CCSIDs supported
by WebSphere MQ.
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 references 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.
- Message Retention
- Select this check box to specify that unwanted messages are to
be left on the queue. Otherwise, unwanted messages are handled according to
their disposition options.
Data type |
Enum |
Units |
Not applicable |
Default |
Cleared |
Range |
- Selected
- Unwanted messages are left on the queue.
- Cleared
- Unwanted messages are handled according to their disposition options.
|
- Custom Properties
- Specifies name-value pairs for setting additional properties on
the object that is created at run time for this resource.
You must enter a name that is a public property on the object and a value
that can be converted from a string to the type required by the set method
of the property. The acceptable properties and values depend on the object
that is created. Refer to the object documentation for a list of valid properties
and values.

Tuning performance parameter index
Searchable topic ID:
ucli_pqcfm
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/ucli_pqcfm.html