JMS provider settings


 

+

Search Tips   |   Advanced Search

 

To configure JMS provider settings...

  1. In the navigation pane, click...

    Resources | JMS | JMS providers | Scope | JMS_provider

To change JMS resources of the JMS provider, click link for type of resource under Additional Properties.

For the default WebSphere MQ messaging providers, the scope, name, and description properties are displayed for information only. We cannot change these properties.

For a third-party JMS provider that we have defined, 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...

...can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates defined at more general scopes.

Name

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

Data type String
Default

Description

A description of the JMS provider, for admin purposes within WAS.

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 using a variable map. Check the driver installation notes for specific JAR file names that are required.

Is only available for third-party messaging providers.

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 using a variable map.

Is only available for the WebSphere MQ messaging provider and third-party messaging providers.

Data type String

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

Is only available for third-party messaging providers.

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

Is only available for third-party messaging providers.

Data type String
Default Null





 

Related concepts

JMS interfaces - explicit polling for messages

 

Related tasks

Administer activation specifications and listener ports for message-driven beans
Manage messaging with the WebSphere MQ messaging provider
Define a third-party messaging provider
Maintain (deprecated) V5 default messaging resources
Manage messaging with the default messaging provider

 

Related

Mapping of admin console panel names to command names and WebSphere MQ names