它应当被用于受管理的环境下。
使用受管理路由路径路由消息
它可被用于受管理的或不受管理的环境下。
它可被用于受管理的或不受管理的环境下。
It can be used in both managed and non-managed environments.
配置所需的受管理对象。
确保审核的范围处于很高的级别，即您希望受管理的级别。
Make sure the scope of auditing is at a very high level, the level at which you want to be managed.
下面的表1给出一些自动生成的受管理系统名示例。
Some example automatically generated managed system names are shown in Table 1, below.
受管理系统配置一个共享内存池，这个池有2GB的真实内存。
The managed system is configured with a Shared memory pool that has 2 GB of real memory assigned.
还可以使用搜索功能寻找某个受管理系统上的LPAR。
A search function is also available if you are looking for an LPAR on a particular managed system.
这个方面还用受管理bean类上的类型间声明定义了辅助方法。
This aspect also defines helper methods using inter-type declarations on managed bean classes.
反过来，这将会导致不应该创建受管理bean时却创建了。
This, in turn, could lead to a managed bean being created when it shouldn't be.
应用程序如何使用JNDI在JMS实现层中访问JMS受管理对象。
How the application accesses the JMS administered objects in the JMS implementation layer using JNDI.
在所有受管理的程序中，Exception对象代表了处理的错误。
In all managed applications, Exception objects represent processing errors.
可以很快看出在连接某个HMC的受管理系统中哪个使用的处理器最多。
You can quickly observe which of the managed systems connected to an HMC is using the most processor.
必须在实现JNDIAPI 的目录中注册JMS受管理对象。
The JMS administered objects must be registered in a directory that implements the JNDI API.
这些特殊的组件是企业和业务单元级支持的企业资产的受管理和控制的集合。
These special components are a managed, governed set of enterprise assets that are funded at the enterprise or the business unit level.
MBean可以是一个统计提供者，它为受管理的应用程序和资源提供各种统计数据。
An MBean can be a statistics provider that supplies various statistical data for the managed application and resource.
当我第一次运行load. sh脚本时，从两个HMC收集所有受管理系统的数据。
When I ran the load.sh script for the first time, data was collected from both HMCs for all the managed systems.
要想在HMC上收集使用数据，必须为每个受管理系统启用数据收集(图12)。
To collect utilization data on the HMC, data collection must be enabled for each managed system (Figure 12).
然而，存在一些相对简单的方法来处理TCS和任意受管理服务之间的安全通道。
There are, however, some relatively simple approaches to handling a secure communication channel between the TCS and any managed service.
我们已经知道，每个JMS受管理对象必须在可以通过JNDI访问的目录中注册。
We already know that every JMS administered object must be registered in a directory accessible via JNDI.
在前面步骤中创建的受管理对象在供JMS应用程序使用之前，需要在目录中注册。
The administered objects created in the previous step need to be registered in the directory before they are available to the JMS application.
如果同一目的地的消息需要按照不同的方式进行路由，则不能使用受管理路由路径。
If messages at the same destination need to be routed differently, then administered routes cannot be used.
JMS应用程序通过这些受管理对象与WebSpheremq队列管理器通信。
A JMS application communicates with WebSphere MQ queue managers via these administered objects.
因为这个受管理系统名包含物理机器的序号，所以确保它在整个企业范围内是惟一的。
This managed system name is guaranteed to be enterprise-wide unique since it contains the serial number of the physical machine.
可以用JSF -EL(表达式语言)把JSF组件绑定到受管理的bean属性。
You can use the JSF-EL (expression language) to bind JSF components to managed bean properties.
它需要的磁盘空间非常少，具体数量取决于取样速率以及受管理系统和LPAR的数量。
Remarkably, it requires very little disk space, depending on the sample rate, the number of managed systems and LPARs.
这个特点的副作用是，受管理系统上的每个LPAR在任何时候都能够使用其标称处理能力。
As a side effect, this means every LPAR on a managed system will always be able to use its entitled capacity at any point in time.
使用受管理系统名特有的命名结构格式，从而进一步帮助识别受管理系统和组织中的其他实体。
Use a naming structure format that is unique to managed system names, thereby further delineating the name from other entities in the organization.
受管理对象是实现JMS接口并且特定于根提供程序的对象，并且可以通过应用程序直接访问。
Administered objects are the root provider-specific objects that implement JMS interfaces and are directly accessible by the application.
应用推荐