New generic JMS provider bindings.
新的通用JMS提供者绑定。
Sending the message to a JMS provider
向JMS提供者发送消息
Specify the URL for the JMS provider.
为JMS提供者指定url。
This step is the same as for the embedded JMS provider.
该步骤与嵌入式JMS提供程序中的步骤相同。
The JMS provider would load-balance them across consumers.
JMS提供者会在消费者之间根据负载平衡原则分配这些消息。
To a third-party JMS provider using JNDI administered objects.
使用由JNDI管理的对象连接到第三方jms提供者。
Applications are bound to JNDI objects that represent the JMS provider.
将应用程序绑定到表示JMS提供程序的JNDI对象中。
The JMS provider that owns the topic sends it to the topic's subscribers.
拥有该主题的JMS提供者将消息发送给该主题的订阅者。
The JMS provider must support nested map messages to convert collection classes.
JMS提供者必须支持嵌入的映射消息来对集合类进行转换。
Each JMS provider has tuning parameters and techniques to enhance JMS performance.
每个JMS提供者都有相应的优化参数和技术用以提高JMS的性能。
Note that the Geronimo JMS provider, ActiveMQ, already includes clustering support.
注意,GeronimoJMS提供程序active MQ已经包含集群支持。
In general terms, a connection pool is a pool of free connections to a JMS provider.
总的来说,连接池是一个到JMS提供程序的空闲连接池。
The following sections describe how to install the embedded JMS provider or the MQ JMS provider.
下面的部分描述了如何安装嵌入式JMS提供程序或者MQ JMS提供程序。
Of course, it is also possible to write portlets that use just JMS and use MQ as the JMS provider.
当然,也可以仅使用JMS来编写Portlet,并使用MQ作为JMS提供程序。
In summary, this restriction makes it easier to implement a JMS provider as a JCA resource adapter.
总之,这种限制使得JMS提供者更容易实现为JCA资源适配器。
Leave the JMS provider to the Default messaging provider and specify user id and password to access it.
将JMS提供程序保留为缺省消息传递提供程序,并指定访问它的用户ID和密码。
The two queues, one for the request and one for the response, must be exposed as part of a JMS provider.
这两个队列,一个为请求队列,另一个为响应队列,必须作为JMS提供程序的一部分公开。
We will then configure our JMS provider so that applications can interact with the bus through the JMS API.
随后,我们将配置我们的JMS提供程序,以便应用程序能通过 JMSAPI与总线交互。
For a JMS provider, the JCA specification recommends that the names and values given in Table 1 be supported.
对于JMS提供者,JCA规范建议支持表1中给出的名字和值。
The following sections describe how to configure and start the embedded JMS provider and the MQ JMS provider.
下面的部分描述如何配置和启动嵌入式JMS提供程序和MQ JMS提供程序。
For performance tuning information for the JMS server or JMS client setup, see the JMS provider documentation.
有关JMS服务器或JMS客户端设置的优化信息,请参阅相应的JMS提供者文档。
Unfortunately, these properties are only recommended, and not every JMS provider will necessarily support them.
不幸的是,这些属性只是建议性的,不是每一个JMS提供者都一定支持它们。
The connection factory is responsible for creating connections to the JMS provider, which in this case is ActiveMQ.
连接工厂负责创建指向JMS提供程序(本例中为ActiveMQ)的连接。
The sample application is currently configured to make use of resources configured on the WebSphere MQ JMS provider.
示例应用程序当前配置为使用在WebSphereMQJMS提供程序上配置的资源。
Since they are JMS resources, we will create them in the JMS provider for the SIBus: the default messaging provider.
由于这些是JMS资源,所以将在SIBus的JMS提供程序(即缺省的消息传递提供程序)中进行创建。
Figure 4 shows how to select the new generic JMS provider protocol binding for export and imports within the tooling.
图4显示了如何在工具内选择新的用于导出和导入的通用JMS提供者绑定。
In addition, the JMS provider will need to be configured to support multiple subscribers on the appropriate destinations.
此外,还需要将JMS提供者配置为在一些适当的目的地上可以有多个订阅者。
One of the aims of version 1.5 of the specification is to allow a JMS provider to be implemented as a JCA resource adapter.
规范的1.5版本的目标之一就是允许JMS提供者作为JCA资源适配器实现。
When WebSphere MQ is configured as a JMS provider, it will use the default key and trust stores for the application server.
当WebSphereMQ被配置成JMS提供程序时,它将对应用服务器使用缺省的密钥和信任存储区。
JMS Activation Specifications represent a group of messaging configuration properties that could differ for each JMS provider.
JMS激活规范表示一组可能随每个jms提供者而异的消息配置属性。
应用推荐