Specifying the Execution Locale

Designer 10.7 | webMethods Service Development Help | Building Services | About Service Run-Time Parameters | Specifying the Execution Locale

When you create a service, you can set the locale property to indicate the locale policy in which the service executes at run time. The locale policy of a service refers to the language, regional, or cultural settings of a specific target market (the end user). Each locale consists of five sections: language, extended language, script, region, and variant.

Locales can influence the following:

String display of numeric values and date/time values

Parsing of dates and numbers from strings

Default currency (pounds, Euros, dollars)

Default measuring system (metric or customary)

Default system resources (such as fonts, character encoding)

Collation (sorting) of lists

User interface/content language

Integration Server recognizes the following locale policies at run time:

Server locale uses its default JVM locale.

User locale uses the client locale.

Root locale uses neutral or POSIX locale.

Null locale uses no locale policy.

You can also configure Integration Server to recognize custom locales. By default, the service uses the null locale. That is, it uses no locale policy.

To specify the execution locale of a service

1. In the Package Navigator, open the service that you want to configure.

2. In the Run time category of the Properties view, do one of the following to specify the Execution Locale property:

Select...	To...
[$default] Default Runtime Locale	Use the server’s default JVM locale.
[$user] Default User Locale	Use the client locale.
[$null] No Locale Policy	Use no locale policy.
[root locale]	Use the neutral or POSIX locale.
[<ISO code>] <Language>	Use a specific locale.
Open locale editor...	Define a custom locale.

3. If you selected Open locale editor, complete the following in the Define Custom Locale dialog box.

In this field...	Do the following...
Language	Select one of the ISO 639 codes that represent the language. (2- or 3-letter codes)
Extended Language	For future release.
Script	Optional. Select one of the 4-letter script codes in the ISO 15924 registry.
Region	Optional. Select one of the ISO 3166-2 country codes.
IANA Variant	Optional. Add or remove a variant code registered by the IANA.

4. Click OK. Integration Server will execute the service in the specified locale.