Using Content Server in International Environments PDF
Content Server Locales > System Locales > Changing the System Locale Setting


Changing the System Locale Setting

The default system locale for Content Server is English-US. If you want, you can to change it using System Properties, which is one of the stand-alone administration utilities.

Note: Before changing the system locale, make sure that you close any applets that are running. This prevents UI elements from the original locale from being displayed after the system locale has been changed. In addition to restarting any applets, it is also necessary to restart the web browser.

To change the system locale, complete the following steps:

  1. UNIX: Start the System Properties utility by running the System_Properties script, which is located in the bin subdirectory of the Content Server installation directory.

    2. Windows: From the Windows Start menu, select Programs   Content Server Content Server   [Instance Name]   Utilities   System Properties.

    The System Properties applet is started.

  2. Open the Server tab.
  3. From the System Locale dropdown list, choose the system locale you want to use for the current content server instance (see also Available System Locales ).
  4. Click OK to apply the setting and exit System Properties.
  5. Stop and restart the content server:
    1. Log into Content Server as an administrator.
    2. Go to the Administration Applets page.
    3. Choose Admin Server. (You may need to scroll down.)
    4. Click the restart icon (curved arrow) next to the appropriate content server button.
  6. Stop and restart the Admin Server:

    7. UNX:
    a)  Go to the [Install_Dir]/admin/etc directory.
    b)  Execute the idcadmin_restart script.

    Windows:
    a)  Go to Start   Settings   Control Panel   Administrative Tools   Services.
    b)  Select the IDC Content Admin Service.
    c)  Right-click and choose Restart from the popup menu.

    Note: If you do not restart the Content Server and Admin Server, the changes will not take effect.

  7. Depending on your database and search solution setup, you may need to perform an additional task:
    • If your database is set up to use Unicode or UTF-8 and your current Verity locale supports the character set of the new content server system locale, then you do not need to do anything. (This will generally be the case if you are using the ‘uni’ Verity locale.)
    • If your database is set up to use Unicode or UTF-8 and your current Verity locale does not support the character set of the new content server system locale, then you need to change the Verity locale to a locale that does support the character set. After that, you need to rebuild the search index to ensure the data in the database can be accessed and retrieved correctly after the locale changes.
    • If your database is not set up to use Unicode or UTF-8 support, you need to contact Oracle’s Consulting Services organization to ensure the data in the database can be accessed and retrieved correctly after the system locale change.
Caution: Please note that rebuilding the search index may be a very time-consuming process, depending on the number of content items managed by your Content Server instance. It is therefore recommended that you perform the index rebuild during off-peak hours of content server use (typically at night or on the weekend).

Copyright © 1996, 2007, Oracle. All rights reserved.