Chapter 5 265
Configuring ITO
Database Reports
a. For more information about the logfiles, see the section “On
The ITO Management Server” on page 460.
You can define additional reports by customizing the file:
/etc/opt/OV/share/conf/OpC/mgmt_sv/reports/<lang>/\
oper.rpts
Whenever an operator saves report output to a file without specifying an
absolute path (starting with “/”) the file is stored in the operator’s Unix
working directory, which is defined by $OPC_HOME (if set), $HOME, or
/tmp in that order or priority. In addition, the file is owned by the
operator’s unix user, not by opc_op, unless the operator logged in as unix
user opc_op. The permissions of the file will be according to the umask as
set before the ITO Operator GUI was started.
Long-term Reports
ITO allow’s you to generate statistical and trend-analysis reports over a
defined period of time. These reports can be configured to cover periods
from as little as a few days to as much as weeks or even months.
Note that the tool /opt/OV/bin/OpC/opcdbmsgmv moves all messages
that are marked as acknowledged to the history-message tables in the
database, where they are retained with little or no negative impact on
operational tasks. Although automatically started every two hours by
the ITO control manager, opcdbmsgmv also may be called manually for
trouble-shooting purposes.
Report Security
For reasons of security, ITO restricts access to the database for
report-writing tools to a database user, opc_report, who has read-only
access. The opc_report user makes use of the Oracle report role
Sel. History Details Detailed report on selected history
(acknowledged) Messages
Sel. Pending Messages Brief report on selected pending messages
Sel. Pending Details Detailed report on selected pending
messages
Report Name Description
