BRMS implementation example 2.
BRMS实现示例2。
BRMS implementation example 1.
BRMS实现示例1。
Managing enterprise rules with BRMS.
使用BRMS管理企业规则。
Business rules governance provided by BRMS.
BRMS提供业务规则治理。
BRMS tools promote loosely coupled architecture.
BRMS工具促进了松散耦合的体系结构。
The ILOG BRMS approach includes the following benefits.
ILOGBRMS方法提供以下好处。
Traditional non-BRMS implementation of business rules.
业务规则的传统非brms实现。
One of them is defining the logic as business rules in a BRMS.
其中一种方法是将逻辑定义为BRMS中的业务规则。
Use Case 5 — Reaching the tipping point — optimizing with BRMS.
用例5——到达临界点——使用BRMS进行优化。
Figure 1 shows the conceptually common architecture of a BRMS system.
图1显示了BRMS系统概念上的通用体系结构。
Generate the service data objects from the WSDL exposed by ILOG BRMS.
从ilogBRMS公开的WSDL生成服务数据对象。
A side-by-side comparison of BRMS vs. traditional rules implementations.
BRMS和传统规则实现的比较。
The next section explores some more features and reasons for using BRMS tools.
下一个部分将探索一些其他功能和使用BRMS工具的理由。
WebSphere Commerce can expose the data using web services, which BRMS can consume.
WebSphereCommerce可以使用BRMS能够使用的web服务公开数据。
Figure 7 shows the interaction flow from the task command to the external ILOG BRMS.
图7展示了从任务命令到外部ILOG BRMS的交互流。
It bears repeating: BRMS tools allow business user to define rules in simple English.
值得重复的是：BRMS工具允许业务用户使用简单的英语来定义规则。
BRMS are software tools used to create, manage, and support business rules of an enterprise.
BRMS是用于创建、管理和支持企业的业务规则的软件工具。
Here are some of the advantages that become apparent from the BRMS architecture, as shown in Figure 1.
下面是一些可从BRMS体系结构中明显看出的优点，如图1所示。
There are various ways (EJB, POJO, or web service) to expose business rules created within JRules BRMS.
有多种方法（EJB、POJO或webservice）可以公开在 JRulesBRMS中创建的规则。
For a list of some leading providers of BRMS products please check the Resources section of this article.
有关一些领先的BRMS产品提供商的列表，请参见本文的参考资料部分。
You can see from these examples how BRMS promotes visibility, simplicity and agility in the business world.
这些示例展示了BRMS提高了业务领域中的可见性、简单性和敏捷性。
Once the rules are authored, BRMS can expose the rules using various interfaces like EJB, POJO, and web services.
一旦规则创建完成，BRMS可以使用EJB、POJO和web服务等各种接口来公开规则。
The other crucial aspect is that BRMS does not hold any of the application data as it holds just the business rules.
另一个关键方面是，BRMS只拥有业务规则，不拥有任何应用程序数据。
These application data reside in WebSphere Commerce and need to be made available to BRMS during the authoring of the rules.
应用程序数据驻留在WebSphereCommerce 中，需要在规则创建期间对BRMS可用。
The basic idea is that the BRMS decouples an application's business logic from its data validation logic and from its flow control.
其基本思想在于，BRMS将应用程序的业务逻辑与其数据验证逻辑和流程控制分离开来。
Reference links for traceability: BRMS artifacts can be associated with links to relevant Industry Model requirements and specifications.
通过引用链接提供可跟踪性：BRMS工件可以与相关的Industry Models需求和规范的链接相关联。
We have discussed some key benefits of using BRMS, but if you've been in it for long time, you know how to separate the hype from reality.
我们已经讨论了使用BRMS的主要优势，但是如果您长期从事IT方面的工作，那么您应该知道如何分辨宣传和现实。
By adopting the ILOG BRMS approach, organizations can effectively deal with the problems associated with traditional embedded decision logic.
通过采用ILOGBRMS方法，组织能够有效处理与传统嵌入式决策逻辑关联的问题。
This article discussed how to integrate WebSphere Commerce with ILOG JRules BRMS to provide more robust, dynamic, and complex business rules.
本文讨论如何集成WebSphereCommerce和ILOGJRulesBRMS来提供更健壮、更动态和更复杂的业务规则。
Direct import of standard artifacts: in some cases, Industry Model artifacts are available in a format that can be directly imported into a BRMS.
直接导入标准工件：在某些情况下，Industry Models工件采用可以直接导入BRMS的格式。
应用推荐