The service tier is designed as a service facade.
服务层被设计为服务facade。
The following functions are desirable in a REST-style Web service facade component
在REST 样式的Web服务Facade组件中需要以下功能
All rules are wrapped in a service facade interface, with each rule exposed as a method.
将所有的规则封装在服务facade接口中，每个规则作为一个方法公开。
As shown in Figure 2, the rules are defined in BRBeans and are accessed through a rule service facade.
如图2所示，规则都定义在BRBean中并通过facade规则服务进行访问。
There are many ways to logically partition and package the rules as part of service facade. For example.
这里有许多方法来将规则逻辑分割并打包成服务facade的部分。
All application specific rules are wrapped in a service facade, with each rule being exposed as a method.
所有应用特定的规则都封装到一个服务代理中，每个规则作为一个代理提供的方法。
These kinds of steps can be implemented by direct invocation of components that do not have a service facade.
此种类型的步骤可以通过直接调用不具有服务Facade 的组件来实现。
Figure 10 shows the properties of the invoke activity after connecting to the rule service facade created earlier.
图10展示了在连接先前创建的规则服务facade之后的调用行为的属性。
Therefore, a Web service facade component enables application developers to customize the URL representing a resource.
因此，Web服务Facade组件允许应用程序开发人员自定义表示资源的URL。
In this section you will use a more sophisticated pattern called Service Facade to WebSphere MQ: request-response.
在这个小节中，您将使用更高级的模式Service Facade toWebSphereMQ： request - response。
Congratulations! You have successfully deployed and exercised the Web service facade to a WebSphere MQ queue pattern!
祝贺您！您已经成功部署并测试了Webservice facade toaWebSphereMQqueue模式！
Rule service interface: Once the service facade is implemented, a service interface and binding elements are generated.
规则服务接口：一旦实现了服务facade，就生成了服务接口及绑定元素。
Rule service facade implementation: The above rule implementation can be invoked using a rule service facade, as shown in Listing 5.
规则服务facade的实现：可以通过使用规则服务facade来调用上面的规则实现，如清单5所示。
Congratulations! You have successfully created, deployed and exercised the Service Facade to WebSphere MQ: request-response pattern.
祝贺您！您已经成功地创建、部署和测试了Service Facade toWebSphereMQ：request - response模式。
This service facade approach provides a loosely coupled rule access mechanism that fits well with the web services programming model and process modeling.
该服务facade解决方案提供松耦合的规则访问机构，它可以非常好地适合于Web服务编程模型及流程模型。
You will also deploy an instance of the Service Facade to WebSphere MQ: request-response pattern, which also writes Web service requests to a WebSphere MQ queue.
此外，您还将部署Service Facade toWebSphereMQ:request-response模式的一个实例，它同样将Web服务请求写到 WebSphere MQ 队列。
In the OTMPS service facade, we wrapped all rules in a single service (OTMPSRules), where each rule is exposed as a method of the service, as shown in Listing 3.
在OTMPS服务facade中，我们将所有规则都包装在了一个单独的服务(OTMPSRules)中，其中将每种规则都发布成该服务的方法，如清单3所示。
To create an instance of the Service Facade to WebSphere MQ: one-way with acknowledgment pattern, click on create New instance at the bottom of the pattern specification.
要创建Service Facade toWebSphereMQ：one - waywith acknowledgment模式的一个实例，在模式说明的底部单击CreateNewInstance。
As part of the OTMPS pilot, we implemented a simple rules service framework, which consists of a rules service Facade and a rule Engine Selection (for details see the 5th article in this series).
作为试验性项目OTMPS的一部分，我们实现了一个简单的服务器框架，它包含一个规则服务代理和一个规则选择引擎(详细信息请参阅系列文章中的第5篇)。
Each rule service facade operation creates an instance of the TriggerPoint class and invokes the trigger function on that class with the reference to invoker, input parameters, and the rule name.
每种规则服务facade操作都创建了triggerpoint类的实例并通过使用对于调用的引用、输入参数及规则名称来调用该类的trigger函数。
In this article, we describe Business Rules Beans (BRBeans) framework and the implementation of a rule service facade. In addition, we illustrate an example through the following step-by-step methods.
在本文中，我们描述了业务规则Bean (Business Rules Beans,BRBeans)的框架及规则服务外观的实现。
Another option is the bundling of several related services into coarser-grained service definitions, which is a variation of the facade pattern.
另一种选择就是将一些相关的服务捆绑成粗粒度的服务定义，这是门面模式的变种。
To generate the enterprise service definition from the Facade bean.
要从门面Bean生成企业服务定义，您需要遵循下列步骤。
Modularity patterns: Separated Interface and Plug In, Service Locator, Event Aggregator, facade.
模块化模式：分离界面和插件、服务定位、事件聚合、外观模式。
A facade pattern provided by JPA Manager Beans, which is used in a service approach.
JPAManagerBeans提供的外观模式，用于服务方式。
It might be interesting to define a service provider interface for an id creation service or function that the facade can optionally call to create valid IDs.
为ID创建服务或者函数(facade可以调用该函数创建有效的ID)定义服务提供者接口，这可能是很有趣的。
Retrieves the data from the facade interface of the chart data service -- which could be an existing service or solution asset -- and is exposed by the RPC adapter.
从图表数据服务的facade接口检索数据 ——该服务可以为现有服务或解决方案资产 ——并由RPC适配器公开。
Once the facade interface has been implemented, the final step is to expose it as a Web service.
一旦已经实现了facade接口，最后的步骤是使其作为Web服务公开给外部。
In this case, the application object ACTS as a facade for data in a Web service.
在这个示例中，该应用程序对象用作Web服务中数据的Facade。
Information service query facade.
信息服务查询facade。
应用推荐