此规则类别通过允许非编程人员对规则进行维护从而支持业务灵活性。
This rule category supports business agility by enabling nonprogrammers to maintain the rules.
列出和每一项规则相关联的所有资源，展开规则类别和规则节点。
To list the resources associated with each rule, expand the rule categories and rule nodes.
对于这个例子来说，添加一个被称作MyRule的新的规则类别(请参见图11所示)。
For this example, add a new rule category called My rule (see Figure 11).
本文简要总结了三种普通规则类别，并说明它们如何与SOA集成——不用受以下两方面的限制？
This article summarizes three general rule categories and describes how they integrate with the SOA — regardless of.
当您展开这棵树时，每一个规则类别和规则都显示出生成结果的数量，并且列出和该规则相关联的资源(请参见图17所示)。
When you expand the tree, each rule category and rule displays the number of results generated and lists the resources that are associated with the rule (see Figure 17).
客户机服务不知道其所使用的服务是如何实现的——是否采用规则或其他实现技术——也不知道规则所属的规则类别、何时存在选择。
The client service is agnostic to how the service is implemented — whether rules or some other implementation technology — and to which rule category is used, when there is a choice.
您还能够通过输入或者点击一个定义好的规则集，选择一组规则的集合。然后点击Set对提供者、规则类别、以及规则进行配置，从而执行一个特定的分析。
You can also select a collection of rules by typing or clicking a defined rule set. and then clicking set to configure the providers, rule categories, and rules to perform a specific analysis.
您应当识别出规则扩展的第一个部分，这是由于它几乎等同于前面所显示的类别扩展。
You should recognize the first part of the rule extension, because it is almost identical to the category extension previously shown.
相反，在本系列的下一篇文章中，我们将只关注您在创建新的类别和规则时所需要用到的那一部分，例如：提供者和结果扩展点。
Instead we will focus on just few that you need to create new categories and rules. We will cover others, such as the provider and result extension points, in the next article of this series.
所谓的类别代表了静态分析框架之中的一组规则。
An analysis category represents a group of rules within the static analysis framework.
虽然默认的类别、规则和字典是可以立即使用的，但是也可以对它们进行定制，以识别更特定于所分析领域的信息。
Default categories, rules, and dictionaries are included out of the box, but these can be customized to recognize information more specific to the domain being analyzed.
在向导的第一页，您可以选择规则位于分析类别树的什么位置。
On the first wizard screen, you can select where the rule will be located in the analysis category tree.
一旦这些规则就位，系统就只废弃任何属于其中一个类别的信息包。
Once these rules are in place, your system will simply discard any packets that fall into one of these categories.
一个类别还拥有一个唯一的ID，它被其他类别和规则用来决定控制。
A category also has a unique ID, which is used by other categories and rules to determine containment.
控制区域用于接受客户端请求(HTTP、IIOP)，并根据预定义的规则将请求划分为不同的服务类别。
The control region is used to accept the client requests (HTTP, IIOP), and classify the requests into different service classes according to predefined rules.
举例来说，您将首先创建您自己的类别，然后将规则同这个类别相关联。
For this example, you will first create your own category, then you will associate the rule with that category.
这些规则可以根据类别分成组，这些不同的组可以同时被使用。
Such rules can be grouped together based on categories, and applied collectively as well.
本文还将描述不同类别的规则与各种服务交互样式进行交互的方式。
This article also aims to describe the ways different categories of rules interact with the various service interaction styles.
私有API：这个类别中的规则专注于找出你的代码中访问了私有API的实例。
Private API: The rules in this category focus on finding instances within your code where a private API has been accessed.
本文的一个目的就是对各种类别的业务规则进行简要总结，并说明单个与IBMSOA集成的方法如何适应不同类型的规则。
One purpose of this article is to summarize the various categories of business rules and show how a single approach to integration with the IBM SOA fits different kinds of rules.
提供者包含类别（规则或者其他类别的松散组织，或者两者皆有）。
Providers contain categories, which are loose organizations of rules or other categories, or both.
所谓的分析提供者能够帮助对一个特定领域分析的规则或者类别进行分组。
An analysis provider helps group rules and categories for a specific domain of analysis. A domain of analysis covers other coding languages or different types of analysis.
我们来考虑一下编写一个具有新类别和新规则的规则插件程序所必需的所有步骤。
Let's consider all of the steps that are necessary to write a complete rule plug-in with a new category and rule.
提供者包含许多类别，它们是松散地组织的规则或其他类别。
Providers contain categories, which are loose organizations of rules or other categories.
CodePro带有大约35个类别的900多个规则，可以通过多种方式考虑您的代码，并为代码的不同方面生成单元测试。
With more then 900 rules in about 35 categories, CodePro can look at your code in several ways, generating unit tests for different aspects of the code.
在本篇文章中，我们已经学习了APIs，以及从底层构建新分析Provider需要的大多数方面，包括类别以及规则的定义。
In this article, we have covered most of the APIs and requirements to build a new analysis provider from the ground up, including the definition of a category and rule.
与 /Products/Beverages.aspx 相似，下面我们要为其他产品类别添加重写规则。
Similar to /Products/Beverages.aspx, we'd next add rewriting rules for the other product categories.
除了结果之外，history元素还保持同被选中的提供者、类别和规则的联系。
In addition to results, the history element also keeps track of which providers, categories, and rules were selected.
OmniFind将它的结果组织为类别，每个类别是一个基于规则的搜索结果集，具有给定的ID和描述性名称。
OmniFind organizes its results into categories. Each category is a rule-based set of search results, given an ID and a descriptive name.
该条目包括了所有Provider，类别以及在分析启动配置中定义的规则的列表，还有选择用于分析的资源的列表。
This entry contains a list of all providers, categories, and rules that were defined in the analysis launch configuration, as well as a list of selected resources that were analyzed.
应用推荐