Configure resources for the default messaging provider
Use the following tasks to configure JMS connection factories, activation specifications, and destinations for the default messaging provider.
Use these tasks to configure administrative JMS resources provided by the default messaging provider.
These administrative JMS resources are in addition to any temporary JMS destinations created by applications.
- List JMS resources.
- Configure a unified connection factory.
- Configure a queue connection factory.
- Configure a topic connection factory.
- Configure a queue.
- Configure a topic.
- Configure an activation specification.
Subtopics
- Listing JMS resources for the default messaging provider
Use the WAS console to list JMS resources for the default messaging provider, for administrative purposes.
- Configure JMS resources for point-to-point messaging
Configure connection factories, queues and service integration bus destinations for point-to-point messaging.
- Configure JMS resources for publish/subscribe messaging
Use this task to configure a JMS resources for publish/subscribe messaging.
- Configure a unified connection factory for the default messaging provider
Use this task to configure a unified JMS connection factory for applications that use the JMS 1.1 domain-independent (unified) interfaces.
- Configure a queue connection factory for the default messaging provider
Use this task to configure a JMS queue connection factory for point-to-point messaging with the default messaging provider. This is intended more for backwards compatibility, as described in section 1.5 of the JMS 1.1 specification.
- Configure a topic connection factory for the default messaging provider
Use this task to configure a JMS topic connection factory for publish/subscribe messaging with the default messaging provider. This is intended more for backwards compatibility, as described in section 1.5 of the JMS 1.1 specification.
- Configure a queue for the default messaging provider
Use this task to configure a JMS queue for point-to-point messaging with the default messaging provider.
- Configure a topic for the default messaging provider
Use this task to configure a JMS topic for publish/subscribe messaging with the default messaging provider.
- Configure an activation specification for the default messaging provider
Configure a JMS activation specification to enable a message-driven bean to communicate with the default messaging provider.
- Delete JMS resources for the default messaging provider
Use this task with the WAS console to delete JMS resources.
- Configure JMS connection factory properties for durable subscriptions
Use this task to configure durable subscription properties of JMS connection factories for use by enterprise beans with the default messaging provider.
- Configure JMS activation specification properties for durable subscriptions
Use this task to configure durable subscription properties of JMS activation specifications for use by message-driven beans with the default messaging provider.
- Enable a provider to stream messages to cloned durable subscriptions
Use this task to enable a provider to stream messages to consumers ahead of their message requests. This is most often used by publish/subscribe consumers to provide a performance enhancement.
- Enable CMP entity beans and messaging engine data stores to share database connections
Use this task to enable container-managed persistence (CMP) entity beans to share the database connections used by the data store of a messaging engine. Performing this task has been estimated to provide a potential performance improvement of 15% for overall message throughput, but can only be used for entity beans connected to the application server containing the messaging engine.
- Configure a connection to a non-default bootstrap server
A bootstrap server is an application server running in the same cell, specifically the same core group, as the service integration bus.
- Protecting an MDB or SCA application from system resource problems
We can configure the system so that if there is a problem with a dependent external system resource, the enterprise application is stopped before messages are moved unnecessarily to an exception destination. This configuration also handles occasional problems with messages without blocking the enterprise application.
- Sample JMS 1.1 application client
If we are new to JMS 1.1 application client programming, we can use this example code as a starting-point for developing your client application.
Subtopics
- Listing JMS resources for the default messaging provider
Use the WAS console to list JMS resources for the default messaging provider, for administrative purposes.
- Configure JMS resources for point-to-point messaging
Configure connection factories, queues and service integration bus destinations for point-to-point messaging.
- Configure JMS resources for publish/subscribe messaging
Use this task to configure a JMS resources for publish/subscribe messaging.
- Configure a unified connection factory for the default messaging provider
Use this task to configure a unified JMS connection factory for applications that use the JMS 1.1 domain-independent (unified) interfaces.
- Configure a queue connection factory for the default messaging provider
Use this task to configure a JMS queue connection factory for point-to-point messaging with the default messaging provider. This is intended more for backwards compatibility, as described in section 1.5 of the JMS 1.1 specification.
- Configure a topic connection factory for the default messaging provider
Use this task to configure a JMS topic connection factory for publish/subscribe messaging with the default messaging provider. This is intended more for backwards compatibility, as described in section 1.5 of the JMS 1.1 specification.
- Configure a queue for the default messaging provider
Use this task to configure a JMS queue for point-to-point messaging with the default messaging provider.
- Configure a topic for the default messaging provider
Use this task to configure a JMS topic for publish/subscribe messaging with the default messaging provider.
- Configure an activation specification for the default messaging provider
Configure a JMS activation specification to enable a message-driven bean to communicate with the default messaging provider.
- Delete JMS resources for the default messaging provider
Use this task with the WAS console to delete JMS resources.
- Configure JMS connection factory properties for durable subscriptions
Use this task to configure durable subscription properties of JMS connection factories for use by enterprise beans with the default messaging provider.
- Configure JMS activation specification properties for durable subscriptions
Use this task to configure durable subscription properties of JMS activation specifications for use by message-driven beans with the default messaging provider.
- Enable a provider to stream messages to cloned durable subscriptions
Use this task to enable a provider to stream messages to consumers ahead of their message requests. This is most often used by publish/subscribe consumers to provide a performance enhancement.
- Enable CMP entity beans and messaging engine data stores to share database connections
Use this task to enable container-managed persistence (CMP) entity beans to share the database connections used by the data store of a messaging engine. Performing this task has been estimated to provide a potential performance improvement of 15% for overall message throughput, but can only be used for entity beans connected to the application server containing the messaging engine.
- Configure a connection to a non-default bootstrap server
A bootstrap server is an application server running in the same cell, specifically the same core group, as the service integration bus.
- Protecting an MDB or SCA application from system resource problems
We can configure the system so that if there is a problem with a dependent external system resource, the enterprise application is stopped before messages are moved unnecessarily to an exception destination. This configuration also handles occasional problems with messages without blocking the enterprise application.
- Sample JMS 1.1 application client
If we are new to JMS 1.1 application client programming, we can use this example code as a starting-point for developing your client application.