Enabling and Disabling Languages

Languages are enabled in PPM as soon as you deploy them. Users can see boilerplate PPM content in their session language immediately after they log on. However, you may want to make languages unavailable to users until all of the translatable content is in place, and then enable them for users.

To enable or disable a language on a PPM instance:

  1. Run the sh ./kConfig.sh (located in the <PPM_Home>/bin directory):

    Note: For information on how to run the kConfig.sh script on Windows and UNIX systems, see the Installation and Administration Guide.

    The PPM Configuration wizard starts.

  2. From the Select the language below for this installation list, select the language that you want the installer to use to display its steps.

    Note: Regardless of the language you select for the configuration wizard to use, the server configuration parameters names are displayed in English.

  3. Click OK.

    The configuration wizard lists all of the tasks that you can use it to perform.

  4. Click Next.

  5. On the Configuration Options step, select the MLU (Multilingual UI) checkbox, and then click Next.

    The configuration wizard displays all of the non-system languages deployed on the PPM instance.

  6. Verify that all non-system languages installed are listed, and then do the following, as necessary:

    • To disable a language, clear the corresponding checkbox.

      Note: Keep in mind that users cannot select a session language that has been disabled.

    • To re-enable a language that has been disabled, select the checkbox for the language.

  7. Click Next.

    The configuration wizard advises you that your changes are completed.

  8. Click Done to exit the wizard.

  9. Stop, and then restart the PPM Server.

  10. Open the PPM log-on page and check the Language list to verify that the changes you made are reflected are implemented.

After if you disable a language on an upgraded system, the PPM database schema may still contain data that is displayed in that language if translations are not available. For example, if an entity was created in a now-disabled language, and the system has no translation for the entity in a user's session language, the attributes of that entity are still displayed in its definition language.