Upgrading OMEGAMON Data Connect

Upgrade all instances of OMEGAMON® Data Connect to this APAR level now, to ensure that all instances can receive data from the upgraded OMEGAMON Data Broker. Use the new configuration validator command-line tool to validate your OMEGAMON Data Connect configuration files.

About this task

Procedure

  1. Ensure that the updated OMEGAMON Data Connect installation directory supplied with the PTF for this APAR is used by all instances of OMEGAMON Data Connect.
    For example, if you run OMEGAMON Data Connect on platforms other than z/OS®, then ensure that you use the files in the updated SMP/E target location of OMEGAMON Data Connect on z/OS to refresh the OMEGAMON Data Connect installation directories on those other platforms.

    For details on the SMP/E target location of OMEGAMON Data Connect, see Installing OMEGAMON Data Provider.

  2. Use the new configuration validator to validate your OMEGAMON Data Connect configuration files.

    This APAR introduces improved validation of configuration parameters. Previously, OMEGAMON Data Connect ignored unknown parameters in the configuration file. Now, if the configuration file contains an unknown parameter, OMEGAMON Data Connect fails at startup.

    This APAR also introduces the configuration validator, a command-line tool that you can use to validate the OMEGAMON Data Connect configuration file before starting OMEGAMON Data Connect.

    Use the configuration validator now to reveal errors in the configuration file that OMEGAMON Data Connect was previously silently ignoring, and also later, whenever you edit the configuration file, as a preflight check before starting OMEGAMON Data Connect.

    For example, at a shell prompt, change to the bin directory under the OMEGAMON Data Connect installation directory, and then enter the following command:

    ./validate -t=connect /var/omdp/prod-a/config/connect.yaml

    replacing /var/omdp/prod-a/config/connect.yaml with your configuration file path.

  3. If the configuration validator reports errors, edit the configuration file to fix the errors, and then run the configuration validator again. Repeat until the configuration validator reports that the configuration file is valid.