过程、实例与消息的管理接口。
你会发现，随着你SOA系统的成长和变更，你会需要针对所有契约制品的版本管理策略：服务接口、消息和数据的模式、策略等。
You will find that as your SOA systems grow and change, you will need to have versioning polices for all contract artifacts: service interfaces, messages and data schemas, policies, etc.
使用者和提供者的服务接口、消息格式、范围和服务质量的区别可以通过中介予以解决和消除。
Differences in the consumers' and providers' service interfaces, message formats, scope, and qualities of service can be bridged and facilitated by mediations.
也就是说，应用程序可以不完全单独遵从来自服务接口定义的消息实例。
In other words, an application cannot completely defer to a message instance from the service interface definition alone.
该接口处理任何类型的消息（对象类）。
消息传递接口(MPI)管理此缓冲区。
当应用程序的UI逻辑和业务逻辑拆分开时，SOA支持通常可以在业务逻辑的消息接口上应用，而完全忽略 UI 代码。
Where an application is split between UI logic and business logic, SOA enablement can often be applied at the business logic’s message interface, bypassing the UI code entirely.
该接口允许对消息进行访问，同时提供了其它关于中介细节的操作和属性。
This interface allows access to the message. It also provides other mediation-specific operations or attributes.
服务相关信息通常包括多个相互关联的构件、如服务接口、消息模式、实现代码、使用概要等。
Service-related information typically includes multiple interrelated artifacts, such as service interfaces, message schemas, implementation code, usage profiles, and so on.
超过某个阈值以后，巨量的消息可以推动接口进入单独的服务分类。
Beyond a certain threshold, the sheer volume of messages could push an interface into a separate class of service.
当测试执行时，该用户接口显示消息被发送和接收的测试过程。
As the test was executing, this user interface displayed the test progress as messages were sent and received.
用于构造向服务发送的消息的接口、操作和输入名称。
The interface, operation, and input name are used to construct the message to send to the service.
可以在UI和业务逻辑间引入一个消息接口。
You can introduce a message interface between the UI and the business logic.
如图1所示，通过消息传递接口(mpi)库规范在节点间传递数据。
As shown in Figure 1, the Message Passing Interface (MPI) library specification passes the data between the nodes.
消息队列接口(MQI)中每个调用的功能。
The function of each of the calls in the Message Queue Interface (MQI).
消息队列框架接口包定义框架提供的功能，而消息队列框架实现包提供应用程序特定的实现。
The message queue framework interface package defines the functions the framework provides, while the message queue framework implementation package provides application-specific implementations.
UDDI(通用描述，发现和集成)为发布服务的可用性和发现所需服务定义了一个标准接口(基于SOAP消息)。
UDDI (Universal Description, Discovery, and Integration) defines a standard interface (based on SOAP messages) for publishing the availability of a service and for finding a required service.
这可能是由于目标系统接口无法理解此消息或由于消息导致了目标系统接口内的处理错误而造成的。
This will occur because of the target System Interfaces inability to understand the message or because the message is causing a processing error within the target System Interface.
短消息服务接口的描述如图4所示。
The short message service interface is described as shown in Figure 4.
大型机中间件(如cics和IMS)支持在消息接口中每个事务包含多达32kb的消息。
Mainframe middleware, such as CICS and IMS, supports message sizes up to 32kb per transaction in the message interface.
消息传递接口必须与平台和语言无关。
The messaging interface must be platform- and language-independent.
业务对象编辑器用于描述消息的内容，接口编辑器用于描述如何将消息包装到操作信封中。
The business object editor is used to describe the content of the message, and the interface editor describes how the message is wrapped into an operation envelope.
系统使用一个消息接口和一组数据通路来使处理器彼此通信。
The system USES a messaging interface and a set of data paths that allow processors to communicate with each other.
重构模式的目的在于向现有应用程序添加消息接口——通常为SOA接口，适合作为服务使用，使用WSDL进行描述。
The purpose of the refacing pattern is to add a message interface — typically an SOA interface, suitable for use as a service, described in WSDL — to an existing application.
网络接口，它允许消息生产者和消费者位于不同的地方
Network interfaces, which allow message producers and consumers to be located in different places
中介具有Web服务接口，并接收消息。
WSDL描述指定Web服务的地址、允许的通信机制、接口和消息类型。
The WSDL description specifies the address, allowable communication mechanisms, interface, and message types of a Web service.
访问消息与SIMessage接口。
SOACOE架构师负责定义接口、消息流和非功能需求(nonfunctional requirement,NFR)，以及低级功能需求。
The SOA COE architects are responsible for defining interfaces, message flows, nonfunctional requirements (NFRs), and lower-level functional requirements.
我们仅仅定义ApplicationServer所能够解释和分派到现有接口的消息部分。
We merely defined message parts that Application Server is able to interpret and dispatch onto the existing interface.
应用推荐