skip to main content
Corticon Server: Integration & Deployment Guide : Enabling Server handling of locales, languages, and timezones
 

Try Corticon Now

Enabling Server handling of locales, languages, and timezones

When deploying Decision Services that will be consumed by users or services running in different locales, you often need to address issues with locale-dependent data formats and localized messages. Corticon now has the ability to specify a "locale" when calling a Decision Service. When locale is specified, Corticon uses that locale when parsing and formatting locale-dependent data types such as Decimals and Dates. In addition, Corticon returns localized Rule Messages if you defined localizations for the messages when creating the Rulesheets for your Decision Service.
In prior releases, you would have needed to deploy a Decision Service multiple times--once for each locale supported--to have localized Rule Messages returned. This is no longer necessary. A single deployed Decision Service can support multiple locales.
Localizing your rule modeling and processing environment can implement five related functions:
1. Displaying the Studio program in your locale of choice. This means switching the Corticon Studio user interface (menus, operators, system messages, etc.) to a new language. Consult with Progress Corticon support or your Progress representative to learn more about available and upcoming Corticon localization packages. 
2. Displaying your Studio assets in your locale of choice. This means switching your Vocabularies, Rulesheets, Ruleflows, and Ruletests to a new language.  See "Localizing Corticon Studio".
3. Displaying your localized Rulesheet's rule statements in your locale of choice. Rulesheets can specify rule statements in another language that are returned to requestors when the server is set to that language. This is not a new feature in this release. However, as of this release, when a request's execution property specifies a language that has defined appropriate rule statements, the locale-specific statements are included in the response.  See "Localizing Corticon Studio".
4. Enabling requests submitted to a Corticon Server to set an execution property that indicates the locale of the incoming payload so that the server can transform the payload's locale-specific decimal and date literal values to the decimal delimiter and month literal names of the server, run the rules, and return the output formatted for the submitter's specified locale. This function is described in this section. 
5. Enabling requests submitted to a Corticon Server to set an execution property that indicates the timezone of the incoming payload so that the server can transform the payload's time calculations to the timezone of the server, run the rules, and return the output formatted for the submitter's specified timezone. This function is described in this section.
In this section: 
* Character sets supported
* Handling requests and replies across locales
* Examples of cross-locale processing
* Example of cross-locale literal dates
* Example of requests that cross timezones