Adding a New Language to WorkSpace

The following procedure shows you how to add new languages to Oracle BPM WorkSpace.

To add a new language:

  1. Locate the file fuego.resources_6.5.0.jar in the directory <ORABPM_HOME>/studio/webapps/workspace/WEB-INF/lib. This file contains almost all the English resources used by the application.
  2. Extract the contents of the file fuego.resources_6.5.0.jar into a new directory.
  3. Search for an existing WorkSpace translation file int he directory <ORABPM_HOME>/studio/webapps/workspace/WEB-INF/lib. For example, search for: fuego.resourcesrt_fr_6.5.0.jar. This is the French translation.
  4. Extract the contents into another new directory. Use this directory as a template for the new language.
  5. Replace all the properties files in the template directory with the corresponding English files you extracted from the fuego.resources_6.5.0.jar file.
  6. Rename the files in the template directory using the code that corresponds to your language and country according to ISO-639. For a complete list of the available codes, see http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt.
  7. Translate the files in the template directory to the new language.
  8. Modify the MANIFEST.MF file located in the META-INF in your template directory, so that it references the new language.
    In the following lines, you need to replace your_locale for the code that identifies your new language:
    • Bundle-Name: Oracle BPM Resources your_locale Plug-in
    • Bundle-SymbolicName: fuego.resources.runtime.your_locale; singleton:=true
  9. Modify the plugin.xml file located in your template directory, so that it references your new language. If necessary, also add a value for country and variant.
  10. Use the Java jar utility to package all files in the template folder. The name of the new jar is composed by the String fuego.resourcesrt_, followed by the code that identifies your language, the suffix 6.5.0 and the extension .jar. For example, if your new locale is Vietnamese you need to run the jar tool in the following way:
    jar -cvfm fuego.resourcesrt_vi_6.5.0.jar META-INF/MANIFEST.MF fuego fuegoblock plugin.xml
                    
  11. Copy the new jar to the directories that correspond to your Oracle BPM installation.
    Installation Type Directories
    Studio
    • <ORABPM_HOME>/studio/studio/eclipse/plugins
    • <ORABPM_HOME>/studio/webapps/feeds/WEB-INF
    • <ORABPM_HOME>/studio/webapps/workspace/WEB-INF/lib
    Enterprise
    • <ORABPM_HOME>/enterprise/ext
    • <ORABPM_HOME>/enterprise/webapps/archivingviewer/WEB-INF/lib
    • <ORABPM_HOME>/enterprise/webapps/feeds/WEB-INF/lib
    • <ORABPM_HOME>/enterprise/webapps/papiws/WEB-INF/lib
    • <ORABPM_HOME>/enterprise/webapps/portaladmin/WEB-INF/lib
    • <ORABPM_HOME>/enterprise/webapps/portlets/WEB-INF/lib
    • <ORABPM_HOME>/enterprise/webapps/webconsole/WEB-INF/lib
    • <ORABPM_HOME>/enterprise/webapps/workspace/WEB-INF/lib
    J2EE
    • <ORABPM_HOME>/archivingviewer/WEB-INF/lib/fuego.resourcesrt_it_6.5.0.jar
    • <ORABPM_HOME>/feeds/WEB-INF/lib/fuego.resourcesrt_it_6.5.0.jar
    • <ORABPM_HOME>/papiws/WEB-INF/lib/fuego.resourcesrt_it_6.5.0.jar
    • <ORABPM_HOME>/portaladmin/WEB-INF/lib/fuego.resourcesrt_it_6.5.0.jar
    • <ORABPM_HOME>/webconsole/WEB-INF/lib/fuego.resourcesrt_it_6.5.0.jar
    • <ORABPM_HOME>/workspace/WEB-INF/lib/fuego.resourcesrt_it_6.5.0.jar
  12. Restart your BPM applications.
  13. If you are modifying an enterprise installation, you must regenerate the ear file and re-deploy the Process Engine.
The new language appears as an option in Oracle BPM WorkSpace Settings.