DB2 Remote Windows connection setup

Enter the name of the remote PowerShell user (this user must exist where the IBM DB2 system is installed) with permission to run:

• DB2 CLP commands
• "df" OS command on the following DB2 files:
  • logpath file: Received by running the query - select NAME,VALUE from SYSIBMADM.DBCFG where (DBPARTITIONNUM=<partition number>)
  • DB_PATH file: Received by running the query - select DB_PATH from SYSIBMADM.SNAPDB where (DBPARTITIONNUM=<partition number>)

Note: If the IBM DB2 database user field is left blank, this user needs the minimum SYSMON authority with DATAACCESS privileges.

Select an authentication protocol to connect to the remote host:

• Negotiate - Negotiate authentication automatically selects between the Kerberos protocol and NTLM authentication, depending on availability.
• Basic - Basic authentication sends a Base64-encoded string that contains a username and password for the client. Base64 is not a form of encryption and should be considered the same as sending the username and password in clear text. If a resource needs to be protected, consider using an authentication scheme other than basic authentication.
• Kerberos - The Kerberos protocol is used if it is available; otherwise, NTLM is tried. Kerberos authentication significantly improves upon NTLM. Kerberos authentication is both faster than NTLM and allows the use of mutual authentication and delegation of credentials to remote machines.

Enter the name of the user with permissions to connect and run SQL queries on all DB2 databases. The user should have minimum SYSMON authority with DATAACCESS privileges.

If this field is left blank, then the remote PowerShell connection user and password will be used.

Password

Confirm password

• Enter the full path (do not use the short path format) to the JRE directory on the PATROL Agent host. The Java version must be 8 or later.
  For example:
  • Windows: C:\Program Files (x86)\Java\jre8
  • Unix\LINUX: /usr/java8_64
• Alternatively, you can also use the $JAVA_HOME environment variable in this field. If you use the $JAVA_HOME variable, the Java location depends on the $JAVA_HOME you declare in you PATROL agent host.
• If this field is left blank, the KM looks for the Java executable in the Patrol3\openjdk and Patrol3\jre64 locations.

Enter the name of the OS JVM user (this user must exist where the PATROL Agent and DB2 KM are installed) with permission to run the Java process.

Note: If this field is left blank, the KM will use the user that is running the PATROL Agent.

Select the monitoring collection details for monitoring the DB2 instance.

Availability - Select this option to check the availability of instances, connections, and databases.

Full data monitoring - Select this option to collect all the monitored groups.

Custom data monitoring - Select this option to collect only the monitored groups selected from the custom data module types.

• Applications - This group is responsible for collecting applications instances and parameters and displaying them under each partition of a database.
• Buffer Pools - This group is responsible for collecting buffer pools instances and parameters and displaying them under each database’s partition.
• Capacity - This group is responsible for collecting capacity parameters and displaying them under each partition of a database. 
• HADR - This group is responsible for collecting HADR parameters and displaying them under each partition of HADR standby and primary databases.
• Instance Attributes- This group is responsible for collecting instance attributes and displaying them under the partitions container node of the instance.
• Instance Partition Attributes - This group is responsible for collecting instance's partition's attributes and displaying them under each instance’s partition’s node.
• Locks - This group is responsible for collecting lock parameters and displaying them under each partition of a database.
• Logs - This group is responsible for collecting log parameters and displaying them under each partition of a database.
• Performance - This group is responsible for collecting performance parameters and displaying them under each partition of a database.
• Recovery - This group is responsible for collecting recovery parameters and displaying them under each partition of a database.
• SQL - This group is responsible for collecting SQL parameters.
• Tablespaces - This group is responsible for collecting table spaces instances and parameters and displaying them under each partition of a database.