But now the connections run in managed mode.
但现在连接在受管模式中运行。
The migrated classes can run in managed or non-managed mode.
迁移后的类可以运行于受管或非受管模式下。
In non-managed mode, the application is responsible for quality of service.
在非受管模式下，应用程序负责服务质量。
In this case, binding resource reference name CICSECI_B to cicseci turns on managed mode.
在这种情况下，将资源引用名cicseci_b绑定到cicseci将打开受管模式。
A J2C application runs in managed mode when the application server provides the connection factory.
当应用程序服务器提供连接工厂时，J2C应用程序就在受管模式下运行。
To set the properties for non-managed mode, you must specify all properties required by your CICS server.
要针对非受管模式设置属性，您就必须指定CICS服务器所需的所有属性。
Now that your connections are running in managed mode, you can use the quality-of-service features of WebSphere Application Server.
既然您的连接已经运行在受管模式下，那么您就可以使用WebSphereApplicationServer的服务质量功能了。
As with the JSP and servlet sample, the EJB runs in managed mode when the connection factory is obtained from the application server.
与使用JSPand servlet样本一样，在从应用程序服务器获取连接工厂时，EJB运行于受管模式下。
If you migrate to Integration Edition, you gain full support of J2C managed mode, which is in itself a significant benefit over using CCF connectors or running in J2C non-managed mode.
如果您迁移到集成版，您就获得了对J2C受管模式的完全支持，这本身比起使用CCF连接器或在j2c非受管模式下运行也大有好处。
Under managed mode, the application server interfaces with resource adapters to manage quality of service features such as connection pooling, transaction management, tracing, and security.
在受管模式下，应用程序服务器与资源适配器建立接口，从而管理诸如连接池、事务管理、跟踪和安全性之类的服务质量特性。
Managed mode with application server.
应用服务器的托管模式。
Managed mode with application server.
应用服务器的托管模式。
应用推荐