skip to main content
Corticon Server: Deploying Web Services with Java : Deploying a Ruleflow to the Corticon Server : Creating and installing a Deployment Descriptor file : Installing the Deployment Descriptor file
 

Try Corticon Now
Installing the Deployment Descriptor file
Once Corticon Server has been installed and deployed to Progress Application Server, the included startup scripts ensure the following sequence occurs upon launching Progress Application Server:
Note: If you are using an evaluation license, the Maximum Pool Size in the Ruleflow you are deploying must be exactly 1. Any other value will issue an alert that you have exceeded the allowed number of reactors.
1. The Progress Application Server starts up.
2. Corticon Server starts up as a web service in Progress Application Server's Servlet container.
3. Corticon Server looks for Deployment Descriptor files in a specific directory.
4. Corticon Server loads into memory the Ruleflow(s) referenced by the Deployment Descriptor files, and creates Reactors for each according to their minimum pool size settings. At this stage, we say that the Ruleflows have become Decision Services because they are now usable by external applications and clients.
In order for the Corticon Server to find Deployment Descriptor files when it looks in step 3, we must ensure that the .cdd files are moved to the appropriate location. In the default installation used in this guide, that location is the [CORTICON_WORK_DIR]\cdd directory. In the future, when creating .cdd files, you may want to save them straight to this directory so they become immediately accessible to the default Corticon Server deployed in this guide.
This location is fully configurable. For more information, see the topics in Packaging and deploying Decision Services .
Now, when the startup sequence reaches step 3, Corticon Server will know where all Ruleflows are located because .cdd files contain their pathnames.