Registering an OMEGAMON Collector on zLinux as Db2 instance owner

As an alternative to registering OMEGAMON Collector using the script db2peage-config, you can register and unregister OMEGAMON Collectors at any time without root authorization.

1. Log on to the DB2 instance on which Performance Expert Agent for Db2 Connect Monitoring is installed.
2. Change to the BIN folder of the installation directory of Performance Expert Agent for Db2 Connect Monitoring.
3. Stop Performance Expert Agent for Db2 Connect Monitoring by entering ./e2e --stop
4. Enter one of the following commands on the command line depending on what you want to do:
   1. To add an OMEGAMON Collector that is located on z/OS® to the e2e.ini file of Performance Expert Agent for Db2 Connect Monitoring, enter ./e2e --addhost <host name> <DB2 port> <location name> <mainframe flag> <user login> <user password>

      where the variables represent the following:

      <host name>

      the network host name or IP address of the DB2 subsystem on which the registered OMEGAMON Collector runs.

      <DB2 port>

      the port number of the DB2 subsystem on which the registered OMEGAMON Collector runs.

      <location name>

      the location name of the DB2 subsystem on which the registered OMEGAMON Collector runs.

      <mainframe flag>

      whether the OMEGAMON Collector is located in a mainframe environment.

      For a z/OS environment, specify Y. For a multiplatform environment, specify N.

      <user login>

      the user ID of the user who has access to the DB2PM database in Performance Warehouse on the OMEGAMON Collector side.

      <user password>

      the password of the user who has access to the DB2PM database in Performance Warehouse on the OMEGAMON Collector side.

      Important: You should not include the password in the --addhost command if it contains special characters because the command might not work with special characters. You are then prompted to enter the password afterwards on a separate line. You can include the following special characters in passwords, but they might not work on the command line:

      ! @ # $ % ^ & ( ) [ ] { } * . - _ / \ ? : ; , < > = ' " + |
   2. To later change the user ID and password for a registered OMEGAMON Collector, enter ./e2e --change <number> <user login> <user password>

      where the variables represent the following:

      <number>

      the number of the OMEGAMON Collector for which user login and password are to be changed.

      <user login>

      the user ID of the user who has access to the DB2PM database in Performance Warehouse on the OMEGAMON Collector side.

      <user password>

      the password that is to be changed.

      Important: You should not include the password in the --change command if it contains special characters because the command might not work with special characters. You are then prompted to enter the password afterwards on a separate line. You can include the following special characters in passwords, but they might not work on the command line:

      ! @ # $ % ^ & ( ) [ ] { } * . - _ / \ ? : ; , < > = ' " + |
   3. To see the numbers of all registered OMEGAMON Collectors, enter ./e2e --listhosts
   4. To remove the registration entry of an OMEGAMON Collector from the e2e.ini file of Performance Expert Agent for Db2 Connect Monitoring, enter ./e2e --removehost <number>

      where <number> denotes the number of the OMEGAMON Collector for which you want to remove the registration entry.

   5. To test the connection, enter e2e --test <number>
5. Ensure that the following configuration for the OMEGAMON Collector PESERVER subtask is available before you start DB2 Connect monitoring:

   SNAPSHOTHISTORY=Y

   for Snapshot History processing

   SHDB2CONNECTAPPLICATION=Y

   if you want to collect DB2 Connect application data

   SHDB2CONNECTSYSTEM=Y

   if you want to collect DB2 Connect system data

6. When DB2 Connect monitoring is active for more than one server, ensure that only one of these servers accesses the collected data on the corresponding DB2 subsystem at a time.

   You must consider this if you use one of the following:

   • More than one OMEGAMON for Db2 PE
   • DB2 Performance Expert for z/OS and OMEGAMON for Db2 PE, or both, or several of both
   • OMEGAMON for Db2 PE in a data sharing group running on different logically partitioned modes (LPARs) in a sysplex environment