Use this panel to view the configuration properties of a selected 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 WebSphere® 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.
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. For more information about the scope setting, see Scope settings.
The name by which the JMS provider is known for administrative purposes.
Data type | String |
Default |
|
A description of the JMS provider, for administrative purposes within WebSphere Application Server.
Data type | String |
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.
This property is only available for third-party messaging providers.
Data type | String |
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.
This property is only available for the WebSphere MQ messaging provider and third-party messaging providers.
Data type | String |
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, you must enable the control region adjunct process to allow messages to be delivered. Selecting this option starts the control region adjunct process on the next server restart.
Data type | Check box |
Default | Cleared |
Range |
|
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 adaptor configuration. For more information see Maintaining the WebSphere MQ JCA resource adapter.
This property is only available for the WebSphere MQ messaging provider.
Data type | Button |
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.
Data type | String |
Default | Null |
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.
Data type | String |
Default | Null |