28 IBM Tivoli Monitoring for Network Performance V2.1: The Mainframe Network Management Solution
More discussion on monitors and the data related to them can be found in 6.5.1,
“Monitored metrics” on page 138.
2.3.4 Setting options
The itmnp.properties file contains configuration parameters for the monitor. This
file is typically copied to /etc/itmnp/ directory. This directory is specified in the
variable $CONFIG_DIR within itmnpMonitor.sh shell script. The itmnp.properties
file consists of the configuration parameters for the monitor. The detailed
information for each parameters are provided as comments in the member; see
our examples in “AIX itmnp.properties” on page 218 and “z/OS itmnp.properties”
on page 218.
The parameters can be grouped into:
򐂰 Monitor configuration
monitor_hostname The fully qualified domain name of the system where
the monitor is located. This name is used to retrieve
the monitor configuration from the Web application
and must match the monitor name provided when
defining the monitor configuration.
bind_interface The interface or stack which the monitor binds on this
host.
CSAPIport The first of the two ports used by the monitor for
internal communication. The monitor uses the port and
the next numbered port (such as 1670 and 1671). This
is the port monitor_cs390 process is listening on.
򐂰 Communication between the monitor and Web application; see also 2.4,
“Communication and security” on page 34
local_httpport The port number that the monitor listens on, and the
Web application used to communicate with the
monitor. This port is used by the Web application to
transmit the monitor configuration.
Memory data z/OS Communications Server management
interfaces.
Response time Result of ping command.
SNMP performance data Use SNMP queries to collect performance
data that is stored in MIBs.
Performance data category Data source
Chapter 2. Components and architecture 29
WAS_hostname The host name of the WebSphere Application Server
where the Web application runs.
WAS_httpport The port number that the monitor uses to
communicate with the Web application.
socksServer, socksPort
The fully qualified URL and port for the Socks server
the monitor will use to communicate with the
WebSphere Application Server. (Optional)
򐂰 Database properties
DBName The name of the DB2 database where the
performance data will be stored.
DBUserName The database user who has the authority to store data
in the DB2 database.
DBPassword The password of the DB2 database user.
DBHostName The fully qualified host name of the system where DB2
is located. This is the same system as the WebSphere
Application Server host name.
DBPort The port number that DB2 database server is listening
on. Typical value for AIX is 50000, while in z/OS you
can see it from the DSNL004I message in the DB2
startup.
DBDriverType The type of driver used to establish connections with
the database. Use the value of UNIVERSAL.
DBCacheDirectory The directory to be used by the monitor to store the
collected data in a local cache. This cache stores the
collected data before it is sent to the DB2 database.
This directory is only used when the DBCachRowLimit
and DBCacheTimeout are > 1.
DBCacheTimeout The maximum number of seconds that the monitor will
store data in a local cache before sending the data to
the DB2 database. Data will be transferred to the DB2
database when either the maximum number of
seconds is reached or the maximum number of rows is
reached.
Tip: Although this parameter defaults to DBDriverType=UNIVERSAL, we
found that we need to comment it out for a DB2 for z/OS database. Explicitly
specifying DBDriverType=UNIVERSAL make the connection to a distributed
DB2 database.

Get IBM Tivoli Monitoring for Network Performance V2.1 The Mainframe Network Management Solution now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.