In most production deployments, Corticon Server JARs are bundled and given a J2EE 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 J2EE container where you intend to deploy the Corticon Server.
Corticon Studio makes in-process calls to the same Corticon Server classes (although packaged differently) 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.
Note: For detailed information on using packages that facilitate setup of Corticon Server for Java and Corticon Web Console on supported UNIX/Linux platforms and brands of Application Servers, refer to the Progress Software web page Progress Corticon 5.7 - Supported Platforms Matrix for the currently supported platforms and app servers. Then see the Corticon KnowledgeBase entry Corticon Server 5.X sample EAR/WAR installation for different Application Servers for detailed instructions on configuring Apache Tomcat, JBoss, WebSphere, WebLogic on all supported platforms. The Corticon Server ZIP download includes key scripts in shell script format for use in UNIX/Linux applications, such as corticonManagement.sh, testServerAxis.sh, and testServerREST.sh.
