JMS provider settings

Use this page to view the configuration properties of a selected JMS provider.

To view this page, use the administrative console to complete the following steps:

In the navigation pane, click Resources > JMS->JMS providers. This displays a list of JMS providers in the content pane. For each JMS provider in the list, the entry indicates the scope level at which JMS resource definitions are visible to applications. You can create the same type of JMS provider at different Scope settings, to offer JMS resources at different levels of visibility to applications.
(optional) If you want to manage JMS resources that are defined at a different scope setting, change the Scope setting to the required level.
In the Providers column of the list displayed, click the name of a JMS provider.

If you want to browse or change JMS resources of the JMS provider, click the link for the type of resource under Additional Properties. For more information about the administrative console panels for the types of JMS resources, see the related topics.

For the default messaging provider (which is based on service integration technologies) and the IBM MQ messaging provider, the scope, name, and description properties are displayed for information only. You cannot change these properties.

For a third-party non-JCA provider that you have defined yourself, the properties of that provider are displayed.

Scope

The level (cell, node, or server level) at which this resource definition is available.

Resources such as messaging providers, namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates that are defined at more general scopes.

Name

The name by which the JMS provider is known for administrative purposes.

Information

Value

Data type

String

Default

Default messaging provider.
For JMS resources to be provided by a service integration bus, as part of WebSphere® Application Server.
My JMSprovider
For JMS resources to be provided by a third-party JMS provider that you specify, rather than by the default messaging provider or the IBM MQ messaging provider that are available as part of WebSphere Application Server. You assign the name, for example My JMSprovider, when you define the third-party JMS provider to WebSphere Application Server. You must also have installed and configured the third-party JMS provider before applications can use its JMS resources.
IBM MQ messaging provider
For JMS resources to be provided by IBM MQ. You must have installed and configured IBM MQ before applications can use its JMS resources.

Description

A description of the JMS provider, for administrative purposes within WebSphere Application Server.

Information	Value
Data type	String

Classpath

A list of paths or JAR file names that together form the location for the JMS provider classes. Each class path entry is on a separate line (separated by using the Enter key) and must not contain path separator characters (such as ';' or ': '). Class paths can contain variable (symbolic) names to be substituted by using a variable map. Check your driver installation notes for specific JAR file names that are required.

Note: This property is only available for third-party messaging providers.

Information	Value
Data type	String

Native library path

An optional path to any native libraries (*.dll, *.so). Each native path entry is on a separate line (separated by using the Enter key) and must not contain path separator characters (such as ';' or ': '). Native paths can contain variable (symbolic) names to be substituted by using a variable map.

Note: This property is only available for the IBM MQ messaging provider and third-party messaging providers.

Information	Value
Data type	String

Enable JCA based inbound message delivery

Specifies that IBM MQ messaging provider will support inbound delivering of messages using the JCA defined interfaces.

Note: This property is only available for the IBM MQ messaging provider, at the server scope.

When using IBM MQ messaging provider activation specifications on the z/OS® operating system, you must enable the control region adjunct (CRA) process to allow messages to be delivered. Selecting this option starts the control region adjunct process on the next server restart.

Information	Value
Data type	Check box
Default	Cleared
Range	Cleared Do not start the control region adjunct process. Selected Start the control region adjunct process.

Update resource adapter

This button can be used to update the IBM MQ resource adapter that provides the function made available by the IBM MQ messaging provider. This button must only be used as directed by a member of IBM service, otherwise it may result in the use of an unsupported level of the IBM MQ resource adapter.

Normally the IBM MQ resource adapter is automatically updated by applying WebSphere Application Server fix packs. It is important to note that use of the Update resource adapter button prevents these automatic updates from happening for future fix packs for any node on which the button is used. If, in the future, you require the IBM MQ resource adapter used by the node to receive updates when a fix pack is applied then you must re-establish the recommended resource adapter configuration.

Note: This property is only available for the IBM MQ messaging provider.

Information	Value
Data type	Button

External initial context factory

The Java™ classname of the initial context factory for the JMS provider.

For example, for an LDAP service provider the value has the form: com.sun.jndi.ldap.LdapCtxFactory.

Note: This property is only available for third-party messaging providers.

Information	Value
Data type	String
Default	Null

External provider URL

The JMS provider URL for external JNDI lookups.

For example, an LDAP URL for a messaging provider has the form: ldap://hostname.company.com/contextName.

Note: This property is only available for third-party messaging providers.

Information	Value
Data type	String
Default	Null

Disable IBM MQ

This check box is only valid for the IBM MQ messaging provider. When selected, this check box disables all IBM MQ functionality on affected application servers. Note that you must restart the affected application server processes for this change to take effect.

In a single server environment this check box is only available on the IBM MQ messaging provider panel where the scope is set to server, and has the effect of disabling all IBM MQ functionality in that application server.

In a network deployment environment this check box is available on all IBM MQ messaging provider panels. The effect of selecting the check box depends on the scope at which you select it:

At the cell scope, all IBM MQ functionality is disabled on all application servers in the cell.
At the node scope, all IBM MQ functionality is disabled on all application servers that are part of that node.
At the cluster scope, all IBM MQ functionality is disabled on all application servers in that cluster.
At the server scope, all IBM MQ functionality is disabled in that particular application server.

The value of the check box at a higher scope takes precedence over the value at a lower scope. For example, if you do not select the check box for an IBM MQ messaging provider at the server scope, but do select it for a IBM MQ messaging provider at a higher scope (such as the cell scope), the value of the check box at the cell scope takes precedence and IBM MQ functionality is therefore disabled in all application servers in the cell, regardless of whether the check box is selected at the server scope.

An informational message indicating that IBM MQ has been disabled is added to all IBM MQ messaging provider panels that are at affected scopes, but this message does not appear on those panels where the check box is selected. In a single server environment this informational message is only displayed after a server restart is performed. In a network deployment environment the informational message is displayed immediately.

Information	Value
Data type	Check box
Default	Not selected

Additional properties

Connection factories: A connection factory is used to create connections to the associated JMS provider. These connection factories can be used for accessing JMS Queue and JMS Topic destinations.
Queue connection factories: A queue connection factory is used to create connections to the associated JMS provider of the JMS queue destinations, for point-to-point messaging.
Topic connection factories: A topic connection factory is used to create connections to the associated JMS provider of JMS topic destinations, for publish and subscribe messaging.
Queues: A JMS queue is used as a destination for point-to-point messaging.
Topics: A JMS topic is used as a destination for publish/subscribe messaging.
Activation specifications: A JMS activation specification is associated with one or more message-driven beans and provides configuration necessary for them to receive messages.
Resource adapter properties: These properties are used to configure the IBM MQ resource adapter, which is used by the IBM MQ messaging provider. In particular most of these settings affect the behavior of IBM MQ messaging provider activation specifications.