Typically, each Decision Service deployed to a Corticon Server has a unique Decision Service name that lets the rules engine handle the request when applications and clients invoke a Decision Service by its name.

However, the Decision Service Versioning and Effective Dating feature makes an exception to this rule. Decision Services with identical Decision Service Names can be deployed on the same Corticon Server provided that each has a different Major version number, or that each has the same Major yet a different Minor version number.

For example, you could deploy Cargo_v0_16.eds,Cargo_v1.1.eds,Cargo_v1.2.eds.

Note: An alternate approach is to rename the Decision Service when you compile it so that you have, say, Cargo_v0_16.edsand Freight_v0_16.eds.