服务请求者通过查找服务代理者那里的被发布服务登记记录来找到服务；
Service requesters find services by searching the Service broker's registry of published services;
请求者实体将用请求者代理使用Web服务的功能。
A requester entity USES the Web services functionality with a requester agent.
这个方法不仅让我们无需单独生成服务代理，而且服务和服务消费者的实现都可以使用同样的服务接口。
The usage of this approach not only allows us to bypass service proxy generation, but also to use the same interfaces for both service and client implementation.
只有那些不得不向提供者的使用者公开的服务才需要有服务代理或请求处理程序。
Only those services that have to be exposed to the consumers of a provider need have a service proxy or a request handler.
在这样的情况下，网关代理服务将假设为最终接收者角色，并且返回一个空结果(不是一个错误)给发送者。
In such a case, the gateway Proxy service would assume the role of the ultimate receiver and return an empty result (not a fault) to the sender.
业务服务所有者将决定服务提供什么样的功能——而不用管服务是怎么实现的--他或她是服务设计者在业务方面的代理人。
The business service owner will decide what functionality the service provides, no matter how it is implemented – he or she is the service designer’s “proxy” to the business side.
服务代理从其可用提供者列表中选择服务提供者。
The service proxy selects a service provider from its list of available providers.
服务器端消息接收者可作为客户端的代理，调用实际的用户定义的服务方法。
The server-side message receiver functions as a proxy for the client, calling the actual user-defined service method.
客户端应用程序调用通用代理(由它调用服务代理)来调用服务提供者。
The client application calls the general proxy that calls the service proxy to invoke the service provider.
这个体系架构，如下图1所示，需要三个服务角色：一个服务提供者、一个服务客户和一个服务代理。
This architecture, as shown below in Figure 1, requires three service roles: a service provider, a service client, and a service broker.
客户机不再直接调用服务提供者，而调用代理中的服务代理，该服务代理将对服务提供者进行调用，如图7所示。
The client no longer invokes the service provider directly, but rather invokes a service proxy in the broker, which in turn invokes the service provider, as shown in Figure 7.
在这种场景下，服务消费者查找注册中心得到代理的位置，或许根据服务消费者当前的位置以及它使用的通信协议通信。
In this scenario, the Service consumer pings the registry to find out where the proxy is, perhaps based on where the Service consumer is currently located and with what protocols it can communicate.
ESB提供了第三种选择，承诺在支持使用者动态地一次性绑定到服务代理的同时，仍然能够通过代理使用多个提供者和选择新的提供者。
An ESB offers a third choice, a compromise enabling a consumer to dynamically bind to a service proxy just once and yet still be able to use multiple and future providers using the proxy.
或者，服务代理可以封装业务逻辑，以根据已建立的服务级别协议或业务规则改变服务提供者的选择。
Or perhaps the service broker would encapsulate business logic that varies the selection of service providers based on established service level agreements or business rules.
服务代理调用所选提供者的端点。
更准确地说，服务请求者向服务代理提交请求，服务代理从服务提供者那里找到正确的服务。
More specifically, service requesters submit a request to a service broker, which finds the right service from a service provider.
本小节中我们描述了为POJO创建ESB服务代理的主要步骤，开发者可以按照这些步骤来操作。
Here we describe the major steps that a developer would follow to create the ESB Service Proxy to a POJO.
服务提供者可以使用各种技术来将自已声明或注册给服务代理。
The service providers can use various technologies to declare or register themselves to the service broker.
为服务代理的接口建模使其模型与服务提供者定义的WSDL操作相匹配很重要。
It's important to model the interface of the service proxy to match the WSDL operations defined by the service provider.
该图标识了服务请求者，服务请求者可能通过遵循 JAX-RPC 的代理，使用提供具有所显示签名的发布操作的服务。
The figure identifies a service requestor that uses, perhaps via a JAX-RPC compliant proxy, a service that offers a publish operation with the signature shown.
这很好地拆分了服务提供者与使用者，但它要求服务提供者与使用者对特定的服务代理有清晰的了解。
This nicely decouples the service provider and consumer, but it requires them to have clear knowledge of the particular service broker.
严格来说，把代理模式服务作为现存服务的部署是不正确的，因为当代理模式服务被设置时，没有对最终接收者的引用。
Strictly speaking, it is not correct to refer to proxy mode services as deployments of existing services; there is no explicit reference to the ultimate receiver when a proxy mode service is set up.
注册是一种服务代理，它是在UDDI上需要发现服务的请求者和发布服务的提供者之间的中介。
The registry is a service broker, an intermediary between the requester that needs to find services and the service providers that publish their availability on UDDI.
当两者配合使用时，JON服务器、代理和模块提供了端到端的应用管理方案。
When used together, JON server, agents, and modules provide end-to-end application management solution.
该架构涉及了服务提供者、代理，和请求者之间的关系。
The architecture involves a relationship between service providers, brokers, and requesters.
服务提供者将自已注册到服务代理，而服务使用者则会在服务代理中寻求自已需要的服务。
The provider registers itself to the broker, while the consumer looks up desired services from the broker.
服务在提供者、使用者和代理之间形成契约，它们可以为随需应变交互构建自己的生态系统。
Services form a contract among suppliers, consumers, and brokers who can build their own ecosystem for on demand interaction.
服务代理是服务提供者和服务请求者之间的中介 -- 服务本地化，代理托管方案等等。
A service broker is an intermediary between a service provider and a service requestor -- for service location, brokered trust arrangements, and so on.
使用者使用代理的URI调用服务。
合并代理可能对所合并的提供者（连锁酒店）的服务使用者提供一组不同的代理服务（旅行）。
The merged brokers may have a different set of broker services (travel) for service consumers to merged providers (hotel chains).
应用推荐