13.12.2012 Views

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

About OVO Language Support<br />

About Language Support on Managed Nodes<br />

Types of Character Sets in a Japanese-language Environment<br />

If you operate in a Japanese environment, your database character set is<br />

Shift JIS. Table 8-9 shows the Japanese-language character sets that<br />

are supported for OVO managed nodes.<br />

Table 8-9 Verified Character Sets on Managed Nodes (Japanese)<br />

OVO Platform Character Set<br />

Management<br />

server on <strong>HP</strong>-UX<br />

and Sun Solaris<br />

<strong>HP</strong>-UX, Solaris Shift JIS, EUC a , ASCII<br />

Linux EUC a , ASCII<br />

Windows Japanese ANSI Code Page 932 b ,<br />

ASCII<br />

AIX, Tru64 UNIX Shift JIS, EUC a , ASCII<br />

a. 2-byte Extended UNIX Code.<br />

b. Code Page 932 is analogous to Shift JIS.<br />

Changing the Character Set for a Managed Node<br />

NOTE Changing the character set of a node is only possible for NCS- or<br />

DCE-based managed nodes. For HTTPS-based managed nodes it is not<br />

necessary to change the character set for the OVO agent because the<br />

OVO agent always converts the node’s characters from the node’s<br />

character set to UTF8 before the data is transferred to the management<br />

server.<br />

You can change the character set used for a managed node in the<br />

Advanced Options window of the Add/Modify Node window. The<br />

managed node processes are updated automatically. All managed node<br />

processing is then performed using this new character set.<br />

Chapter 8 301

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!