Deploying Decision Services with identical Decision Service names
Ordinarily, all Decision Services deployed to a single Corticon Server must have unique Decision Service Names. This enables the Corticon Server to understand the request when external applications and clients invoke a specific Decision Service by its name. A Decision Service's Name is one of the parameters defined in the Deployment Console and included in a Deployment Descriptor file (.cdd). If Java APIs are used in the deployment process instead of a Deployment Descriptor file then Decision Service Name is one of the arguments of the addDecisionService() method. See Deployment related files
for a refresher.
However, the Decision Service Versioning and Effective Dating feature makes an exception to this rule. Decision Services with identical Decision Service Names may be deployed on the same Corticon Server if and only if:
They have different Major version numbers; or
They have same Major yet different Minor version numbers
To phrase this requirement differently, Decision Services deployed with the same Major Version and Minor Version number must have different Decision Service Names.
The Deployment Console shown in the following figure displays the parameters of a Deployment Descriptor file with three Decision Services listed.
Figure 343. Deployment Console with Three Versions of the same Decision Service
Notice:
All three Decision Service Names are the same: skydiver4.
All three Ruleflow filenames are the same: skydiver4.erf.
Each Ruleflow deploys a different Rulesheet. Each Rulesheet has a different file name, as shown on the following pages.
The file locations (paths) are different for each Ruleflow. This is an operating system requirement since no two files in the same directory location may share a filename.
All three Decision Services have different (Major) Version numbers.
It is also possible to place all Ruleflow files (.erf) in the same directory location as long as their filenames are different. Despite having different Ruleflow filenames, they may still share the same Decision Service Name as long as their Version or Effective/Expiration Dates are different.
They have different Major version numbers; or