Many of them had deployed multiple successful projects, but most of those projects were focused on just one integration problem.
它们中有许多已部署了多个成功的项目，但这些项目大多只关注于一种集成问题。
Ultimately, this creates a classic integration issue: the problem of management integration.
这样最终产生了典型的集成问题：管理集成问题。
Behavior that crosscuts a number of classes poses a particular problem for integration tests.
横切数个类的行为给集成测试带来了一个特定问题。
Flow allows developers to create integration flows they way they think about solving the problem.
流允许开发人员通过自己思考解决问题的方式来创建集成流。
The other problem that cropped up by placing a priority on integration was functionality.
由于将优先权赋予集成而产生的另一个问题是功能性问题。
However, the integration is still a problem that needs to be solved.
不过，如何集成依然是一个尚待解决的问题。
The answer, according to PwC, is Semantic Web techniques. PwC believes that the Semantic Web offers a practical way to address the problem of large-scale data integration.
根据普华永道的报告，问题的答案是语义网技术，普华永道相信，语义网为解决大规模的数据整合问题提供了一种实际可行的方法。
As we previously mentioned, SDO isn't the only technology that proposes to resolve the problem of data integration in distributed applications.
前面已经提到，SDO并不是提出解决分布式应用程序中数据集成问题的惟一技术。
The problem with the European model, in hindsight, is that the initial aim of limited economic integration developed its own momentum.
事后再看欧洲模式的问题，却是在于起初进展缓慢经济一体化目标逐渐成为主流。
Given that ETL is just a small part of EII, you can imagine the scope and the severity of the point-to-point integration problem.
考虑到ETL仅仅是EII的一小部分，所以您可以想象端对端集成问题的范围和严重性。
This is a classic integration problem: one application has data that another one needs.
这是一个典型的集成问题：一个应用程序有数据，而另一个应用程序需要数据。
An enterprise requires the ability to differentiate and design service artifacts appropriate for specific styles of integration required to solve a particular integration problem.
企业必须能够区分和设计适合解决特定集成问题所需的集成样式的服务构件。
Unfortunately, integration pain is often the smallest problem.
而更为不幸的是，集成之痛还只是最小的问题。
To get around this problem, the Universal Description Discovery and Integration (UDDI) specification describes a Web service that is a directory, like a phonebook, for locating other Web services.
为了解决这个问题，统一描述、发现和集成(Universal Description Discovery and Integration,UDDI)描述了一种Web服务，它是一个类似于电话簿的目录，用于查找其他的Web服务。
If an error occurs that is too complex to fix, you can click a button to export problem details into a ZIP file, which you can send to Integration Developer for detailed analysis.
如果发生太复杂而无法修复的错误，您可以单击一个按钮将问题详细信息导出到ZIP文件，然后可以将该文件发送到IntegrationDeveloper以进行详细分析。
Tracing has been enhanced to capture information which can then displayed later in the test client from WebSphere Integration Developer for analysis and problem determination.
跟踪功能已得到增强，现在可捕获稍后可在WebSphereIntegrationDeveloper中的测试客户端中显示的信息，以用于分析和问题确定目的。
If there are a large number of these, resolve the underlying problem (missing nicknames, E-mail addresses, and so forth), and then rerun Apply Resource Mapping from the ClearQuest Integration TAB.
如果有大量这样的用户，就要确定这个潜在的问题(丢失别称、电子邮件地址，等等)，然后从ClearQuestIntegration页签重新运行ApplyResourceMapping。
Consider also the n(n-1) integration problem.
同样考虑n（n-1）集成问题。
As Ron sees it, the problem comes down to communication and the way in which developers typically work in traditional integration projects.
如同Ron所看到的，问题在于通信和传统集成项目中开发者典型的工作的方式。
One problem with Web service APIs is that they require integration with an application to take advantage of the cloud storage.
Web服务APIs 的一个问题是，它们需要与应用程序集成，以利用云存储。
In this age of mergers and acquisitions, a common problem faced by solution architects is the integration of product lines in a manner that provides a consistent user experience.
在并购（Mergers and Acquisitions，M&A，兼并与收购）时代，我们常常无法回避的一个问题是：如何在不影响用户体验的前提下完成产品线集成。
The basic problem is the attempt of developers to replace a middleware solution with point to point web services as an integration approach regardless of the usage context.
基本问题是开发人员在不考虑使用环境的情况下尝试使用点到点web服务作为集成方法替代中间件。
An integration pattern has been created to use this new function and solve the IDoc routing problem. The solution has two parts.
一个集成模式已被创建，以便使用这个新功能并解决idoc路由问题。
He Outlines several prescriptive recommendations providing a holistic solution to a data integration problem for an enterprise.
他描述了几种规范的推荐纲要，为企业实现数据集成提供了整体的解决方案。
It supposed to provide an answer to the problem of growing volumes of data (2d and 3d) and integration to other sources of data. The following description is from Actify Centro website.
旨在解决日益增长的数据量(包括2d和3d)和与其他数据来源集成的问题。
A preferred way to resolve this problem is to use document-literal style SOAP message with an assumption that both "RPC" and "document" style are allowed for this particular integration.
解决此问题的一个首选方法是，使用Document - literal样式的SOAP消息，并假定对于这个特殊集成，“rpc”和“Document”样式都是允许的。
The problem you are hitting is most likely a default value on all foreign queue definitions on the service integration bus when the MQ Link is being used to transmit messages to a WebSphere MQ queue.
您所碰到的问题很可能是，当使用MQLink将消息发送到WebSphere MQ队列时服务集成总线上所有外来队列定义的缺省值。
You could ask to run automated builds with cruise control after an integration problem goes unnoticed.
您可以在集成问题被忽视之后，请求运行带有巡航控制的自动化版本。
Although the integration points were described as three separate scenarios, a typical problem-isolation scenario would seamlessly blend all these scenarios together in various combinations.
尽管这里通过三个单独的场景介绍集成点，但是典型的问题隔离过程往往以各种组合方式把这三个场景无缝地融合在一起。
Although the integration points were described as three separate scenarios, a typical problem-isolation scenario would seamlessly blend all these scenarios together in various combinations.
尽管这里通过三个单独的场景介绍集成点，但是典型的问题隔离过程往往以各种组合方式把这三个场景无缝地融合在一起。
应用推荐