16.10 - Tracking Events - Teradata Ecosystem Manager

Teradata Ecosystem Manager API Reference

prodname
Teradata Ecosystem Manager
vrm_release
16.10
created_date
June 2017
category
Programming Reference
featnum
B035-3204-067K

To verify the events generated by the API calls, use one of two ways. The end-to-end way requires the published event to be up and running and /opt/teradata/client/em/conf/apiconfig.xml must point to the correct Ecosystem Manager Publisher. For information on how to install and run Ecosystem Manager Publisher, refer to Teradata Ecosystem Manager Installation, Configuration, and Upgrade Guide.

If the Ecosystem Manager Publisher is correctly configured, the Ecosystem Manager portlets can be used to view events and alerts.

If no instances of the Publishers are running, the second way to verify if events generated correctly is to open the datastore file. Each event is separated by 
--- END OF RECORD ---. After Publisher resumes, messages are sent and cleaned from the datastore.