If you have already configured an OMEGAMON®
runtime environment to send collections to OMEGAMON Data Provider,
then follow the steps here to add more.
Procedure
-
Update the collection configuration in the
RKANPARU(KAYOPEN) member to select the additional collections.
Tip: Update KAYOPEN before you create the collections. Performing
the configuration in this order ensures that attributes go to the correct destinations as soon as
you create the collections.
- Reload the collection
configuration in the affected monitoring agents.
- If necessary, update and then reload the OMEGAMON Data Connect configuration.
Whether you need to perform this step depends on whether the current OMEGAMON Data Connect configuration already selects the corresponding table
for forwarding. For example, if OMEGAMON Data Connect is already
configured to forward all tables from a monitoring agent, and you are adding a collection for
another table from that agent, then you don't need to perform this step.
- Create the collections.
To create historical collections, you use the OMEGAMON enhanced 3270 user
interface (e3270UI) or the Tivoli® Enterprise Portal
(TEP). For more information about creating historical
collections, see the OMEGAMON documentation for e3270UI
and TEP.
- Check the RKLVLOG output data set of the affected monitoring agent
jobs for KPQH038I messages.
- Check the STDOUT output file from OMEGAMON Data Connect for KAYC0008I and KAYC0033I messages.
- Check that the attributes are arriving at your analytics platform.
For
example, in Elastic, check that an index has been created for the table.