代码样本显示了EJB组件如何使用连接对象来访问消息队列资源。
This code sample shows how an EJB component might access a message queue resource, using connection objects.
实际上，在WebServices等待发送或接收消息时，消息队列资源要么稀缺要么不稀缺。
In reality, the message queuing resource is either scarce or isn't scarce while Web services are waiting to send or receive a message.
在本文中，我分析了J2EE环境中服务器端资源(例如数据库、消息队列、目录和企业系统)的连接合用。
In this article, I examine connection pooling in a J2EE environment for server-side resources such as databases, message queues, directories, and enterprise systems.
其它类型的事务性资源，JMS消息队列和JCA连接器，依靠相似的机制将资源征用隐藏起来，使用户看不到。
The other types of transactional resources, JMS message queues and JCA connectors, rely on a similar mechanism to hide resource enlistment from the user.
与数据库资源一样，通过使用可以合用的连接对象来访问消息队列。
As in the case of a database resource, message queues are accessed using connection objects that can be pooled.
正如下面约束与限制部分中所述，消息流必须仅访问JDBCxa数据源和mq队列，而不是其他OD BC数据源或资源管理器。
As noted in the Restrictions and Limitations section below, the message flow must access only the JDBC XA data source and MQ queues, and not other ODBC data sources or resource managers.
存储过程程序可以访问DB2数据和传统的非db2资源，比如QSAM和VSAM数据集、消息队列、CICS程序、IMS事务和数据库。
The stored procedure program can access DB2 data as well as traditional non-DB2 resources such as QSAM and VSAM data sets, message queues, CICS programs, IMS transactions and databases.
另外，如果一个资源表示需要被返回，在回复的消息头部中会申明一个返回队列参数。
In addition, if a resource representation should be returned, a return queue parameter is specified in the header.
点对点：当存在两个直接交互的应用程序时，该消息模型称为点对点模型，并且所使用的JMS资源是一个队列。
Point to point: When there are two applications that interact directly, the messaging model is called point to point, and the JMS resource that's used is a queue.
而且，J2EE规范只认可三种类型的事务性资源 ―JDBC数据库、JMS消息队列服务器和“其它通过JCA访问的事务性服务”。
Moreover, the J2EE specification only recognizes three types of transactional resources -- JDBC databases, JMS message queue servers, and "other transactional services accessed through JCA."
一种常用方法是，让应用程序把数据发送给一个消息队列，比如ibmWebSphereMQ，等待到资源可用时处理数据。
One common approach is to have the application send the data into a message queue, such as IBM WebSphere MQ, to be processed when the resources are available.
应用程序、系统和网络通常比其给定的资源容量(其中包括WebServices可用的消息队列)的发展速度更快。
Applications, systems, and networks are generally growing more rapidly than their given resource capacity, and this includes message queues for Web services.
异步的松散耦合WebServices的一个问题是，对于某些业务功能，可能会超出消息队列服务器或系统的资源容量。
One problem with asynchronous loosely coupled Web services is that for some business functions, it can exceed its resource capacity for the message queuing servers or system.
每个总线成员内都有许多消息传递引擎，可以管理队列等运行时资源并能够在文件、内存或数据库内存储消息。
Within each bus member, there is a number of messaging engines that manage runtime resources like queues and are capable of storing messages in a file, memory, or database.
当一个EJB组件想访问数据库、消息队列服务器或者其它一些事务性资源时，它需要到资源管理器的连接(通常是使用JNDI)。
When an EJB component wants to access a database, a message queue server, or some other transactional resource, it acquires a connection to the resource manager (usually by using JNDI).
这包括对JDBC资源、jms队列、消息传送引擎等的配置。
This includes configuration for JDBC resources, JMS queues, messaging engines, and more.
资源管理器存储应用程序状态，常常是数据库，但也可能是消息队列服务器（在J2EE 应用程序中，它们将是 JMS提供者）或其他事务性资源。
The RMs store the application state and are most often databases, but could also be message queue servers (in a J2EE application, these would be JMS providers) or other transactional resources.
您必须首先设置以下资源，然后才能将消息发送到ServiceIntegrationBus上托管的队列或从该队列获取消息。
You must first set up the following resources before you can send or retrieve messages to or from a queue hosted on a Service Integration bus.
要为Web服务实现提供SOAP/JMS支持，必须创建所需的 JMS资源（队列（Queue）、队列连接工厂（Queue Connection Factories）和侦听器端口（Listener Ports））来处理和响应传入的消息。
To support SOAP/JMS for the Web service implementation, you must create the JMS resources (Queue, Queue Connection Factories and Listener Ports) needed to handle and respond to incoming messages.
所有消息传递资源(连接工厂、队列、主题等)都被分配给一个已命名总线。
All messaging resources (connections factories, queues, topics, and so on) are assigned to a named bus.
释放构造器中分配的资源，包括消息队列，如果他不是作为参数传递给构造器的。
Deletes resources allocated in ACE_Task constructor, which includes the message queue, if it wasn't passed as a parameter to the constructor.
这个消息队列群集资源为分布式、异步消息应用程序提供通信基础结构。
This Message Queuing Cluster Resource provides a communications infrastructure for distributed, asynchronous messaging applications.
这个消息队列群集资源为分布式、异步消息应用程序提供通信基础结构。
This Message Queuing Cluster Resource provides a communications infrastructure for distributed, asynchronous messaging applications.
应用推荐