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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Example of Processing Files on Managed Nodes<br />

About OVO Language Support<br />

About Character Code Conversion in OVO<br />

In an English-language environment, OVO could process managed node<br />

files as follows:<br />

Scenario OVO agent-processing character set is ROMAN8.<br />

LANG=de_DE.iso88591<br />

opcmsg msg_text=“This is a message with ä, ü,<br />

ö”<br />

Conversion Input conversion of the opcmsg is from ISO8859-1 to<br />

ROMAN8 before the OVO message interceptor<br />

evaluates the message attributes.<br />

Output conversion, before forwarding the message to<br />

the management server, is from ROMAN8 to<br />

ISO8859-1/WE8ISO8859P1 (the database character<br />

set).<br />

Tips for Processing Files on Managed Nodes<br />

On <strong>HP</strong>-UX, you can define different character sets for different managed<br />

nodes. Define the character set most frequently used on each managed<br />

node. For example, if you use mostly monitor logfiles with ROMAN8<br />

characters, you should use ROMAN8 for your managed nodes. Similarly,<br />

if your environment mostly generates input data for OVO in the ISO<br />

8859-15 character set, you should set the managed node character set to<br />

ISO 8859-15. When in doubt, use ISO 8859-15.<br />

NOTE You can use a different character set for each managed node. You<br />

determine the managed node character set by the character sets used in<br />

your environment.<br />

Chapter 8 313

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

Saved successfully!

Ooh no, something went wrong!