Article ID: 123198, created on Oct 21, 2014, last review on Jun 23, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5

Symptoms

You are going to use non-lating characters on your installation of the Office 365 Application (version 4.11 or higher).

Cause

The Office 365 Application version 4.x uses APS 1.2 for integration. So, additional configuration actions are required to add non-lating characters support.

Resolution

Linux-based Provisioning Gateway Host

Perform the following actions:

  1. Log on to the host as root.
  2. Make sure the mbstring PHP extension is installed and enabled. For example, use the phpinfo() method.
  3. Specify the following options in the php.ini configuration file:
    • mbstring.internal_encoding = UTF-8
    • mbstring.http_output = UTF-8
    • output_handler = mb_output_handler
  4. Restart the HTTPD service using the service httpd restart command.

Windows-based Provisioning Gateway Host

Important: One Windows-based Provisioning Gateway Host can be used to support one language with non-latin characters.

  1. Log on to the host as Administrator.
  2. Make sure the mbstring PHP extension is installed and enabled. For example, use the phpinfo() method.
  3. Specify the following options in the php.ini configuration file:
    • mbstring.internal_encoding = CHARACTER_ENCODING_OF_TARGET_LANGUAGE
    • mbstring.http_output = UTF-8
    • output_handler = mb_output_handler
  4. Restart the IIS service using the iisreset command.
  5. Set the target language as default for non-Unicode applications.

Search Words

d

office 365

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF