Deploy languages using kDeploy.sh and server clustering
You can use the
kDeploy.sh script and server clustering to deploy languages.
Deploy languages using kDeploy.sh
You can deploy a language at any time after PPM center installation by running the
kDeploy.sh script. The procedures described in this section show how to run the script to deploy a language in addition to the system language, and how to run the script to deploy a language as the new system language.
To deploy a language pack using the
kDeploy.sh script after PPM is installed or upgraded:
Using either console mode (UNIX) or Cygwin (Windows), navigate to the
>/bindirectory, and run the following:
sh ./kDeploy.sh -lang <LP>
<LP>represents the language codes for a supported language.
For each additional language you want to deploy, repeat Step 1 and Step 2.
Restart all PPM components on the machine.
(Optional, but strongly recommended) For each language deployed on your PPM instance, run the
kImportAttributes.shscript in test mode, and then, based on the results in the Translation Impact report, decide which of the default translations to import and which to exclude.
Note: For information on why you might choose to perform this optional step, see Determining What Translated Content to Import After Deploying Languages.
For instructions on how to run the
kImportAttributes.shscript in test mode, see Running Import Script. (You must have the Sys Admin: Manage Translations access grant.)
For information on the Translation Impact report, see Translation Impact Report.
For each language deployed on your PPM instance, run the kImportAttributes.sh script to import the translated user interface content.
Note: For instructions on how to selectively import translated content, see Using Translation Management Tools.
Complete the tasks described in After Language Deployment.
The upgrade utility checks the
server.conf file for the existing PPM setup to determine whether you have a single PPM Server or multiple servers in a cluster. Based on this, the upgrade tool sets up either a stand-alone or clustered environment for JBoss.
For detailed information on server cluster configuration, see the Installation and Administration Guide.