在计算单元级别中，由于仅需要对资源定义一次并且每个应用服务器都可以看到它，因此界定所有内容似乎非常容易。
Scoping everything at the cell level might seem easy since a resource only needs to be defined once and every application server can see it.
任何在计算单元内运行的J2EE应用程序都可以潜在地访问任何J2EE资源。
Any J2EE application that runs within the cell can potentially access any J2EE resource.
这决定了JMS资源可以由一个应用服务器使用，还是由运行在节点上的所有应用服务器或运行在网络部署单元(Net work Deployment cell)的所有应用服务器使用。
This determines whether the JMS resource can be used by an application server, all application servers running on the node or all application servers running in the Network Deployment cell.
确保在单元(cell)范围或与您的应用服务器节点相适应的范围下创建该资源。
Make sure the resource is created either under cell scope, or under the appropriate scope for your application server node.
如果这样做，计算单元内的任何应用程序就都可以查找该资源，然后将隐式地使用提供的用户ID和密码。
If you do so, then any application within the cell can look up the resource, and then implicitly use the provided user id and password.
服务和资源分别被打包成束，这些束作为应用程序的传递单元的文件。
Services and resources are packaged into bundles, which are files that serve as the delivery unit for applications.
因此，计算单元中的任何应用程序都可以访问任何使用组件别名定义的资源。
Thus, any resource defined with a component alias is accessible to any application in the cell.
根据应用程序性能增加或减少计算资源单元。
Higher and lower compute resource units based on application performance.
WebSphereMQETClient让应用程序可以在TXSeries等外部同步点(syncpoint)协调器的控制下，参与其他本地资源管理器的工作单元。
The WebSphere MQ et Client lets applications participate within a unit of work with other local resource managers, under the control of an external syncpoint coordinator such as TXSeries.
WebSphereMQETClient让应用程序可以在TXSeries等外部同步点(syncpoint)协调器的控制下，参与其他本地资源管理器的工作单元。
The WebSphere MQ et Client lets applications participate within a unit of work with other local resource managers, under the control of an external syncpoint coordinator such as TXSeries.
应用推荐