You can localize the GUIs for WFM Web Supervisor and WFM Web Agent without having to obtain localized software from Genesys. This enables Genesys partners and customers to deploy translated versions of these user interfaces, when Genesys does not provide localized versions of WFM.
This topic includes the following sections:
- Procedures: Initial and Subsequent Localizaton
- Tools and File Descriptions
- Applying the Localization.bat File Options
The WFM Agent and Supervisor components each draw their GUI text from a properties file, which you can modify. You can localize WFM to any language that you wish, by translating the text in these files.
Perform this localization carefully, by making backups that you can use to undo mistakes and by using text that has the precise meaning of the words and phrases that you are translating. Genesys assumes no responsibility for work performed by anyone, other than a Genesys employee.
Ensure you have the following requirements to complete your self-localization:
- JDK (the Java Development Kit, same version as required by WFM Web) must be located in the path JAVA_HOME.
- Certificate to sign Java code.
The localization.bat batch file is installed in the same directory where WFM Web was initially installed. Use this file to:
- Extract the agent.properties and supervisor.properties properties files from the wfm.war file.
- Update the wfm.war file by reinserting the two WFM Properties files. Run the localization.bat file from the Windows command line interface.
For example, To display the help message, which summarizes all functionality, enter:
C:\Program Files\GCTI\WFM76\Web>localization -h
Before localizing your WFM deployment, ensure you take the following precautions:
- Back up wfm.war before you make your changes. You may need to replace the modified file if your changes have unexpected results.
- Back up the properties files before you make your changes, for the same reason that you back up wfm.war.
- Back up wfm.war, as well as the properties files, after you make your changes too. When you install a WFM Web patch, you also install a new (non-localized) wfm.war file. The backup allows you to restore your changes accurately and with a minimum of effort.
- With that backup, you can restore your changes accurately and with a minimum of effort after installing a WFM Web patch, which includes a new (non-localized) wfm.war file.
- Wait for the extraction and updating processes to finish; they do not display status.
Due to changes in the Java security model, localized resources must be placed into signed wfm-localization.jar. See docs.oracle.com, The localizer is responsible for obtaining a certificate and for signing the file wfm-localization.jar.
Task Summary: WFM Localization Process
|1. Extract the properties files from inside wfm.war|
|2. Localize the properties files. See "Procedure: Localizing WFM the First Time"|
|3. Create the file wfm-localization.jar, including inside translated resources from task 2 of this summary.|
|4. Sign the wfm-localization.jar file (from task 3).|
|5. Update wfm.war with the signed wfm-localization.jar (from task 4).|
|6. Deploy the new wfm.war on the web application server.|
Procedures: Initial and Subsequent Localizaton
You will use different procedures for the initial and subsequent localization of WFM.
The first time you localize WFM, you must follow the steps in the Procedure: Localizing WFM the First Time. When you localize the text in your WFM web archive, you are modifying the program’s software—the messages, menus and other elements of the screen display. By doing this yourself, you must accept responsibility for any possible errors you might make and ensure that you can recover from any possible errors. Therefore:
- Accept responsibility by following these instructions closely. Do not take shortcuts.
- Ensure error recovery by backing up your files before and after every change.
All Subsequent Localizations
In the future, if there is an updated version of WFM Web that you need to deploy (for example, a patch or software update) and you have already localized WFM, follow the steps in the Procedure: Localizing WFM the Next Time (Subsequently).
Purpose: To localize WFM for the first time (the initial process).
Start of Procedure
- Make a backup copy of the existing wfm.war file and save it in a safe place (in a different directory, with a different name, or both). The wfm.war file is an important WFM software component, and you might need to replace a broken version.
- Extract the supervisor.properties and agent.properties properties files from the wfm.war file, by using the software tool localization.bat. Click Start > Run to open a command window. Then enter: localization -x
...where -x extracts the properties files. See Using localization.bat for ways to specify file names and locations.
- Make a backup copy of the properties files before you change them, rename them with a descriptive name (for example, agent.properties.english.v8.1.000.10), and then store them in a safe place.
You will need these in the future to compare with newer properties files when software updates to WFM Web are released.
- Using a text editor, update the two properties files by changing the English text strings to the language you want to use.
- Make a backup copy of these localized properties files, rename them with a descriptive name (for example, agent.properties.czech.v8.1.000.10) and then store them in a safe place.
- Create the wfm-localization.jar file, by using the localization -c option.
- Sign the wfm-localization.jar file, by using Java's utility keytool, which is documented here: docs.oracle.com.
- Update the wfm.war file. Use the localization -i option.
- Deploy the wfm.war file to the WFM Web Server, by completing the following steps:
In a worst-case scenario, you can always reinstall WFM Web from the original software release disk or FTP download that you received from Genesys.
- Stop Tomcat.
- Copy the edited wfm.war file and then paste it into the Tomcat folder.
- Restart Tomcat.
End of Procedure
Purpose: To localize WFM after an updated version has been deployed (subsequent to the initial localization).
Prerequisite: Your WFM deployment has been localized at least once before. See Initial Localization.
Start of Procedure
- Use the localization.bat file to extract the two properties files (one for the WFM Web for Agents GUI and one for the WFM Web for Supervisors GUI) from the wfm.war file. (See step 2 in the Procedure: Localizing WFM the First Time
- Compare the new versions of the properties files with the original ones, by using the windiff tool (or any text editor that provides comparison capabilities) to identify any new or changed strings that require localization.
- Using the text editor, update the two localized properties files that you created in step 3 in the Procedure: Localizing WFM the First Time, adding any new string resources in the appropriate place.
- Create and sign the wfm-localization.jar file and update the file wfm.war, by using the same tools as described steps 6 and 7 in the Procedure: Localizing WFM the First Time.
- Deploy the updated wfm.war file on the Web application server. See instructions for deleting the .war file from Tomcat (step 9 in the Procedure: Localizing WFM the First Time).
End of Procedure
Tools and File Descriptions
Use the tools specified in the table below to localize your installation of WFM.
|localization.bat||Use this batch file to extract and update the properties files from wfm.war. See Using localization.bat.|
|wfm.war||This Web archive file contains the WFM properties files agent.properties and supervisor.properties.|
|agent.properties||Edit the text inside this properties file, to localize the WFM Web for Agents GUI.|
|agent800.properties||Edit the text inside this properties file, to localize parts of the WFM Web for Agents GUI.|
|supervisor.properties||Edit the text inside this properties file, to localize the WFM Web for Supervisors GUI.|
|wfm-localization.jar||The archive that contains the translated resources.|
|Text editor||Use a non-formatting text editor (such as Notepad or Wordpad) to edit the properties files.|
|Windows system tools||Use the appropriate system tools to stop and restart the web application server, and to copy the localized wfm.war to its appropriate location.|
|Web Application Server||This appendix uses Tomcat as the default device that enables access to WFM. However, depending on your configuration and version of WFM, it could instead be WebSphere.|
Applying the Localization.bat File Options
This section describes how to use the options in the Localization.bat file and provides examples.
Specifying the DefaultsEach file used by the localization.bat file has a default name and a default location. To use these defaults, enter the command line in its simplest format: [+]
Specifying DirectoriesYou can specify absolute paths or relative paths to the directories that hold the files. Here are some examples: [+]
Specifying FilenamesYou can specify different filenames for any of the files. Here are some examples: [+]
Combining OptionsYou can combine any or all of these options. This example occupies a single command line, and has been wrapped in arbitrary places for readability: [+]
To see usage examples, enter this command line: localization -e