Architecture

BMC PATROL for IBM DB2 UDB enables you to monitor the Local or Remote IBM DB2 instances or Direct IBM DB2 Database. A typical architecture for BMC PATROL for IBM DB2 UDB is as follows:

Local monitoring

local monitoring.jpg

JDBC monitoring

JDBC monitoring.jpg

Remote monitoring

Remote monitoring.jpg

Data collection details

In local monitoring, BMC PATROL for IBM DB2 UDB starts a JAVA process. This JAVA process runs local DB2 commands to get the list of instances and databases. For each running database JAVA is connected to it via JDBC API and starts collecting the data.
For remote monitoring the JAVA process identifies where the remote DB2 server is running and based on the OS he creates a remote client connection, for Windows it will be PowerShell and for UNIX it will be SSH, then the same logic will be applied as local monitoring.
In the first inventory poll, the JAVA process discovers the IBM DB2 system (instances, databases and partitions) and creates the discovery tree for PATROL. JAVA also discovers the IBM DB2 DiagLogs in the first discovery poll.

After the discovery is complete, the JAVA collector starts collecting availability for the IBM db2 instances, databases and partitions, the default availability poll cycle is 1 min. the java process also start to collect data performance, the default data performance poll interval is 10 minutes, the JAVA also collected the DiagLog metrics the default collection cycle is 5 minutes, all the poll cycles are configurable.

BMC PATROL for IBM DB2 UDB collector details

The following table lists different BMC PATROL for IBM DB2 UDB collectors and explains how they work:

Collectors	Explanation
ConfigurationManager (15 sec)	Runs every 15 sec (default) and is responsible for checking if there was any change in the pconfig area.
ChannelListener (2 sec)	Responsible for opening a channel and starts a Java process and to listen to the java channel for incoming data
AutoDiscovery (24 hour)	Run force discovery