Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide

12.1.6 Operation in a multi-language environment

You can deploy JP1/IM in a system set up with multiple languages. For example, JP1/IM - View is able to simultaneously display JP1 events that are registered in JP1/Base under different language codes^#.

#: Some extended characters, special characters, and control codes may not display correctly or be recognized as different characters in JP1/IM - View, regardless of whether JP1/IM is being run in a multi-language environment. For details, see 1.3 Notes on operations in windows in the manual Job Management Partner 1/Integrated Management - Manager GUI Reference.

However, there are several conditions that apply when running JP1/IM in a multi-language environment. These conditions may influence your system configuration or manner of operation.

Organization of this subsection

(1) System conditions

(2) Server conditions

(1) System conditions

The following conditions apply to the JP1/IM system itself (the entire JP1/IM system composed of managers and agents).

Two-byte characters in automated actions will appear garbled.^# If you specify machine-dependent characters, the automated action may not work correctly.
#: Level 1 and level 2 Japanese character codes will display normally.

Note the following when the system contains an agent using a UTF-8 locale:

Version 8 or later of JP1/Base must be running in the UTF-8 locale environment. Also, any machines to which that agent forwards events must also be running version 8 or later of JP1/Base.

The manager must be running version 8 or later of JP1/IM - Manager and JP1/Base.

A system with hosts running version 7 of JP1/IM or JP1/Base will be unable to properly deal with JP1 events issued from the UTF-8 locale environment (the hosts will be unable to display the JP1 events or execute automated actions correctly).
In this case, make sure that the JP1/Base in the UTF-8 environment is version 8 or later, and set up JP1/Base to run in compatibility mode. For details about how to do so, see the description of the pre-setup tasks in the Job Management Partner 1/Base User's Guide.

The following conditions apply when the system contains a combination of hosts running Japanese^#1 and English^#2 language environments:
#1: Hosts running Japanese versions of the operating system and software, in which the LANG environment variable is set to Japanese.
#2: Hosts running English or Japanese versions of the operating system and software, in which the LANG environment variable is set to English.

Hosts configured as an integrated manager or base manager must use a Japanese language environment.

The manager configured directly above an agent running an English language environment must be running a Japanese language environment.

On the manager, JP1/IM - Manager and JP1/Base must run in a Japanese language environment. If you also install JP1/IM - View, install the Japanese language version.

If you intend to monitor the system using the Central Console, when you connect from JP1/IM - View to JP1/IM - Manager (JP1/IM - Central Console), both must be running Japanese language environments.

If you intend using the Web-based JP1/IM - View to monitor events, you must use a Japanese Web browser running under a Japanese OS to connect to JP1/IM - Manager (JP1/IM - Central Console) running in a Japanese language environment.

In a cluster system, both JP1/IM - Manager and JP1/Base must be running in a Japanese language environment.

The following figure shows an example configuration of a system that combines hosts running Japanese and English language environments:

Figure 12-1 Example system configuration comprising hosts with Japanese and English language environments

Notes:

Note the following when operating a system comprising hosts running both Japanese and English language environments.

Definition files and settings files
When you expect definition files and settings files to be used by JP1/Base in an English language environment, make sure that only alphanumeric characters (ASCII) are used for the file names, the characters in the files, and the values of any attributes. If you create and distribute these files from JP1/IM - Manager, avoid distributing files that contain 2-byte characters.

Automated actions
Note the following when executing an automated action on a target host running an English language environment:

Do not specify an action that contains 2-byte characters. If you specify such an action, the action results may be garbled and display incorrectly, or the action may fail to execute altogether.

When defining variables in the automated action definition, do not specify event information that contains 2-byte characters. If you specify such information, the action results may be garbled and display incorrectly, or the action may fail to execute altogether.

Do not use 2-byte characters in the file name of the environment variable definition file used by the automated action, or in the file itself. If the file or its name contains 2-byte characters, the action results may be garbled and display incorrectly, or the action may fail to execute altogether.

Do not specify an automated action that outputs execution results containing 2-byte characters. If you specify such an automated action, the action results may be garbled and display incorrectly.

Command execution from JP1/IM - View
Note the following when executing a command on a target host running an English language environment:

Do not specify a command that contains 2-byte characters. If you specify such a command, the command execution results may be garbled and display incorrectly, or the command may fail to execute altogether.

Do not use 2-byte characters in the file name of the environment variable definition file used at command execution, or in the file itself. If the file or its name contains 2-byte characters, the command execution results may be garbled and display incorrectly, or the command may fail to execute altogether.

Do not specify a command that outputs execution results containing 2-byte characters. If you specify such a command, the command execution results may be garbled and display incorrectly.

Searching for events
Do not use 2-byte characters in search conditions when conducting an event search on a JP1/Base in an English language environment. If you specify a 2-byte character, the search will not be conducted correctly.

(2) Server conditions

The following conditions apply to individual servers (all physical and logical hosts within a given machine).

You must use the same language version (English or Japanese) for JP1/IM and JP1/Base.

In UNIX systems, the same language code (the locale set for the host by the LANG environment variable or similar) must be set for JP1/IM and JP1/Base.

[Contents][Back][Next]

[Trademarks]