Task overview: Globalizing applications
An application that can present information to users according to regional cultural conventions is said to be globalized: The application can be configured to interact with users from different localities in culturally appropriate ways. In a globalized application, a user in one region sees error messages, output, and interface elements in the requested language. Date and time formats, as well as currencies, are presented appropriately for users in the specified region. A user in another region sees output in the conventional language or format for that region. Globalization consists of two phases: internationalization (enabling an application component to use regional conventions) and localization (implementing a specific regional convention). This product supports globalization through the use of its localizable-text API and internationalization service.
- Make sure the server runtime environment is properly configured.
- Implement message catalogs in the application by using the localizable-text API.
This product supports the maintenance and deployment of centralized message catalogs for the output of properly formatted, language-specific (localized) interface strings.
For more information about the localizable-text API, see Task overview: Internationalizing interface strings (localizable-text API).
- Implement more extensive locale support by using the internationalization service.
With the internationalization service, we can manage the distribution of the internationalization information, or internationalization context, that is necessary to perform localizations within Java EE application components. Supported application components also include Web service client environments and Web service-enabled enterprise beans.
For more information about the internationalization service, see Task overview: Internationalizing application components (internationalization service).
Working with locales and character encodings
Language versions offered by this product