Welcome to ILOG Rules for .NET > Introducing ILOG Rules for .NET > Inside ILOG Rules for .NET > Architecture Guidelines

Explains how the parts of ILOG Rules for .NET operate together to form a comprehensive platform for integrating business rules into your application. It should also help you make design decisions when you integrate Rules for .NET into your enterprise architecture. Before you read this section, make sure you are familiar with the main features and purpose of the ILOG Business Rule Management System (BRMS).

In This Section

Architecture of a Business Rules Application
Understand the architecture of ILOG Rules for .NET.
Designing the Rule Project
Discover the stage when developers and business analysts set up a business domain.
Orchestrating Ruleset Execution
Find out how the developer loads the rules into the rule engine and executes them.
Authoring and Reviewing Rules
Find out how users create and edit business rules.
Integrating Rule Execution into an Embedded Rule Engine
Describes what you need to do to integrate a rule engine and execute your rules.
Deploying Rulesets to a Managed Rule Execution Environment
Find out how to manage your rulesets in an execution environment.
Enabling Business Rule Management for Business Users
Understand how rules are stored in a version-controlled data store for Rule Studio, and in a Rule Document Library for Rule Team Server.
Language Support
Discover how you can set up ILOG Rules for .NET so that you can work in other languages.

Related Section

The Components of ILOG Rules for .NET
Describes the parts of ILOG Rules for .NET such as the ILOG Rule Engine for .NET, and ILOG Rule Solutions for Office.