ILOG JRules User Guide > Deploying Rules > Tasks > Deploying Rules to .NET > Preparing for Deployment to .NET

Before deploying to .NET, you need to have created your rule project up to and including extraction to a ruleset archive. On completion, you have a JAR file containing the JRules ruleset archive that you use as input to the BOM to XOM (B2X) Mapping tool.

On the .NET side, you need to create the .NET XOM and add extenders in your .NET Execution Object Model (XOM) to fill the gap between your Java XOM and the .NET XOM.

Note
You do not necessarily need to have a Java XOM if you want to use JRules to build the BOM and then deploy to .NET. The BOM model can be passed to the .NET developers to implement the classes with a one-to-one mapping with the BOM. Extenders can be used on the .NET side if necessary.

To enable a rule package to be executed in .NET from JRules:

  1. Create the .NET XOM.
  2. In .NET you must implement the Execution Object Model (XOM). You may need to add extender classes that will implement missing methods from the Business Object Model (BOM) classes.
  3. Identify extenders in the .NET XOM.
  4. In .NET you use metadata to indicate which classes are extenders. The metadata definition need only be set up once. It should have the following format:
public class Extender : Attribute
{
}
You will then be able to use the metadata [Extender] on your extender classes. This enables the GUI to determine which classes should be available for translation or for extender purposes. On completion, you will have a DLL file that is used as input to the B2X Mapping tool to remap the BOM for .NET compatibility.

Related Concepts

Rule Project
Rulesets and Ruleset Archives
Deployment to .NET

Related Tasks

Generating a .NET DLL Using the B2X Mapping Tool
Setting Up a Rule Project
Writing Rules
Exporting a Ruleset Archive
Deploying Rules to .NET