+

Search Tips   |   Advanced Search

JMS provider settings

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

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

  1. 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. We can create the same type of JMS provider at different Scope settings, to offer JMS resources at different levels of visibility to applications.

  2. Optional. To manage JMS resources defined at a different scope setting, change the Scope setting to the required level.

  3. In the Providers column of the list displayed, click the name of a JMS provider.

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 WebSphere MQ messaging provider, the scope, name, and description properties are displayed for information only. We cannot change these properties.

For a third-party non-JCA provider that we 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 defined at more general scopes. For more information about the scope setting, see Scope settings.


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 WAS.

  • My JMSprovider

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

  • WebSphere MQ messaging provider

    For JMS resources to be provided by WebSphere MQ. We must have installed and configured WebSphere 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 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 the driver installation notes for specific JAR file names required.

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 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.

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

Information Value
Data type String


Enable JCA based inbound message delivery

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

This property is only available for the WebSphere MQ messaging provider, at the server scope.

When using WebSphere MQ messaging provider activation specifications on the z/OS operating system, 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 WebSphere MQ resource adapter that provides the function made available by the WebSphere 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 WebSphere MQ resource adapter.

Normally the WebSphere 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 WebSphere 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. For more information see Maintain the WebSphere MQ resource adapter.

This property is only available for the WebSphere 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.

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.

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

Information Value
Data type String
Default Null


Disable WebSphere MQ

This check box is only valid for the WebSphere MQ messaging provider. When selected, this check box disables all WebSphere 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 WebSphere MQ messaging provider panel where the scope is set to server, and has the effect of disabling all WebSphere MQ functionality in that application server.

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

The value of the check box at a higher scope takes precedence over the value at a lower scope. For example, if we do not select the check box for a WebSphere MQ messaging provider at the server scope, but do select it for a WebSphere 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 WebSphere 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 WebSphere MQ has been disabled is added to all WebSphere 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.

For more information see Disable WebSphere MQ functionality in WebSphere Application Server.

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 WebSphere MQ resource adapter, which is used by the WebSphere MQ messaging provider. In particular most of these settings affect the behavior of WebSphere MQ messaging provider activation specifications.


Related concepts

  • JMS interfaces - explicit polling for messages


    Related tasks

  • Manage messaging with the default messaging provider
  • Manage message listener resources for message-driven beans
  • Configure the WebSphere MQ messaging provider with native libraries information
  • Maintain the WebSphere MQ resource adapter
  • Disable WebSphere MQ functionality in WebSphere Application Server
  • Define a third-party non-JCA messaging provider

  • Mapping of administrative console panel names to command names and WebSphere MQ names Reference topic