Register remote Windows DB2 environment dialog box

Enter a unique environment name for monitoring the DB2 environment. A container will be created with the environment name. This environment will hold all the DB2 instances. BMC recommends you to provide only alphanumeric characters in environment name.

Enter a valid powershell remote Host name or an IP address. Each environment can contain a single host name. BMC recommends you to provide only alphanumeric characters in environment name.

Enter the name of a user with permissions to run DB2 commands. The user should have at least SYSMON user 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 user name and password for the client. Base64 is not a form of encryption and should be considered the same as sending the user name and password in clear text. If a resource needs to be protected, strongly 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 path to the installation base directory. Files are installed to the following directories under the installation base as follows:

For example:

Windows: C:\Program Files\IBM\SQLLIB 

UNIX: /opt/ibm/db2/V10.5

Enter the path to the J2EE folder where the jar files reside.

For example:

Windows: C:\Program Files (x86)\Java\jre7

Unix\LINUX: /usr/java7_64/

OK

Click to apply the configuration.

Close

Click to close the dialog box.

This group is responsible to collect buffer pools instances and parameters and display them under each database’s partition. You can see the queries and commands used to collect the group’s instances and parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_BUFFERPOOLS.xml.

This group is responsible to collect instance parameters and display them under the partitions container node of the instance. You can see the commands used to collect the group’s parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_INSTANCE_PARAMETERS.xml.

This group is responsible to collect instance’s partition’s parameters and display them under each instance’s partition’s node. You can see the commands used to collect the group’s parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_INSTANCE_PARTITION_PARAMETERS.xml.

This group is responsible to collect HADR parameters and display them under each partition of HADR standby and primary databases. You can see the queries used to collect the group’s parameters in the XML. This group will be active only when the database is HADR database.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_HADR.xml.

This group is responsible to collect lock parameters and display them under each partition of a database You can see the queries used to collect the group’s parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_LOCK.xml.

This group is responsible to collect capacity parameters and display them under each partition of a database. You can see the queries used to collect the group’s parameters in the XML. The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_CAPACITY.xml.

This group is responsible to collect applications instances and parameters and display them under each partition of a database. You can see the queries used to collect the group’s instances and parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_APPLICATIONS.xml.

This group is responsible to collect table spaces instances and parameters and display them under each partition of a database. You can see the queries used to collect the group’s instances and parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_TABLESPACES.xml.

This group is responsible to collect log parameters and display them under each partition of a database. You can see the queries used to collect the group’s parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_LOG.xml.

This group is responsible to collect SQL parameters and display them under each partition of a database. You can see the queries used to collect the group’s parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_SQL.xml.

This group is responsible to collect recovery parameters and display them under each partition of a database. You can see the queries used to collect the group’s parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_RECOVERY.xml.

This group is responsible to collect performance parameters and display them under each partition of a database. You can see the queries used to collect the group’s parameters in the XML.

The XML file used to collect this monitored group is located at <Patrol Home>/Patrol3/pso/xml/ PSO_PERFORMANCE.xml.