Globalization and localization assumptions and limitations

Globalization and localization have several implications for the integration of WebSphere Commerce and Sterling Order Management.

To set up UTF-8 character encoding, all process startup scripts (for example, for the application server, time-triggered transactions) must be modified to include the -Dfile.encoding=UTF-8 parameter for the Java™ command. Specifically for integration, the parameter -Dfile.encoding=UTF-8 needs to be passed in the startIntegrationServer script.

The promotion name and promotion code exist in the language that is created and set up by the business user. Other fields, such as promotion description and reason code, exist in multiple languages that depend on the locale of the promotion. The language request from Sterling Order Management is the request that is returned to the Sterling Order Management user.