Skip Headers
Oracle® Communications Network Integrity Developer's Guide
Release 7.1

E23701-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

33 Network Integrity Localization Pack

This chapter provides information about the Localization Pack for Oracle Communications Network Integrity.

Localization Pack Overview

The following sections provide overview information about the localization pack:

Localization Summary

The Network Integrity UI is a fully internationalized Web browser-based application. English is the default interface language. A System Integrator can localize the UI into any other languages, by building a Localization Pack.

Localization Pack Summary

The Network Integrity UI makes use of the full depth of i18n support provided by the Application Development Framework (ADF) stack. The application UI is fully internationalized by making use of XML Localization Interchange File Format (XLIFF) files to keep all display strings separate from other code artifacts. Various parts of the ADF stack (ADF Faces, ADF Model, and ADF Data Control) are also built with full i18n support. A Localization Pack is a collection of XLIFF files and other property files, which together localizes the UI to another language. A Localization Pack can be installed into the Network Integrity application, in the same manner as a Cartridge Pack installation.

Expected Outcomes

The user can successfully build a Localization Pack.

Building the Localization Pack

Use the following procedure to build a Localization Pack:

  1. Download localization.iar from the Localization Pack in the Oracle Communications Network Integrity documentation media pack on the Oracle software delivery Web site:

    https://edelivery.oracle.com

    Note:

    The Localization Pack also contains a partial sample traditional Chinese localization, for your reference, where parts of the Scan Configuration Creation page are translated into traditional Chinese.
  2. Extract META-INF/manifest.xml to a temporary location.

  3. Open manifest.xml and edit the value of the name tag:

    <name>Locale_Name (Locale_Code)</name> 
    

    Where Locale_Name is the locale of the localization pack that you want to deploy in Network Integrity; for example, German, and where Locale_Code is the code of the locale of that localization pack; for example, de, as in the following example:

    <name>German (de)</name>
    

    For information on supported locales and valid locale codes, see the following Java guide:

    http://download.oracle.com/javase/1.4.2/docs/guide/intl/locale.doc.html

  4. Save manifest.xml and return it to localization.iar/META-INF.

  5. Extract META-INF/cartridge.xml to a temporary location.

  6. Open cartridge.xml and edit the values of the name and languageCode tags:

    <localizations>
       <localization>
          <name>Locale_Name</name>
          <languageCode>Locale_Code</languageCode>
       </localization>
    </localizations>
    

    Where Locale_Name is the locale of the localization pack that you want to deploy in Network Integrity; for example, German, and where Locale_Code is the code of the locale of that localization pack; for example, de, as in the following example:

    <localizations>
       <localization>
          <name>German</name>
          <languageCode>de</languageCode>
       </localization>
    </localizations>
    
  7. Save cartridge.xml and return it to localization.iar/META-INF.

  8. Extract localization.iar/localization.jar to a temporary location.

  9. Extract localization.jar/oracle to a temporary location.

  10. Edit all the XLF files found in localization.jar/oracle or any of its nested folders:

    1. Edit the name of each XLF file to add an underscore and the locale code before the file extension, as shown in the following example:

      DisAddressMsgBundle_de.xlf

      Note:

      Compound locale codes, such as ar-QA, should be added to the XLF file name with an underscore in the place of the hyphen, as in the following example:

      DisAddressMsgBundle_ar_QA.xlf

    2. Open each XLF file and edit the file tag so that the source-language attribute is set to the locale code, as in the following example:

      <file source-language="de"        original="oracle.communications.inventory.api.entity.PhysicalPortMsgBundle" datatype="xml">
      

      Note:

      The source-language attribute for compound locale codes, such as ar-QA, should be set to the first two characters only, as in the following example:
      <file source-language="ar"        original="oracle.communications.inventory.api.entity.PhysicalPortMsgBundle" datatype="xml">
      
    3. Open each XLF file, locate each trans-unit tag and edit its child source tag with the translated value for the desired localization.

  11. Edit all the PROPERTIES files found in localization.jar/oracle or any of its nested folders:

    1. Edit the name of each PROPERTIES file to add an underscore and the locale code before the file extension, as shown in the following example:

      IntegrityUIBundle_de.properties

      Note:

      Compound locale codes, such as ar-QA, should be added to the XLF file name with an underscore in the place of the hyphen, as in the following example:

      IntegrityUIBundle_ar_QA.properties

    2. Open each PROPERTIES file and edit the value for each key with the translated value for the desired localization. For example, edit the INTEGRITY_MANAGE_SCAN_CONFIG key, as in the following example:

      INTEGRITY_MANAGE_SCAN_CONFIG=new_value
      

      Where new_value is the translated value for the key for the desired localization.

    3. (Optional) To enter extended character values (such as Chinese characters), you must use Unicode Escapes (only one character is allowed per escape sequence). Save each PROPERTIES file with UTF-8 encoding, then convert each PROPERTIES file to Unicode Escapes using the native2ascii tool provided with your JDK by entering the following command:

      native2ascii -encoding UTF-8 input_file_name output_file_name
      

      Where input_file_name is the name of the PROPERTIES file being converted, and where output_file_name is the name of the converted file.

      See the partial sample Chinese localization included in the Localization Pack for an example.

  12. Return all XLF and PROPERTIES files to localization.jar.

  13. Return localization.jar to localization.iar.

  14. Deploy localization.iar using the cartridge deploy tool.

  15. (Optional) To localize link names in the Link panel in the Network Integrity UI, you must edit the MBean with the translated values for the desired localization. See Network Integrity System Administrator's Guide for more information about viewing and editing the MBean.

  16. (Optional) To localize cartridge-specific UI parameters:

    1. Extract the contents from your custom cartridge IAR file to a temporary location.

    2. Extract the cartridge MAR file to a temporary location.

    3. Extract the /resourcebundles/xliffBundles/IntegrityOverrideBundle.xlf file to a temporary location.

    4. Edit IntegrityOverrideBundle.xlf:

      • Open each XLF file and edit the file tag so that the source-language attribute is set to the locale code, as in the following example:

        <file source-language="de"        original="oracle.communications.inventory.api.entity.PhysicalPortMsgBundle" datatype="xml">
        

        Note:

        The source-language attribute for compound locale codes, such as ar-QA, should be set to the first two characters only, as in the following example:
        <file source-language="ar" original="oracle.communications.inventory.api.entity.PhysicalPortMsgBundle" datatype="xml">
        
      • Open each XLF file, locate each trans-unit tag and edit its child source tag with the translated value for the desired localization.

    5. Return IntegrityOverrideBundle.xlf to the cartridge MAR file.

    6. Return the cartridge MAR file to the cartridge IAR file.

    7. Deploy your custom cartridge.

Testing the Browser Local

When running the Network Integrity UI, the user chooses the appropriate language from the web browser. This is usually done using the Character or Text Encoding menu of the browser, or from a Language preference setting. The UI displays the selected language only when the corresponding Localization Pack is installed. Otherwise, the UI displays the default English language.

There may be parts of the UI that are supplied by third parties, which are not fully internationalized. Those parts always display in English.