Article ID: 122585, created on Aug 6, 2014, last review on Nov 15, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • APS 2.x

Configuring locales on sandboxes with no linux shared hosting

Normally to work with localization you need to install a language pack, create a brand, specify the locales available for the brand and then only log in through the brand access point.

On sandboxes with no Linux Shared Hosting module (lin-mn and lin-pba) brands cannot be configured.

There is another way you can enable multiple languages even on lin-mn sandbox, without using a brand.

  1. Install a language pack you wish to use on your sandbox.

    Available language packs can be downloaded:

    Installation instructions are available here, the part when locale should be enabled in brand settings can be skipped.

  2. After the language pack is installed on Operations Automation management node, open System > Settings > User Interface in Operations Automation PCP.

    Under Localization choose user can select language on login screen for Allow to select language setting.

    For Available languages mark checkboxes next to languages you wish to activate (at least two must be enabled).

    Now login screen will contain a list of languages you specified enabled.

  3. If it is necessary to change locale of Billing Automation part of the sandbox - following steps are required:
    • Stop pba service (service pba stop);
    • Run script pba-installer-*.sh (effectively, we are installing new modules as per this article);
    • Go through wizard and choose needed language pack(s)
    • After pba-installer execution is finished start configuration script(/usr/local/bm/tools/configure.pl);
    • Start pba service (service pba start).

Just a reminder:

  • *.tgz file is a tarball, when it is copied to the tarballs directory according to the instructions don't forget to change permissions to 0755.

    - *.pdl.asc is a package manifest


Search Words

localization

pack

locale

language

70bf700e0cdb9d7211df2595ef7276ab 717db81efe94e616312b74fb03a5d474 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF