Configure the JMS administered objects.
配置JMS管理的对象。
To define the JMS queue administered objects.
要定义jms队列管理的对象，请执行以下步骤。
To configure the needed administered objects.
配置所需的受管理对象。
To a third-party JMS provider using JNDI administered objects.
使用由JNDI管理的对象连接到第三方jms提供者。
The type of JNDI namespace from which administered objects are to be retrieved.
要从其中检索受管的对象的JNDI名称空间的类型。
The JMS administered objects must be registered in a directory that implements the JNDI API.
必须在实现JNDIAPI 的目录中注册JMS受管理对象。
A JMS application communicates with WebSphere MQ queue managers via these administered objects.
JMS应用程序通过这些受管理对象与WebSpheremq队列管理器通信。
How the application accesses the JMS administered objects in the JMS implementation layer using JNDI.
应用程序如何使用JNDI在JMS实现层中访问JMS受管理对象。
It is assumed that you have already edited JMSAdmin.config to configure a namespace to store JMS-administered objects.
假设您已经对JMSAdmin . config进行了编辑，以配置一个名称空间来存储JMS受管的对象。
Administered objects are not dependent on JNDI, but it is implicit that they can be bound to and looked up in a JNDI namespace.
受管的对象并不依赖于JNDI，但暗示它们可以绑定到JNDI名称空间并可以在其中查询它们。
The nodes can reuse any existing JNDI repositories and administered objects that are already set up for the existing JMS network.
这些节点可以重用任何现有的JNDI储存库和已为现有的JMS网络建立的管理对象。
You should now be able to see how a JCA resource adapter would provide the JMS destination objects by using administered objects.
现在应当能够看出JCA资源适配器如何通过使用托管对象来提供JMS目标对象了。
WebSphere MQ provides an administration tool that creates and manages administered objects in any JNDI accessible directory service.
WebSphereMQ提供管理工具，以便在JNDI可访问的任何目录服务中创建和管理受管理对象。
Administered objects are the root provider-specific objects that implement JMS interfaces and are directly accessible by the application.
受管理对象是实现JMS接口并且特定于根提供程序的对象，并且可以通过应用程序直接访问。
Since the WebSphere MQ names are encapsulated within the JMS administered objects, the application code is not affected by these changes.
由于WebSphereMQ名称封装在JMS受管理对象中，因此应用程序代码不受这些更改的影响。
The administered objects created in the previous step need to be registered in the directory before they are available to the JMS application.
在前面步骤中创建的受管理对象在供JMS应用程序使用之前，需要在目录中注册。
For example, message priority can be specified in the application code but may also be overridden through settings in the administered objects.
例如，消息优先级可以在应用程序代码中指定，但是也可以通过管理对象中的设置覆盖。
As WebSphere MQ messaging provider administered objects are held in JNDI, they are accessible from any process with access to the JNDI namespace.
由于WebSphereMQ消息传递提供程序受管理对象保存在JNDI中，因此可以从有权访问JNDI命名空间的任何流程访问它们。
The application USES JNDI to lookup the various JMS administered objects it needs and USES these to attach to the WebSphere MQ messaging provider.
应用程序使用JNDI查找它需要的各种JMS受管理对象，并使用这些对象来附加到WebSphereMQ消息提供程序。
EjbCreate initializes the Apache Velocity templating engine context and looks up the JMS-administered objects, the connection factory, and destination.
ejbCreate初始化apacheVelocity模板引擎上下文，并查看JMS管理对象、连接工厂和目标。
The JMS specification refers to objects that are created by an administrator and contain configuration information for use by JMS clients as JMS administered objects.
JMS规范将那些由管理员创建并且包含由JMS客户机使用的配置信息的对象称为JMS受管的对象。
The sample code includes a script to invoke the WebSphere MQ JMS administration tool, as well as the definition scripts for the administered objects we will be using.
示例代码包括一个调用WebSphereMQJMS管理工具的脚本，还包括我们将使用的受管理对象的定义脚本。
Accept the default values on the "Bind message destination references to administered objects" panel, because of how we named the actual message destinations we created.
接受“Bindmessagedestinationreferences toadministered objects”面板中的缺省值，因为我们就是这样为我们创建的实际消息目的地命名的。
While there are many types of resources that can be represented in a registry, three types of administered objects are of primary interest to JMS: connection factory, queue, and topic.
尽管在注册中心可以表示许多类型的资源，但是以下三种类型的受管理对象对JMS最重要：连接工厂、查询和主题。
Now that we've configured WebSphere MQ and defined the administered objects in the JNDI directory, we're ready to run the sample included with this article. To do so, follow these steps
现在已经配置了WebSphereMQ，并在JNDI目录中定义了受管理对象，我们已经准备好运行本文附带的示例。
However, before they can be used by the sample application, we need to define a number of JMS administered objects so that the sample application can interact with them using the JMS 1.1 API.
不过，在示例应用程序使用这些对象前，我们还需要定义一系列JMS管理的对象，以便示例应用程序能够使用JMS 1.1API与它们进行交互。
However, before they can be used by the sample application, we need to define a number of JMS administered objects so that the sample application can interact with them using the JMS 1.1 API.
不过，在示例应用程序使用这些对象前，我们还需要定义一系列JMS管理的对象，以便示例应用程序能够使用JMS 1.1API与它们进行交互。
应用推荐