关键的解决方案组件列示如下并如图2所示。
Key solution components are listed below and shown in Figure 2.
打包解决方案组件。
下面的章节将概括介绍这些解决方案组件的特点。
The following sections briefly describe the characteristics of the solution components.
了解IBM解决方案组件如何解决这些问题。
这种操作耦合意味着解决方案组件可能会争用有限的资源。
This operational coupling implies that solution components could compete for limited resources.
重要的是记住在解决方案组件之间的边界上使用Web服务是不合适的。
It's important to remember that it is acceptable not to use web services at the boundary between solution components.
这些值描述了解决方案组件依赖关系的类型。这个 依赖 。
Values represent the These possible types of solution components for the SolutionComponent.
这样，解决方案组件将在单独的进程中运行(因为它们位于不同的集群成员中)。
The solution components will then run in separate processes (since they are in different cluster members).
这包括安装解决方案组件和使用其操作所需的资源（如数据库表和队列）对其进行配置。
This includes installing the solution components and configuring them with the resources, such as database tables and queues, that they need to operate.
检索列表的解决方案组件的依赖关系，可以防止你卸载一个托管解决方案。
A list of Retrieves all the entities that can participate in a Many-to-Many entity relationship.
这些功能允许通过定义一个“集群化”拓扑跨多个流程和多台物理机器分发解决方案组件。
These capabilities enable the distribution of solution components across multiple processes and multiple physical machines by defining a "clustered" topology.
可维护性许多解决方案组件是使用遗留平台技术实现的，但组织不再掌握这方面的技术了。
Maintainability Many solution components are implemented using legacy platform technologies in which the organization no longer has expertise.
为创建和部署服务、数据同步、发现和发布服务、开发和管理定制解决方案组件提供工具支持。
Tooling support for the creation and deployment of services, data synchronization, discovery and publication of services, development and administration of custom solution components.
用绿色填涂的组件是前面描述的组件和在架构模式中讨论的组件之外的解决方案组件。
The components shaded in green represent solution components that are in addition to those described previously and those discussed in the architectural patterns.
这些要求不一定会影响解决方案组件本身的开发，但却会影响客户解决方案的操作环境。
These requirements do not necessarily affect the development of the solution components themselves, but rather the operating environment for customer solutions.
架构师可能也要通过制定与目标运行时及解决方案组件的部署位置相关的决策，来优化分析师定义的流程模型。
The architect may also refine the process model defined by the analyst by making decisions concerning the target run times and where the solution components are to be deployed.
混搭应用程序和Web应用程序都使用浏览器作为客户端解决方案组件，从而为特定的应用程序提供一个用户界面(UI)。
Both mashups and Web applications generally use a browser as the client-side solution component that provides a user interface (UI) to a given application.
更重要的是，还可以定义哪个解决方案组件使用哪个总线，从而确保使用不同总线的解决方案组件也使用不同的线程池。
More importantly, you can also define which solution component USES which bus, thus ensuring that solution components using different buses also use different thread pools.
隔离各个解决方案组件的最简单、也是成本最高的方法是将各组件放到分隔的硬件上—通常以一个已定义分类系统为依据。
The simplest, but also the most costly way of isolating solution components from each other is to put them on separate hardware, typically according to a defined classification system.
或者，如果针对一个解决方案进行了一个错误的管理更改，导致整个进程崩溃或挂起，则那个进程托管的所有解决方案组件也会崩溃或挂起。
Or, if a faulty administrative change was made for one solution, causing an entire process to crash or hang, then all solution components hosted by that same process will crash or hang too.
图5展示了一个一般化的项目组合管理采用路线图实例，它是由IBMRational开发的，作为项目组合管理过程和解决方案组件的交付工作的一部分。
Figure 5 provides an example of a generic portfolio management Adoption Roadmap, developed by IBM Rational as part of the delivery effort for portfolio management processes and solution components.
这些是这个解决方案蓝图的必有组件。
版本部署人员在生产环境中配置解决方案的组件。
The Release Deployer configures the components for the solution in the production environment.
关于你们的解决方案和组件选择的方法，你们能给我们一些细节吗？
InfoQ: Could give us some details on your approach to solution and component selection?
开发整个解决方案及其组件的逻辑和物理布局(结构)。
Develops the logical and physical layout (structure) of the overall solution and its components.
解决方案：调出安全组件。
图4展示的是理想化的解决方案，因为某些组件可能不支持动态设置超时。
Figure 4 presents a somewhat ideal solution, because some of the components might not support dynamically setting timeouts.
图5说明了这种解决方案模式包含的组件。
Figure 5 depicts the components involved in this solution pattern.
讨论一个样例医疗解决方案及其组件。
这些更新还可以与J2EE元素外的其他解决方案支持组件一起使用，如数据库更新、操作系统更新，等等。
These updates may also be combined with other supporting solution components outside the J2EE elements, such as database updates, operating system updates, and so on.
应用推荐