If you are executing the JSM in a distributed or tiered architecture, the remote servers may exist in different countries. These servers may have specific regional or language requirements.
The Java Service Manager resource files are internationalized.
The resource files have a load hierarchy.
basefile.properties
basefile_language.properties
basefile_language_country.properties
Each property entry read will replace a previous property entry. This replacement can occur due to a duplicate key entry further down in the same file or duplicate entry in the later locale property files.
The locale is determined from the client program. A program running on an IBM i machine will supply its encoding and locale information to the JSM server.
Example
|
CCSID |
37 |
|
COUNTRYID |
AU |
|
LANGUAGEID |
ENG |
For the above example, the JSM server will create a thread to handle the connection. This thread will use encoding Cp037 and locale en_AU.
A single JSM server can handle multiple clients with different encoding and locale information.
