This file lists common JMS-related entities for reuse in other DITA topics (through conrefs)
Specifies the level to which this resource is visible: the cell, node, or server level.
Use scope settings to limit the availability of resources to a particular cell, node, or server. When new resources are created in this view, they are created within the selected scope.
Resources such as JMS providers can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates that are defined at more general scopes.
The value you set for this check box is displayed in the Scope field on this panel.
Data type | Enum |
Default | Node |
Range |
|
Specifies the level to which this resource is visible: the cell, node, or server level.
This field displays the value that you set on the Configuration scope selection form on this panel.
Data type | Enum |
Default | Node |
Range | Cell, Node, or Server. |
The name by which this connection factory is known for administrative purpose. The name must be unique within the JMS connection factories across the WebSphere administrative domain.
Data type | String |
The JNDI name that is used to bind the connection factory into the application server's name space.
Data type | String |
A description of this connection factory for administrative purposes..
Data type | String |
Default | Null |
The WebSphere node name of the administrative node where the JMS server runs for this connection factory. Connections created by this factory connect to that JMS server.
Data type | String |
Units | Enum |
Default | Null |
Range | Pull-down list of nodes in the WebSphere administrative domain. |
This alias specifies a user ID and password to be used to authenticate connection to a JMS provider for application-managed authentication.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate the creation of a new connection to the JMS provider.
If you have enabled global security for WebSphere Application Server, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the JMS provider. The use of this alias depends on the resource authentication (res-auth) setting declared in the connection factory resource reference of an application component's deployment descriptors.
This alias specifies a user ID and password to be used to authenticate connection to a JMS provider for container-managed authentication.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate the creation of a new connection to the JMS provider.
If you have enabled global security for WebSphere Application Server, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the JMS provider. The use of this alias depends on the resource authentication (res-auth) setting declared in the connection factory resource reference of an application component's deployment descriptors.
The name of the queue manager for this connection factory. Connections created by this factory connect to that queue manager.
Data type | String |
Default | Null |
Range | A valid WebSphere MQ queue manager name, as 1 through 48 ASCII characters |
The TCP/IP port number used for connection to the queue manager, for client connection only.
This port must be configured on the queue manager.
Data type | Integer |
Default | Null |
Range | A valid TCP/IP port number, configured on the queue manager. |
The name of the channel used for connection to the queue manager, for client connection only.
Data type | String |
Default | Null |
Range | 1 through 20 ASCII characters |
The name of the model queue definition that can be used by the queue manager to create temporary queues if a queue requested does not already exist.
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
Select this tick box to specify that unwanted messages are to be left on the queue. Otherwise, unwanted messages are dealt with according to their disposition options.
Data type | Enum |
Units | Not applicable |
Default | Cleared |
Range |
|
Specifies whether the connection factory is for XA or non-XA coordination of messages and controls if the application server uses XA QCF/TCF. Enable XA if multiple resources are not used in the same transaction.
If you set this property to NON_XA, the JMS session is still enlisted in a transaction, but uses the resource manager local transaction calls (session.commit and session.rollback) instead of XA calls. This can lead to an improvement in performance. However, this means that only a single resource can be enlisted in a transaction in WebSphere Application Server. In WebSphere Application Server Enterprise the last participant support enables you to enlist one non-XA resource with other XA-capable resources.
For a WebSphere Topic Connection Factory with the Port property set to DIRECT this property does not apply, and always takes the value NON_XA.
Data type | Enum |
Units | Not applicable |
Default | XA enabled |
Range |
|
Recommended | Do not enable XA when the message queue or topic received is the only resource in the transaction. Enable XA when other resources, including other queues or topics, are involved. |
The name of the host on which the queue manager runs, for client connection only.
Data type | String |
Default | Null |
Range | A valid TCP/IP hostname |
Which of the two ports that connections use to connect to the JMS Server. The QUEUED port is for full-function JMS publish/subscribe support, the DIRECT port is for non-persistent, non-transactional, non-durable subscriptions only.
Data type | Enum |
Units | Not applicable |
Default | QUEUED |
Range |
The TCP/IP port numbers for these ports are defined on the JMS Server. |
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 |
|
Recommended |
|
The JMS client identifier used for connections to the queue manager.
This client ID is used if the application does not use the Connection.setClientID(String) method to specify a client ID.
Data type | String |
Default | Null |
Select this checkbox to enable clone support to allow the same durable subscription across topic clones.
Data type | Enum |
Units | Not applicable |
Default | Cleared |
Range |
|
If you select this property, you must also specify a value for the Client ID property.
The name of the model queue definition that the broker can use to create dynamic queues for non-default streams if the stream queue does not already exist
The name of the model queue definition that the broker can use to create dynamic queues to receive publications for streams other than the default stream. This is only used if the stream queue does not already exist. If this model queue definition does not exist, all stream queues must be defined by the administrator.
Data type | String |
Units | En_US ASCII characters |
Default | Null |
Range | 1 through 48 ASCII characters |
The name of the cell to which applications should be connected.
This does not have to be the same as the cell in which the application is deployed.
For thin clients this field must be specified. For other usage, this field is optional and, if left to default, the name of the home cell is used.
Data type | String |
Default | home cell name |
The name of the message bus to which applications should be connected.
This name is qualified by the cell name.
Data type | String |
Default | Null |
The name of a pre-configured channel chain used to communicate with the messaging engine.
Data type | String |
Default | Null |
The name used to identify the WLM target group that refines where applications should be connected.
This name is qualified by the cell name and, if needed, bus name. For an application server or server cluster, the cell name is enough, because their WLM target group namespace is at the cell level. For messaging engine, messaging engine group, and destination, the name is qualified by both the cell and bus names.
For example, if Target name specifies the name of a destination and Target significance is set to Preferred, then the createConnection() method tries to connect to a messaging engine that localizes the named destination. If the connection cannot be completed (for example, because no such messaging engines are running), then an attempt is made to connect to some other messaging engine that is available on the same bus.
To make a specific connection, set Target significance to Critical. This forces the createConnection() method to try to connect to the target identified by the Target name property; for example, a specific messaging engine or application server, or the name of a destination with only one localization. In this critical case, if there is no available messaging engine that hosts the target, then the connection fails.
Data type | String |
Default | Null If the Target name value is not specified, applications are connected to any available messaging engine on the identified bus. |
Whether the WLM target group name is critical or only helpful to lookup the target.
Data type | Enum |
Default | Preferred |
Value |
|
The name of the messaging engine where all durable subscriptions accessed through this connection are managed.
This property must be set if durable subscriptions are to be created using connections created from this connection factory.
Data type | Enum |
Default | Null |
Range | A list of messaging engines available. |
The acceptable reliability for message delivery, as a quality of service, for non-persistent JMS messages.
This property can also be set on the JMS destination, in which case the JMS destination setting overrides this value.
Data type | Integer |
Default | Express |
Range |
|
Indicates that the client/server protocol must be protected by SSL (in the case of HTTP tunnelling this means that the protocol will be HTTPS), and specifies the SSL cipherSuite to be used.
Set this property to a valid cipher suite provided by your JSSE provider; it must match the CipherSpec named on the SVRCONN channel named by the Channel property.
You must set this property if the SSL Peer Name is to be set.
For SSL, an X.509 distinguished name skeleton that must match the name provided by the bus. The distinguished name is used to check the identifying certificate presented by the server at connect-time.
If SSL Peer Name and SSL Ciphersuite are set, then a certificate is requested from the server, and the server's distinguished name is checked against the value provided here
SSL Peer Name is ignored if SSL Ciphersuite is not specified.
CN=QMGR.*, OU=IBM, OU=WEBSPHERE
The example given checks the identifying certificate presented by the server at connect-time. For the connection to succeed, the certificate must have a Common Name beginning QMGR., and must have at least two Organizational Unit names, the first of which is IBM and the second WEBSPHERE. Checking is not case-sensitive.
For an HTTP transport, this defines the URL of an HTTP proxy server.
If the Transport property is set to HTTP this field can be set to the URL of an HTTP proxy server. If Transport is not set to HTTP, then this field is ignored
Data type | URL |
Default | Null |
Range | A valid HTTP URL value. |
The name of the model destination that the connection factory can use to create temporary destinations.
Data type | String |
Range |
A prefix that is used when generating temporary destinations from this connection factory, so that the temporary destinations can be easily associated with the application that created them.
Data type | String |
Range |
The default namespace within which JMS destinations are referenced if the associated destination does not specify a namespace.
Data type | String |
Range |
The default namespace within which this JMS destination is referenced.
If you do not specify a value for this property, the destination is referenced within the namespace specified for the connection factory.
Data type | String |
Range |
The destination on the service integration bus that provides this JMS destination.
Data type | Enum |
Range |
The topic on the service integration bus that provides this JMS topic destination.
Data type | Enum |
Range | A name of an SIB topic defined within a topicspace on the service integration bus. |
A comma-separated list of bus destinations that a message should pass through after it has been delivered to the bus destination to which the producer is attached.
Data type | String |
Range | A comma-separated list of bus destination names; for example:sidestnA, sidestnB, sidestnC |
The acceptable reliability for message delivery, as a quality of service, for non-persistent JMS messages.
If you do not specify a value for this property, the destination uses the quality of service specified for the connection factory.
Data type | Integer |
Default | Express |
Range |
|
The time in milliseconds before messages on this destination expire.
Data type | Integer |
Default | 0 |
Range |
The name of a mediation to be applied when this JMS destination is being used as a message producer
Data type | String |
Default | Null |
The name of a mediation to be applied when this JMS destination is being used as a message consumer
Data type | String |
Default | Null |
The JNDI name that is used to bind the queue into the application server's name space.
Data type | String |
The JNDI name that is used to bind the topic into the application server's name space.
Data type | String |
A description of the resource, for administrative purposes.
Data type | String |
Default | Null |
A category used to classify or group this resource, for your administrative records.
Data type | String |
Default | Null |
The JNDI name that is used to bind the resource into the name space.
Data type | String |
Whether all messages sent to the destination are persistent, non-persistent, or have their persistence defined by the application.
Whether the message priority for this destination is defined by the application or the Specified priority property
If the Priority property is set to Specified, type here the message priority for this queue, in the range 0 (lowest) through 9 (highest)
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) |
Whether the expiry timeout for this destination is defined by the application or the Specified expiry property, or messages on the destination never expire (have an unlimited expiry timeout)
If the Expiry timeout property is set to Specified, type here the number of milliseconds (greater than 0) after which messages on this queue expire
Data type | Integer |
Units | Milliseconds |
Default | Null |
Range | Greater than or equal to 0
|
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.
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.
Specifies an optional set of connection pool settings.
Connection pool properties are common to all J2C connectors.
The application server pools connections and sessions with the JMS provider to improve performance. This is independent from any WebSphere MQ connection pooling. You need to configure the connection and session pool properties appropriately for your applications, otherwise you may not get the connection and session behavior that you want.
Change the size of the connection pool if concurrent server-side access to the JMS resource exceeds the default value.The size of the connection pool is set on a per queue or topic basis. See the following table for details.
An optional set of session pool settings.
This link provides a panel of optional connection pool properties, common to all J2C connectors.
The application server pools connections and sessions with the JMS provider to improve performance. This is independent from any WebSphere MQ connection pooling. You need to configure the connection and session pool properties appropriately for your applications, otherwise you may not get the connection and session behavior that you want.