Just because the Corticon Server is running does not mean it is ready to process transactions. It must still be loaded with one or more Ruleflows. Once a Ruleflow has been loaded, or deployed, to the Corticon Server we call it a Decision Service because it is a service ready and able to make decisions for any external application or process (client) that requests the service properly.
Loading the Corticon Server with Ruleflows can be accomplished in several ways:
Deployment Descriptor files - An easy method, and the one we will use in this guide.
Deployment using the Server Web Console - Another easy way to load Decision Services. It is discussed in detail in topics in Decision Services and Applications .
Compile and deploy APIs and command line utilities, - These methods require more expertise in development tools, and are not discussed in this guide. For more information, see the topics in Packaging and deploying Decision Services .
All these methods are described more thoroughly in the Server Integration & Deployment Guide.
Package and Deploy Decision Services wizard - The easiest method. It is discussed in detail in the topics in Using Studio to compile and deploy Decision Services .