每个事务分类在各自的服务区域中运行。
每个服务区域都具有对实际存储的需求。
用户不直接控制服务区域。
工作队列与服务区域的关系
服务区域实例数量设置为最小2个，最大4个。
Servant region instances is set to minimum of 2 and maximum of 4.
服务区域将由WLM重新启动以继续该工作。
The servant region will be restarted by WLM to continue the work.
它实际保证的是会话关联在服务区域之间的均等分配。
What it actually guarantees is the equal distribution of session affinities among servant regions.
要利用zWLM功能，您需要启用多个服务区域。
To use the zWLM function, you need to enable multiple servant regions.
通过更改工作负载概要调整每个服务区域的工作线程数量。
Adjust number of worker threads for each servant region by changing the workload profile.
请注意单个服务区域与多个服务区域之间的区别。
Notice any differences between the single servant region and multiple servant regions.
这也可以通过WLM自动维护服务区域数量的功能来实现。
This can also be achieved through WLM's capability to automatically maintain the number of servant regions.
在服务区域处理请求之前，请求被放在WLM工作队列中。
Before the request is processed by the servant region, it's put inside the WLM work queue.
然后zWLM使用这些分类来选择某个服务区域以处理消息。
ZWLM then USES these classifications to select a servant region to process the message.
这些服务分类指定每种类型的各自服务区域中的消息处理目标。
These service classes specify the goals for message processing in the respective servant regions for each type.
通过更改最小和最大服务区域数量添加更多服务区域。
Add more servant regions by changing the minimum and maximum number of servant regions.
缺省情况下，为J2EE服务器配置了单个服务区域。
By default, a J2EE server is configured for a single servant region.
如果CPU资源在该时段中非常紧张，则服务区域将很难启动。
If CPU resources are very tight during that period, then the servant region will have a hard time getting started.
如果系统上的实际存储量有限，您可能担负不起拥有许多服务区域。
If there is a limited amount of real storage on the system, then you can't afford to have many servant regions.
WLM能够动态管理服务区域数量，以便实现总体系统吞吐量目标。
WLM is capable of dynamically managing the number of servant regions in order to achieve the overall system throughput goal.
考虑客户端关联后，工作请求将在WLM控制之外直接路由到服务区域。
When client affinity is to be honored, the work requests are directly routed to the server regions and out of WLM's control.
当服务区域JVM的垃圾收集合理和可接受时，此方法是首选的方法。
This approach is preferred when garbage collection for the servant region JVM is reasonable and acceptable.
在此场景中，具有不同服务分类的所有请求都将在该服务区域中并发地执行。
In this scenario, all requests with different service classes will all be executed in the servant region concurrently.
因此，这种具有单个服务区域的应用程序环境称为“非托管”应用程序环境。
Thus, such an application server environment with a single servant region is called an “unmanaged” application environment.
最小数量的两个服务区域已经启动，其ASID分别为00a4和00aa。
The minimum number of two servant regions have been started with ASID of 00a4 and 00aa.
请确保有足够的存储来支持预期的工作负载吞吐量所需要的最大服务区域数量。
Make sure that there is enough storage to support the maximum number of servant regions that are needed for the expected workload throughput.
地图可以用来表现你们影响的地区，组织成员，服务区域，危机发生点甚至更多。
Maps can be used to show your areas of impact, members, service locations, crises spots and much more.
服务区域将从这些队列中选取请求，并在服务区域地址空间中处理请求。
A servant region will pick up the requests from these queues and process them in the servant region address space.
否则，针对某个事务分类的第一个请求可能要花一些时间，因为需要启动服务区域。
Otherwise the first request to a Transaction Class could take some time because the servant region would need to be started.
相反，WLM将根据需要动态地启动和维护服务区域，以满足工作负载的性能目标。
Instead, WLM will dynamically start and maintain the servant regions as required to meet the workload's performance goal.
运行在该服务区域中的对应MDB实例基于为该消息分类设定的目标处理消息。
The corresponding MDB instance running in that servant region processes the message based on goals set for that class of message.
应用推荐