Corticon Server: Deploying Web Services with .NET : Compiling a Decision Service into an Assembly DLL

Compiling a Decision Service into an Assembly DLL

Compiling a Decision Service's .eds file into an Assembly.dll file provides a marked improvement in performance over IKVM dynamically converting .class files during deployment by compiling the .class files inside the .eds file into an Assembly.dll that contains Corticon Data Objects (CDOs), listeners and Rules. The resulting Assembly.dll is added to the .eds file. When the .eds file is deployed, the Corticon Server looks for an Assembly.dll, and when it finds one, it gets the information it needs from the Assembly.dll instead of from the .class files inside the .eds file.

Creating an Assembly.dll

A Corticon Server for .NET installation includes a script, CompileAssembly.bat, located in the .NET Server's home directory that creates an Assembly.dll. The script's inputs require the location of the .eds file you want to compile, and -- if you have Business Objects -- the name of the reference .jar to create for the Business Objects.

To compile a Decision Service into an Assembly.dll:

1. Generate an .eds file. (You could use Transaction Id; 150/151 to Precompile a RuleFlow into an .eds file.)

2. If you have Business Objects, you need to generate stubs (as described in Using .NET Business Objects as payload for Decision Services) into a .jar file that will be incorporated into your .dll.

3. Edit the script CompileAssembly.bat located at [CORTICON_HOME]\samples\compile assembly as follows:

SET INPUT_EDS_FILE_NAME="<path of the input .eds file>"

SET REFERENCE_JAR_FILE_NAME="<path of the reference .jar created by GenStubs>" (or empty)

4. Save the edited file.

5. Open a Command Prompt to the location [CORTICON_HOME]\samples\compile assembly

6. Run the CompileAssembly script.

When the script successfully completes, the .eds file has embedded its Assembly.dll .