eai
美 
英
- 網絡企業應用集成(Enterprise Application Integration)；企業應用整合；美國早期印刷品(Early American Imprints)
例句
Middleware technologies in various forms have been used to close EAI gaps.
各種窗體的中間件技術已經被用于消除EAI差異。
Web services are the best middleware choice for getting EAI applications to communicate with one another.
Web服務是使得EAI應用程序能夠互相傳遞信息的最好的中間件。
You can have the same internal RFID Web service to call up another external EAI application or even another external Web service.
可以使用同一個內部RFIDWeb服務來調用另一個外部EAI應用程序甚至另一個外部Web服務。
Typically, this kind of integration is called enterprise application integration, or EAI.
通常情況下，這類集成被稱為企業應用程序集成或EAI。
It would be costly and time-consuming to customize schemes for mapping business logic between EAI systems and external applications.
對于在EAI系統及外部應用程序之間映射業務邏輯的計劃的定制是浪費時間并且代價昂貴的。
MDM information integration patterns: These patterns are also EAI patterns, however with a clear focus on information integration.
MDM信息集成模式：這些模式也是EAI模式，但是主要關注信息集成。
While some EAI technologies might offer such a model, in other cases, a custom solution is required.
雖然有些EAI技術可能提供了這樣的模型，但在其他的情況下，需要自定義解決方案。
If the EAI technology does not directly support the required standards, a Service Gateway component can be added.
如果EAI技術不直接支持所需的標準，就需要添加一個網關組件。
OBAs remind me of the old school EAI, enterprise application integration technology while the entire world is moving to an SOA architecture.
OBA讓我想起來老古董EAI——企業應用集成技術，但是現在整個世界都在向SOA轉變。
EAI solutions pull data from different sources, aggregate and transform the data to be used in different contexts.
EAI解決方案從不同來源抓取數據，聚合并轉換數據以被不同的上下文使用。
Support can be provided for web services standards and Enterprise Application Integration (EAI) middleware.
并能使其提供對Web服務規范和企業應用集成（EnterpriseApplicationIntegration，EAI）中間件的支持。
In a sense, they cover the ground previously owned by Enterprise Application Integration (EAI) proprietary platforms.
從某種程度上，它們涵蓋了曾經由私有的企業應用集成（EAI）平臺涉及的領域。
Web services don't solve the EAI problem in and of themselves.
Web服務并沒有解決它們自身的EAI問題。
Enterprises are increasingly turning to a service-oriented approach towards implementing an EAI.
企業正逐漸轉為使用面向服務的方法來實現EAI。
They may form the basis for either the HLDM, or realization of the HLDM within the EAI backbone and external interfaces.
它們為HLDM或在EAI中樞和外部接口內的HLDM的實現形成基礎。
Spring Integration is an API from the creators of the Spring Framework that's geared towards Enterprise Application Integration (EAI).
SpringIntegration是Spring框架創建的又一個API，面向企業應用集成（EAI）。
EAI involves integrating various applications that support different technology interfaces.
EAI涉及對支持不同技術接口的各種應用程序的集成。
The investment required can depend on the existing level of use of EAI, and on the extent of any additional custom development.
投入的多少依賴于所使用EAI的現有級別，也依賴于附加定制開發的工作量多少。
Thus in EAI, "integration" includes both semantic and non-semantic actions, and an "integration layer" can perform both.
因此，在EAI中“集成”包括語義和非語義操作，“集成層”可以執行這兩類操作。
Each SOA has a different set of services that are provided to EAI applications hosted by IBM partners.
每個SOA都具有一組不同的向IBM合作伙伴所承載的EAI應用程序提供的服務。
Typically, EAI is seen as a costly, complex and technically demanding undertaking with no room for errors.
一般來說，EAI被視為昂貴、復雜和技術要求苛刻的工作，不能有絲毫錯誤。
Unlike EAI, Web services offer a wide range of standards to bridge applications with external service providers.
與EAI不同，Web服務提供了廣泛的標準，為應用程序與外部的服務提供者之間搭建了橋梁。
What this means is that you could use multiple SOAs to bridge the gaps between EAI applications or systems.
這意味著您可以使用多重SOA來消除EAI應用程序之間的或系統之間的差異。
Secondly, we introduce four famous EAI management s' architectures and point out their excellence and shortcomings.
其次，介紹了四種具體的企業應用集成系統的體系結構，分析了它們的優點和缺點。
An entity could be either a standalone publisher or an EAI application interface with another publisher.
實體可以是一個獨立發布者，也可以是與另一個發布者通過接口交互的EAI應用程序。
Are open standards required, or can appropriate interoperability be achieved through EAI middleware?
是否需要開放標準？或者是否可以通過EAI中間件來實現適當的互操作性？
This makes them an extremely attractive (and vendor-independent) alternative to EAI implementations.
這讓它們相對于EAI實現成為了極具吸引力的（并且獨立于供應商的）替代品。
The aim of EAI is to eliminate enterprise information isolated island and to link and optimize the data flow and the management flow.
企業應用集成（EAI）的目標是消除企業信息孤島，對數據流程、管理流程進行全面的連接與優化。
Security protocols for EAI applications are more mature those for Web services.
EAI應用程序的安全協議相對于Web服務要成熟的多。
This module explains the fundamental concepts behind using BizTalk Server for EAI within your company.
第1單元介紹在公司中使用BizTalkServer實現EAI所涉及的基本概念。
Without the standards, it is difficult to integrate multi-vendor EAI applications over the Internet.
沒有標準，在互聯網上整合多商家的EAI應用程序是非常困難的。
The EAI application then searches the requested items in a database.
然后EAI應用程序在數據庫中搜索請求的項目。
The EAI approach limits the scope of efforts to integrate EAI systems with external applications.
EAI解決方案限制了使用外部應用程序來集成EAI系統的范圍。
At its simplest, EAI enables the transfer of information between applications.
簡單來說，EAI實現了軟件之間的信息傳輸。
They offer open industry standards to bridge the platform-dependent EAI systems.
它們提供了開放的行業標準，為獨立平臺的EAI系統搭建了橋梁。
Standards for implementing EAI are virtually non-existent.
實現EAI的標準事實上是不存在的。
This model will also show realization of the HLDM within interface mechanisms such as an EAI hub or backbone.
該模型還將顯示帶有接口機制（如EAI集線器或干線）的HLDM的實現。
The fundamental premise behind EAI is that the integration is performed on the back end, using either a hub and spoke or bus architecture.
EAI蘊含的基本假定是，集成在后端進行，使用不是星形結構（hubandspoke），就是總線架構。
Now, let's suppose two SOAs are needed to bridge two EAI applications.
現在，我們假設需要兩個SOA連接兩個EAI應用程序。
If so, then you have a legacy integration issue, often called Enterprise Application Integration (EAI) issue, on your hands.
如果這樣的話，您就有舊系統的集成問題，通常稱為“企業應用集成（EAI）”問題。
