This article, the second in the series, focuses on selecting a correct deployment pattern to meet the requirements of a given customer application or project.
本文是系列文章中的第二篇，重点关注于选择合适的部署模式以满足给定客户应用程序或项目的需求。
The pattern of a canonical data and message model is presented in a future article in this series.
规范化数据模型和消息模型的模式将在本系列的后续文章中讨论。
This coding pattern follows the same approach that Part 1 of this article series introduced as an example (see Resources).
此编程模式采用与本系列第1部分作为例子介绍的相同方法(参见参考资料)。
This short-running process follows the Execute Transaction pattern described in Part 2 of this series.
这个短时间运行的流程遵循本系列 第 2部分中所述的“执行事务”模式。
Part 1 of this series shows that the ESB is a key architectural pattern within the larger architectural pattern called SOA.
本系列的第1部分表明了esb是称为SOA的更大体系结构模式中的一个关键体系结构模式。
If you graph the frequency of various possible results, it's possible to see a pattern of peaks at random-looking series and valleys at the ones that chance would seem to disfavor.
如果用图表画出不同可能性结果的频率，你可能会看到一种模式，貌似随机的序列处于峰值，那些碰巧看上去不太受人喜欢的序列位于谷底。
Read the article The value of applying the business glossary pattern in SOA in this series for a product-neutral description of the business glossary pattern.
阅读本系列 中的文章 “在SOA 中应用业务术语表模式的价值”，了解业务术语表模式的背景知识。
Part 1 of this series lays out the picture of the model-driven and pattern-based development paradigm.
本系列第1部分描绘出模型驱动和基于模式的开发范例的全景。
This pattern generally requires that a single versioning strategy be chosen, comprised of a series of rules and conventions that essentially become governance standards.
该模式通常需要选择统一的版本控制策略，它包含一组可以转变为治理标准的规则和习惯。
Even though the outcome of each individual pattern is random, the outcome of a series of patterns is consistent (statistically reliable).
即使每个模式的结果是随机的，一系列模式的结果则是持续一致的(有可靠的统计数据证明这点)。
Part 1 of the ESB article series identified the ESB as an architectural pattern in SOA; that is true, but not precise.
ESB文章系列的第1部分指出ESB是SOA中的架构模式；这是对的，但是不准确。
This is often achieved by the introduction of the Service Integrator pattern (Part 1 of this series — also see Resources).
这常常通过引入服务集成器模式来实现(本系列的第1部分——同时请参阅参考资料)。
The fifth and last book in the series is a book about patterns and pattern languages.
第5卷也是本系列的最后一卷书，是关于模式和模式语言。
In Part 3 of this series, we applied the WS response template pattern to a UML model of the catalog service.
在本系列的第3部分，我们将WS响应模板模式应用到了Catalog服务的uml模型。
The next article in this series will show how to apply the WS Response Template pattern to the Catalog Service model (see Resources) to produce a more flexible and client-friendly interface.
本系列的下一篇文章将说明如何将WS响应模板模式应用于Catalog服务模型（请参阅参考资料），以得到一个更为灵活的客户机友好接口。
In article 2 of the series, we describe a recipe for creating a pattern solution for the OTMPS, using patterns for e-business.
在系列中的第2篇文章中我们描述了一个OPMPS的模式解决方案的实现，利用模式来实现电子商务。
The first two transactions are the ones between the Stand-alone Reference and the component named Invoker, whose pattern is described in Part 1 of this series.
前两个事务是Stand-aloneReference与名为Invoker的组件之间的事务，其模式已在本系列的 第 1部分中描述过了。
Part 1 of this series describes how the Enterprise Service Bus (ESB) architectural pattern fits within the IBM SOA foundation and how the ESB relates to other parts of the foundation.
本系列的第1部分描述了企业服务总线(esb)体系结构模式如何适应IBMSOAFoundation，以及ESB与Foundation的其他部分如何相关。
This pattern of components is discussed in more detail in the third article in this series, "Designing composite applications: Design patterns."
本系列第三篇文章“设计复合应用程序：设计模式”详细讨论了这种组件模式。
In Part 1 of this series we introduced a design pattern for grid computing on Azure and in Part 2 we wrote the code for a fraud scoring grid computing application named fraud Check.
在本系列的第1部分，我们介绍了在Azure上进行网格计算开发的设计模式，并在第2部分，我们编写了一个欺诈评分(fraud scoring)网格计算应用程序，命名为fraudCheck。
The series discusses the ESB in abstract terms and avoids product specifics; that is, this series is not about the IBM WedSphere ESB product or any other instances of the ESB pattern.
本系列用抽象的术语讨论esb并避免讨论产品细节；也就是说，本系列不讨论IBMWedSphere ESB产品或esb模式的任何其他实例。
In the previous article in this series, you constructed an existing MVC pattern; now you can apply a web services architecture on top of it.
在本系列前一篇文章中，您已经构建了一个已有的MVC模式；现在您就可以在这个模式的基础上应用Web服务体系结构了。
In this tutorial, Part 2 of the series, we discuss how you can leverage your own custom pattern implementations in Rational Software Architect to automate the design of an SOA solution.
在本教程中，系列的第2部分，我们将讨论您如何能够利用Rational Software Architect中您自己的定制模式实现来自动地设计SOA解决方案。
Part 1 of this brief series on effective testing built a FindBugs plugin to find a trivial bug pattern, that of calling System.gc .
这一简短系列的第1部分介绍了如何进行有效测试，它构建了FindBugs插件来查找一个简单的bug模式(只需调用System . gc即可)。
A common DSL pattern identified in Fowler's book is called fluent interface, which he defines as behavior capable of relaying or maintaining the instruction context for a series of method calls.
Fowler的书中确定的一个公共dsl模式叫作连贯接口，他将其定义为能够为一系列方法调用中转或维护指令上下文的行为。
Similarly, classes using the Template Method pattern contain a series of steps, and some are left blank.
类似地，采用TemplateMethod模式的类也包含一系列的步骤，而其余的则留空。
In field practice, a subsurface is mapped by arranging a series of wave-train sources, such as small dynamite explosions, in a grid pattern…
第二句话对解释进行总的说明：“在实地作业中，通过将一系列波列源，诸如小规模炸药爆炸，排列成一个网格模式，从而将地下层面标绘出来。” 接下来是“地震反射法”的详细过程。
Each corresponds to a series of musical notes; one is selected when the player focuses on it, since his or her brain triggers a unique pattern of electrical impulses for each button.
每个按钮对应着一系列的音符；当奏乐者看着某一个按钮时就会选中它，这是因为他或她的大脑对于每一个按钮会触发一组独特的电子脉冲模式。
What emerges from the collective is not a series of critical individual actions but a multitude of simultaneous actions whose collective pattern is far more important.
从群体中涌现出来的不再是一系列起关键作用的个体行为，而是众多的同步动作。 这些同步动作所表现出的群体模式要更重要得多。
By going through the series of exercises that follow, you will be able to learn by example and see how to generate artifacts using the MVC design pattern.
通过下面一系列练习，您将可以通过示例了解并掌握如何使用MVC设计模式生成相应的构件。
应用推荐