Use this panel to view the configuration properties of the selected JMS provider. You cannot change these properties.
Configuration tab
The level to which this resource definition is visible; the cell, node, or server level.
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 which are defined at more general scopes.
When JMS resources are created for this messaging provider, they are always created into the provider scope selected in this panel. To browse or change resources in other scopes, select the required level option, then click Apply, before clicking the link for the type of resource.
Data type | String |
The name by which the JMS provider is known for administrative purposes.
Data type | String |
Default | WebSphereJMSProvider |
A description of the JMS provider, for administrative purposes within IBM WebSphere Application Server.
Data type | String |
The Java classpath for WebSphere MQ as a JMS provider. The list of paths or JAR file names that together form the location for the JMS provider classes.
[JMS Providers > WebSphere MQ and JMS Providers > Generic only]
Data type | String |
Default | [WebSphere MQ] $MQJMS_LIB_ROOT |
The native library path for WebSphere MQ as a JMS provider. An optional path to any native libraries needed by the JMS provider.
[JMS Providers > WebSphere MQ and JMS Providers > Generic only]
Data type | String |
Default | [WebSphere MQ] $MQJMS_LIB_ROOT |
The Native Library Path property is set to the directory where the WebSphere MQ Java feature is installed.
The Java classname of the initial context factory for the JMS provider.
[JMS Providers > Generic only]
For example, for an LDAP service provider the value has the form: com.sun.jndi.ldap.LdapCtxFactory.
Data type | String |
Default | Null |
Related concepts
Using JMS interfaces to explicitly poll for messages
Related tasks
Administering support for message-driven beans