This section discusses the different approaches for packaging and deploying rules for use in test and production environments. Depending on your experience and your production status, you should start with the fastest and easiest way, and -- as your solution moves toward production -- refine your approach to better manage your deployed rules and Corticon Servers.
When you are developing rules in Corticon Studio, within Studio you can:
Package and deploy Decision Services directly to a Corticon Server, a good idea for developer integration testing.
Create deployable Decision Service files that can be delivered to other Corticon servers for later deployment through Server tools.
When you are managing and administering a Corticon Server, you can:
Deploy Decision Service files which can be deployed with the Web Console or Server APIs.
Deploy through a Deployment Descriptor file, a text file that identifies one or more Ruleflow or Decision Service files to be deployed and their respective properties to be set on the Decision Service. This is a good idea when you want a file manifest of the deployment.
Ruleflow files listed in a Deployment Descriptor file are great in a collaborative test environment, but not recommended for production because it requires the server to compile the rule assets into a Decision Service.
Decision Service files listed in a Deployment Descriptor file are recommended for production.
When you want to run Corticon Server in-process, you can:
Use the Server API to add and manage Decision Services. See the JavaDoc APi for more details.
The next section reviews the file types that are involved in deployment.
Package and deploy Decision Services directly to a Corticon Server, a good idea for developer integration testing.