OMNIbus Web GUI 7.3.1 comes with the updated Tivoli Integrated Portal (TIP) version 2.1 framework. OMNIbus Web GUI and TIP are now resided on different home directories, Here, I will use <omnibus_webgui> and <tipv2_home> directories. For example,
There are 5 types of logs:
- Client logs
Web GUI installer uses InstallAnywhere (IA), Deployment Engine (DE), and Composite Offering Installer (COI), and the main log is IBM_Tivoli_Netcool_OMNIbus_Web_GUI_Install-00.log (sometimes referred to as the IA log), which can be found user's home directory. Unfortunately, this log usually only say the issue is found (at a high level) and the rest of the log seems to be successfully undo the steps.
To drill down further, see the log file MachinePlan_localhost.log, which is the logging of all the "ant" tasks that had been executed by COI. This log file is reside in the directory, <omnibus_webgui>\_uninst\OMNIbusWebGUI\plan\install\MachinePlan_localhost\logs\[INSTALL_DATE_TIME]
Further drill down is possible to pin-point where the failed ant task, would lead to the specific files in TIP logs.
The directory <tipv2_home>\logs contains various files, namely output file (*.out) and error file (*.err) for specific tasks executed by COI.
OMNIbus Web GUI includes the ESS Server as a component, and its installation logs reside in <tipv2_home>\..\tipv2Components\ESSServer\logs
The directory <tiv2_home>\profiles\TIPProfiles\logs contains TIP server logs. In particular, all Web GUI server logs into its sub-directory called ncw.
If profiling is enabled, the server log can be used to monitor:
Objectserver Query & Update
Event Data (eg: event lists/integrations)
Event summary Data (eg: dashboard/maps)
Metric Data (eg: gauges)
Authentication & Authorization
This refers to the web browser Java plugins logs.