Low level connectivity - SIMM level 2.
低层连接性-SIMM级别2。
SIMM has a much broader scope than this.
SIMM的范畴远比此宽泛。
Hub-based integration (basic) - Lower SIMM level 3.
基于Hub的集成(基本)-较低的SIMM级别3。
Hub-based integration (advanced) - Upper SIMM level 3.
基于Hub的集成(高级)-较高的SIMM级别3。
The presence of a hub marks the beginnings of SIMM level 3.
hub的出现标志着SIMM级别3的开始。
The SIMM is grouped into seven maturity stages or levels.
SIMM 划分为七个成熟度阶段或级别。
These are the same integration patterns we were using in SIMM level 3.
这些都与我们在SIMM级别3中使用的集成模式相同。
The SIMM and AstraZeneca centre was operational from the end of June 2010.
该中心从2010年6月底开始运营。
To check the performance of a Web service SIMM, you need to develop in the following order.
要检查Web服务SIMM的性能，需要按照以下顺序进行开发。
SIMM does not advocate or require a linear movement from one maturity level to the next.
SIMM并不提倡或要求从一个成熟度到下一个成熟度的线性迁移。
Let's recall the traditional hub and spoke integration architecture (Figure 1) of SIMM level 3.
让我们回忆一下SIMM级别3的传统拓扑集成架构(图1)。
To help you accomplish this, IBM provides a technique called Service Integration Maturity Model (SIMM).
为了帮助您完成此任务，IBM提供了称为服务集成成熟度模型(Service Integration Maturity Model, SIMM)技术。
SIMM is a maturity model that has been set-up in the CAT tool and used by hundreds of clients all over the world.
SIMM是一个在CAT工具中建立起来的成熟度模型，全世界有几百个客户使用这个模型。
SIMM provides multiple results across different dimensions of assessment; as not all dimensions will score the same
SIMM提供不同评估维度上的多个结果，因为不是所有维度都将得到相同的评分。
If you remember from the beginning of the article, the four key capabilities that we introduced in SIMM level 4 were.
回忆一下本文开头的内容，我们在SIMM级别4中引入的4个关键功能包括。
Consider two scenarios on supplementing the SIMM with Web services built with process activities from repositories.
考虑以下两个使用通过存储库中的流程活动构建的Web服务对SIMM进行补充的场景。
This is mostly because at SIMM level 4, you are focused only on exposing requests over standardized protocols and transports.
主要原因是因为在SIMM级别4，您只关心通过标准化协议和传输公开请求。
Now, let's remind ourselves how that architecture is amended to expose mature enterprise services (Figure 2) in SIMM level 4.
现在，让我们回想一下这个架构是如何转变为在SIMM级别4上公开成熟的企业服务(图2)。
Standardized exposition: the connectors on the requestor side of the hub have disappeared in the SIMM level 4 diagram (Figure 2).
标准化公开：位于集线器(hub)的请求一方的连接器在SIMM级别4图中消失不见(见图2)。
Keep in mind this is not the full SIMM or OSIMM assessment but an abbreviated self-assessment based on OSIMM and SIMM content.
记住，这不是完整的simm或osimm评估，而是基于OSIMM和SIMM内容的简略的自我评估。
There is plenty of capital available for water infrastructure, reckons Ian Simm of Impax Asset Management, an investment firm.
Impax资产管理公司伊恩。西姆认为可用来进行水基础设施的资金很充足。
The analyzer should determine that the Web service SIMM consisting of the combined activities won't result in system overloads.
分析器应该确定由组合服务组成的Web服务不会导致系统过载。
SIMM provides the detail content to both understand the differences as well as the blueprint for bringing about the business outcome.
SIMM提供了一些细节内容，有助于理解这几者之间的区别和实现业务成果的蓝图。
Organizations start building this capability in SIMM level 2. Initially, they write connectivity code into their backend applications.
各组织纷纷开始在SIMM级别2构建这种能力。起初，它们将连接性代码写入其后端应用程序。
Note: Even though we're only doing one-to-one connectivity here, we can't describe this as "point-to-point"(for example, SIMM level 2).
注意：虽然我们这里进行的是一对一的连接，但是我们并不能将此描述为 “点对点”（比如，SIMM级别2）。
I believe it's not even possible to have that much RAM, or maybe it is, but then you must have a huge simm module of about 8gb RAM.
我相信根本就没可能会有那么多的内存，就算有，那它你必须有高达8g的内存模块。
The fact that there is a hub present at all suggests this is SIMM level 3 since we already have some opportunity to re-use the integration.
这里有hub出现的事实恰恰表明了这是SIMM级别3，因为我们已经有了某种机会来重用这个集成。
You can choose from alternative workflows that you can use to create a Web service performing a single function of supplementing the SIMM.
可以从备选工作流中选择能够用于创建Web服务的项，以执行补充SIMM的单个功能。
That is where the greatest benefits are drawn from process automation and why it is ideally targeted at SIMM level 5 to build on the matured services of level 4.
这就需要流程自动化所带来的种种好处，这也是为什么SIMM级别5最好是构建在级别4的成熟服务上的原因。
Developing Web services to supplement the SIMM requires collaborative efforts from a team of developers, testers, system administrators, and potential users.
为了开发Web服务来补充SIMM，需要由开发人员、测试人员、系统管理员和潜在用户组成的团队进行协作。
应用推荐