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 : Using the Java Server's Deployment Console Decision Services
 

Try Corticon Now
Using the Java Server's Deployment Console Decision Services
To start the Corticon Deployment Console, choose the Windows Start menu command All Programs > Progress > Corticon 5.7 > Corticon Deployment Console to launch the script file \Server\deployConsole.bat.
The Deployment Console is divided into two sections. Because the Deployment Console is a rather wide window, its columns are shown as two screen captures in the following figures. The red identifiers are the topics listed below.
Figure 369. Left Portion of Deployment Console, with Deployment Descriptor File Settings Numbered
Figure 370. Right Portion of Deployment Console, with Deployment Descriptor File Settings Numbered
The name of the open Deployment Descriptor file is displayed in the Deployment Console's title bar.
The File menu, circled in the top figure, enables management of Deployment Descriptor files:
*To save the current file, choose (File > Save).
*To open an existing .cdd, choose (File > Open).
*To save a .cdd under a different name, choose (File > Save As). 
The marked steps below correspond to the Deployment Console columns for each line in the Deployment Descriptor.
1. Decision Service Name - A unique identifier or label for the Decision Service. It is used when invoking the Decision Service, either via an API call or a SOAP request message. See Invoking Corticon Server for usage details.
2. Ruleflow - All Ruleflows listed in this section are part of this Deployment Descriptor file. Deployment properties are specified on each Ruleflow. Each row represents one Ruleflow. Use the button to navigate to a Ruleflow file and select it for inclusion in this Deployment Descriptor file. Note that Ruleflow absolute pathnames are shown in this section, but relative pathnames are included in the actual .cdd file.
The term deploy, as we use it here, means to inform the Corticon Server that you intend to load the Ruleflow and make it available as a Decision Service. It does not require actual physical movement of the .erf file from a design-time location to a runtime location, although you may do that if you choose – just be sure the file's path is up-to-date in the Deployment Descriptor file. But movement isn't required – you can save your .erf file to any location in a file system, and also deploy it from the same place as long as the running Corticon Server can access the path.
3. Version - the version number assigned to the Ruleflow in the Ruleflow > Properties window of Corticon Studio. Note that this entry is editable only in Corticon Studio and not in the Deployment Console. A discussion of how Corticon Server processes this information is found in the topics Decision Service versioning and effective dating Also see the Quick Reference Guide for a brief description of the Ruleflow Properties window and the Rule Modeling Guide for details on using the Ruleflow versioning feature. It is displayed in the Deployment Console simply as a convenience to the Ruleflow deployer.
4. Version Label - the version label assigned to the Ruleflow in the Ruleflow > Properties window of Corticon Studio. Note that this entry is editable only in Corticon Studio and not in the Deployment Console. See the Quick Reference Guide for a brief description of the Ruleflow Properties window and the purpose of the Ruleflow versioning feature.
5. Effective Date - The effective date assigned to the Ruleflow in the Ruleflow > Properties window of Corticon Studio. Note that this entry is editable only in Corticon Studio and not in the Deployment Console. A discussion of how Corticon Server processes this information is found in the topics Decision Service versioning and effective dating Also see the Quick Reference Guide for a brief description of the Ruleflow Properties window and the purpose of the Ruleflow effective dating feature.
6. Expiration Date - The expiration date assigned to the Ruleflow in the Ruleflow > Properties window of Corticon Studio . Note that this entry is editable only in Corticon Studio and not in the Deployment Console. A discussion of how Corticon Server processes this information is found in the topics Decision Service versioning and effective dating Also see the Quick Reference Guide for a brief description of the Ruleflow Properties window and the purpose of the Ruleflow expiration dating feature.
7. Maximum Pool Size - Specifies how many execution threads for this Decision Service will be added to the Execution Queue. This parameter is an issue only when Allocation is turned on. If you are evaluating Corticon, your license requires that you set the parameter to 1.See Multi-threading, concurrency reactors, and server pools for more information.
Note: Minimum Pool Size, previously associated with this property, is deprecated as of version 5.5.
8. Database Access - Controls whether the deployed Rule Set has direct access to a database, and if so, whether it will be read-only or read-write access.
9. Entities Returned - Determines whether the Corticon Server response message should include all data used by the rules including data retrieved from a database (All Instances), or only data provided in the request and created by the rules themselves (Incoming/New Instances).
10. Datasource Configuration File - The path and filename of the database access properties file (that was typically created in Corticon Studio) to be used by Corticon Server during runtime database access. Use the adjacent
button to navigate to a Datasource configuration file.
11. Dynamic Reload - When Yes, the ServerMaintenanceThread will detect if the Ruleflow or .eds file has been updated; if so, the Decision Service will be updated into memory and -- for any subsequent calls to that Decision Service -- that execution Thread will execute against the newly updated Rules. When No, the CcServerMaintenanceThread will ignore any changes to the Ruleflow or .eds file. The changes will not be read into memory, and all execution Threads will execute against the existing Rules that are in memory for that Decision Service.
12. XML Messaging Style - Determines whether request messages for this Decision Service should contain a flat (Flat) or hierarchical (Hier) payload structure. The topic Service contracts: Describing the call provides samples of each. If set to Auto Detect, then Corticon Server will accept either style and respond in the same way.
The indicated buttons at the bottom of the Decision Service Deployment Properties section provide the following functions:
*(A) Add Ruleflow - Creates a new line in the Decision Service Deployment Properties list. There is no limit to the number of Ruleflows that can be included in a single Deployment Descriptor file.
*(B) Remove Ruleflow - Removes the selected row in the Decision Service Deployment Properties list.
*(C) Pre-compile Decision Services - Compiles the Decision Service before deployment, and then puts the .eds file (which contains the compiled executable code) at the location you specify. (By default, Corticon Server does not compile Ruleflows until they are deployed to Corticon Server. Here, you choose to pre-compile Ruleflows in advance of deployment.) The .cdd file will contain reference to the .eds instead of the usual .erf file. Be aware that setting the EDC properties will optimize the Decision Service for EDC.
*(D) Save Deployment File - Saves the .cdd file. (Same as the menu File > Save command.)