skip to main content
Corticon Server: Deploying Web Services with .NET : Corticon Server for .NET files and API tools : Setting up Corticon Server for .NET use cases
 

Try Corticon Now

Setting up Corticon Server for .NET use cases

In most production deployments, Corticon Server JARs are bundled and given an interface class or classes. The interface class is often called a helper or wrapper class because its purpose is to receive the client application's invocation, translate it (if necessary) into a call which uses Corticon Server's native API, and then forwards the call to Corticon Server's classes. The type of interface class depends on the container where you intend to deploy the Corticon Server.
Corticon Studio makes in-process calls to the same Corticon Server classes (although packaged differently-- see the following topic) when Ruletests are executed. This ensures that Ruleflows behave exactly the same way when executed in Studio Ruletests as they do when executed by Corticon Server, no matter how Corticon Server is installed.