Directory structure and file names

The Sterling™ Order Management System Software directory structure must be maintained based on the language and country or region localization.

File names are limited to one locale and can only contain characters a through z, 0 (zero) through 9, and the underscore (_).

Likewise, because many files are created using a transaction ID, this rule also applies to transaction names and transaction IDs. Similarly, you should adhere to these limitations when localizing the template file name for transaction events (TransactionID.On_SUCCESS.xml).

Sterling Order Management System Software follows the hierarchy of lookups provided here:

1. When a certain locale is selected in the console, it searches for some files with that particular suffix specified in the locale. For example, if the locale ja_JP is chosen in the console, the system searches for files such as ycpapibundle_ja_JP.properties, validation_ja_JP.properties, sapphire_ja_JP.css, and so forth.
2. If these files are not found, the systems looks at the default locale of the operating system that the application server is running. If it is en_US, the system tries to look for the files mentioned in Step 1, but with the suffix en_US, for example, ycpapibundle_en_US.properties.
3. Only if the first two steps fail are the default files, for example, ycpapibundle.properties used.

The method of defaulting to the standard files occurs for the files that can have locale suffix such as alertmessages.js, scfoundationiconsbe.jar, and so on.