This section summarizes how you set the character encoding and request locale, described in the previous sections, for different types of web site configuration.

One Locale for Server and Content

If you design a site where the server locale and the web content locale are the same, the following configuration steps are necessary:

  1. If necessary, set the server locale by changing the JVM locale. See Setting the Java Virtual Machine Locale for more information.

  2. Configure the character encoding for site content. See Using the EncodingTyper to Set the Character Encoding or Setting Character Encoding in JSPs.

  3. Set the generateRequestLocales property to false in the /atg/dynamo/servlet/pipeline/DynamoHandler component.

  4. If necessary, configure the JDBC driver and database for the appropriate encoding. Generally, the encoding of the database should be the same as the encoding of the site content, including JSP files and repository content. See the Configuring the Database Encoding section in this chapter for more information.

Server Locale and One Different Content Locale

If you design a site with two different locales—one server locale and a different web content locale—the following configuration steps are necessary:

  1. If necessary, set the server locale by changing the JVM locale. See Setting the Java Virtual Machine Locale for more information.

  2. Configure the character encoding for site content. See Using the EncodingTyper to Set the Character Encoding or Setting Character Encoding in JSPs.

  3. Set the generateRequestLocales property to true in /atg/dynamo/servlet/pipeline/DynamoHandler component.

  4. In the /atg/dynamo/servlet/RequestLocale component, set the overrideRequestLocale property to the request locale.

    For more information, see Configuring the Request Locale.

  5. If necessary, configure the JDBC driver and database for the appropriate encoding Generally, the encoding of the database should be the same as the encoding of the site content, including JSP files and repository content. See the Configuring the Database Encoding section in this chapter for more information.

Server Locale and Multiple Content Locales

If you design a site with a server locale and multiple visitor locales, the following configuration steps are necessary:

  1. Separate the content pages into language-specific directories.

    See the Locale-specific Content Pages section in this chapter for more information.

  2. Decide which repository design best fits the needs of your site. Edit targeting rules and repository meta-tags as necessary.

    For more information, see the Internationalizing Content Repositories section in this chapter.

  3. If necessary, set the server locale by changing the JVM locale. See Setting the Java Virtual Machine Locale for more information.

  4. Configure the character encoding for site content. See Using the EncodingTyper to Set the Character Encoding or Setting Character Encoding in JSPs.

  5. Set the generateRequestLocales property to true in the /atg/dynamo/servlet/pipeline/DynamoHandler component.

  6. Set the validLocaleNames and defaultRequestLocaleName properties in the /atg/dynamo/servlet/RequestLocale component.

    For more information, see Configuring the Request Locale.

  7. Design the entry point to your site so that it matches the user’s request locale to the appropriate content directory. For more information, see the Designing a Multi-Locale Entry Page section in this chapter.

  8. If necessary, configure the JDBC driver and database for the appropriate encoding. In this situation, you are likely to want to configure your database to use Unicode. See the Configuring the Database Encoding section in this chapter for more information.

  9. Add an attribute for the user’s locale to the profile template.


Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices