Importing localized string resources with the command-prompt tool

PolicyCenter provides a command-prompt tool to import localized string resources that you previously exported. The command imports the following string resources as key/value pairs:

  • Display keys
  • Typecode names and descriptions
  • Workflow step names

The command provides parameters that enable you to specify the location of the import file and a language-specific set of string resources to import.

To run the import tool, ensure that the application server is running and navigate to your application installation directory. Then run the following command:

gwb importLocalizations -Dimport.file= sourceFile -Dimport.language= languageCode

  • Command-prompt parameter -Dimport.file specifies sourceFile, the file that contains the translated resource strings. It must be in the same format as a file exported from PolicyCenter. By default, PolicyCenter puts the export file in the root of the installation directory. You can set the import directory as follows:
    • To use the import translation file that is in the default location, enter only the name of the file to import.
    • To use the translation file that is in a different location, enter either an absolute path or a relative path to the file from the root of the installation directory.
  • Command-prompt parameter -Dimport.language specifies languageCode, the suffix to use in the names of the property files that PolicyCenter writes to the localization folder. The language name must match a PolicyCenter language type that exists in the LanguageType typelist, such as fr_FR or ja_JP. For example, specifying ja_JP indicates that PolicyCenter is to write property files that have that language code in the file name, such as display_ja_JP.properties.

See also