The Log Files page displays links to all log files. The main grid lists log files in alphabetical order by name.
Next to each log file entry is a list of Logger Names, that is, those pages or events that contribute entries to that log. For example, the audit.log file captures events from com.ibi.uoa, com.ibi.config, com.ibi.uoa.caster_config, com.ibi.content, and others. The Log Level field, next to each Logger, identifies the level of events captured by that contributor.
Event levels are cumulative. Events captured by a higher level are included when you select a lower level. For example, if you set the level to Warn, you capture Fatal level and Error level events as well as events that generate a warning.
The levels are defined below:
The log levels assigned to the audit log files are preset, and are not available for updates. You can adjust the log level assigned to any of the other log files. However, when you recycle the application server, all log levels revert to their default value.
The Zip All button saves copies of the current version of all log files into a single zip file. You can use this button to capture records of system events whenever necessary. The log files you capture include records of events from the start of the current day until the time you create the zip file. Event records captured in the log files support troubleshooting and analysis.
Note: The Log Files page does not display Web Services traces or client traces. To view these traces, open the Session Viewer or the Session Monitor.
Log pages list detailed records of system events that were captured in a log file in order of the time of their occurrence, from the earliest event on the day of the log to the most recent.
To open a log file for review, click a link from the Log Name column on the Log Files page. The page for your selected log file opens in a separate window.
The name of the log file appears at the top of the page. A list of earlier versions of that log file also appears at the top of the page. This list contains all previous versions of that log file that are currently available in the drive:\ibi\WebFOCUS_BUE82\WebFOCUS\logs directory.
The New Trace Lines link appears beneath the file name. Click this link to refresh the log page with entries for system events that occur after you open it. New records are posted to a log file automatically. To protect the integrity of this information, no one can use a log page to update or change log file records.
The Bottom link takes you directly to the last entry in the file. This link is useful when you must review a file with a large number of entries and you want to move directly to the most recent event. Similarly, the Top link, which appears below the last entry, returns you to the first entry in the log file and the features that appear on the top of the page.
The list of individual event entries begins below the Bottom link. Individual entries start with the date and time, in hours, minutes, seconds, and milliseconds, that an event took place. A code name identifying the category of event and the specific event itself follows the date and time. A full description of the event comes next. This description includes any messages generated by the system in response to the event.
You can use the log page to review and search for records of specific events in response to a query from a customer service support team member. The Find command in your browser can help you search for an event by a unique message, event name, or timestamp. You can also scroll through records to locate an event.
When your review is complete, close the log page window. You can use the Save or Print command in your browser to save or print a copy of the log page, or you can capture a zipped copy of it using the Zip All button from the Log Files page.
You can now track when ReportCaster Configuration settings are changed. This feature enables you to keep continuous records of how and when ReportCaster Configuration settings are changed, and to comply with any regulatory auditing requirements of your organization. To access the audit log file, launch the Administration Console, click the Diagnostics tab, and then click Log Files. In the Log Name column, click the audit link.
When you change ReportCaster Configuration settings, a record of the event, labeled as caster_config, is created in the audit.log file. Before changes to the ReportCaster Configuration settings are saved, the previous settings of the ReportCaster Configuration tool are recorded in a timestamped dserver.xml file. This file is saved in the following directory:
where nn is the WebFOCUS BUE release number.
After you run a schedule, or use the Purge Job Logs utility, you can select the corresponding job log stored in the ReportCaster Console to download the trace files that were created by the job.
Note: To receive trace files for a ReportCaster job, traces must be enabled for the job.
The job logs appear in the right panel.
The Download Trace Files menu option appears.
The Windows Save dialog box displays, from which you can save the trace files to your machine. The Job Id of the log becomes the name of the zip file to be opened or saved.
You can use the performance log to analyze the resource utilization of schedules in WebFOCUS Business User Edition. This log records the processing duration of individual schedules and schedule components.
To access the performance log, navigate to the ReportCaster Console. On the ribbon, in the Manage group, click the Server Log drop-down arrow to view the Server Log menu, where you can click the performance.log option.
Note: If the Manage Server Group is not visible, click the Server Status button in the Show group.
The performance log feature is turned off by default. To activate performance log recordings, click Turn On Server Performance Trace.
The performance.log records the following information in each record: