连接集中器与代理的上下文切换相关联。
The connection concentrator is associated with context switching of agents.
参见连接集中器的行为。
连接集中器的工作原理。
连接集中器(事务池)。
启用连接集中器必须将连接池打开？
支持连接集中器的数据库。
连接集中器的工作取决于事务边界(提交和回滚)。
Connection concentrator ACTS upon transaction boundaries (commit and rollback).
在连接集中器场景中，只有在事务需要时才产生代理。
In a connection concentrator scenario, agents are spawned only when needed for transactions.
不能在打开连接集中器的情况下启用联邦参数。
The federated parameter cannot be enabled with the connection concentrator on.
在数据库管理器配置中设置以下参数以启用连接集中器
Set the following parameters in the database manager configuration to enable the connection concentrator
现在连接集中器是打开的，服务器的配置仍然保持不变。
Now the concentrator is turned on and your server's configuration stays the same.
连接集中器有助于减少当连接空闲时每个代理分配的资源。
Connection concentrator helps reduce the resources each agent allocates when the connection is idle.
如果在启用了连接集中器时参数没有设置正确会怎么样呢？
What happens if the parameters aren't set properly when the concentrator is enabled?
如果您不能纠正这个问题，那么您的环境就不适合于使用连接集中器。
If you cannot correct this problem, then your environment is not suitable for the use of the connection concentrator.
一旦启用了连接集中器，数据库代理就只在SQL事务期间是“热的”。
With the connection concentrator enabled, the database agent is "hot" only for the duration of an SQL transaction.
因此，这个最高数字基本上就是在启用连接集中器时您同时需要的最大代理数。
Thus, this high water mark number is roughly how many agents you need simultaneously at peak when the concentrator is on.
这表示自您的实例以启用连接集中器开始以来的所有时间点上存在的最大代理数。
This indicates the highest number of agents that existed at any point during the entire time since your instance was started with concentrator enabled.
连接集中器允许用户看起来是连接到数据库的，而实际的数据库代理仍然可以服务入站请求。
The connection concentrator allows users to appear connected to the database while the actual database agent is free to service incoming requests.
这样会导致到达事务边界时的代理分配和解除分配这一巨大开销，这会影响连接集中器的功能。
This will create a large overhead of allocation and deallocation of agents upon reaching transaction boundaries, which defeats the purpose of the connection concentrator.
启用了连接集中器之后，一旦到达事务边界，db2agent就是自由的，可以服务于其他请求。
With connection concentrator enabled, upon reaching transaction boundaries, the db2agent is free and ready to service other requests.
是的，由于连接集中器需要利用连接池的功能，因此启用连接集中器必须将连接池打开。
Yes, connection concentrator needs connection pooling to be enabled in order to exploit its functionality.
而DB 2Connect中的连接集中器功能不要求应用程序断开连接就可以实现资源重用。
The connection concentrator function in DB2 connect on the other hand does not require an application disconnect for the resources to be reused.
max_connections的值必须大于max_coordagents的值，以打开连接集中器。
The value of max_connections must be greater than the value of max_coordagents to turn on the connection concentrator.
注意：当max_connections的值大于max_coordagents的值时，连接集中器便被启用。
Note: connection concentrator is enabled when max_connections is greater than max_coordagents.
分配器(dispatcher)是一个db 2进程(db 2disp)，即连接集中器的关键组件。
The dispatcher is a db2 process (db2disp), the key component of the connection concentrator.
默认情况下，max_connections参数等于max_coordagents，因而连接集中器是不启用的。
By default the max_connections parameter is equal to max_coordagents and the connection concentrator is not enabled.
连接集中器(connectionconcentrator)是DB 2connect特有的一个功能。
The connection concentrator is a feature that is unique to DB2 connect.
当您看到这样的情况时，比如在连接集中器打开后用户请求将被挂起，那么您的max_coordagents设置可能不够高。
When you see situations, such as user requests that appear to hang after the connection concentrator is turned on, your max_coordagents setting might not be high enough.
有关连接集中器的一个常见问题是，“将max_connections和max_coordagents设为多大才最好？”
A frequent question about the connection concentrator is, "What's a good value to set for max_connections and max_coordagents?"
DB 2UDBV7客户机不能利用DB 2 UDB V 8连接集中器的优势，它只对V8客户机和本地V 8服务器连接起作用。
DB2 UDB V7 clients cannot take advantage of the DB2 UDB V8 connection concentrator, which only works with V8 clients and local V8 server connections.
应用推荐