设置服务请求程序。
Step 4 must be performed by the service requester.
步骤4必须由服务请求程序执行。
Step 2: Secure the Web service requester to pass the LTPA token.
步骤2：配置Web服务请求者以传递ltpa令牌。
Means to invoke both, service provider and service requester.
能调用服务请求者和提供者两者的手段。
Service requester - The client, which binds to a particular service.
服务请求者？客户机，它绑定到特定的服务。
To enable the Web service requester to pass the LTPA token, do the following
要使Web服务请求者传递LTPA令牌，需要执行下列步骤
A SaaS service requester incorporates data and functionality from other services.
SaaS服务请求者合并来自其他服务的数据和功能。
The service requester needs to set this property value before invoking the service.
服务请求者需要在调用这个服务之前设置这个属性值。
The service requester interacts with the service realization to achieve a business task.
服务请求者通过与服务实现进行交互来完成业务任务。
In all the scenarios we introduced, one service requester was invoking one service provider.
在我们介绍的所有场景中，都是一个服务请求者调用一个服务提供者。
A service provider can be connected to a service requester if their WSDL descriptions match.
如果WSDL描述匹配，服务提供者就可以连接到服务请求者。
To do so, the service provider must have a way to communicate back with the service requester.
要实现这一点，服务提供者必须有返回途径与服务请求者进行通信。
Management of the life cycle of a communication between service requester and service provider.
服务请求者与服务提供者之间的通讯生命周期管理。
The binding from the service requester to the service provider should loosely couple the service.
服务请求者到服务提供者的绑定与服务之间应该是松耦合的。
What are requirements that the service requester must satisfy to invoke the service successfully?
服务请求者必须满足那些要求才能正确地调用服务？
Let's see how to make that happen using a service provider and service requester in a simple example.
我们来看一下在一个简单的示例中如何用服务提供者和服务请求者来实现多语言web服务。
Caches on the service provider side or the service requester side are not applicable for this pattern.
服务提供端或服务请求端的缓存不适用此模式。
This article will focus on the horizontal arrow (bind) from the service requester to the service provider.
本文将重点讲解从服务请求者到服务提供者的水平箭头(绑定)。
The service requester and the mediation flow component itself did not change at all, hence no programming was involved.
服务请求者和中介流组件本身根本不会发生改变，因此不涉及到编程工作。
We showed how to develop service requester-side artifacts and how to integrate the CICS services with the workflow.
我们说明了如何开发服务请求者端构件以及如何将CICS服务与工作流集成在一起。
In web services terminology, the observer is initially the service requester and the subject is initially the service provider.
在Web服务术语中，最初观察者是服务请求者，目标是服务提供者。
Mediation flows -- perform mediation on request and/or response messages between the service requester and the service provider.
中介流——通过中介传递请求和/或服务请求者和服务提供者之间的响应消息。
Instead of adding a new service provider to the scenario, which we had done in Part 4, we added an additional service requester.
此部分没有向场景添加新服务提供者(如第4部分中所述)，而添加了一个额外的服务请求者。
Part 5 investigated a scenario in which we switched between protocols supported by the service requester and the service provider.
第5部分讨论了在服务请求者和服务提供者支持的协议之间进行切换的场景。
The development of the server-side Web service implementation and the client-side Web service requester can't proceed in parallel.
服务器端的Web服务实现的开发和客户端 Web 服务请求程序的开发不能并行进行。
The third approach assists in the creation of a COBOL-based service requester, which is essentially dealing with a new application.
第三种方法帮助创建基于COBOL的服务请求者，它本质上是创建一个新的应用程序。
The communication between service requester and service provider sets up the basic relationship in a web service: request and response.
服务请求程序和服务提供程序之间的通信建立了Web 服务中的基本关系：请求和响应。
If the service is redeployed to a different server, the service requester can use UDDI to find the new location and cache it for future use.
如果服务重新部署到不同的服务器当中，服务请求者能够使用UDDI发现新的位置并将它缓存以备将来使用。
The service requester and provider are not aware the messages are flowing through the ESB and know nothing about the routing or logging in the ESB.
服务请求程序和提供程序不知道消息流经esb，也不知道在esb中路由或记录的任何消息。
A WSDL file simply tells a client how to access the services; it has no provisions for the service provider to find out about the service requester.
WSDL文件简单地告诉客户端怎样访问这个服务，但没有告诉服务提供者怎样找到服务请求者。
应用推荐