| Oracle® Real-Time Collaboration Administrator's Guide 10g Release 1 (10.1.2) Part Number B25460-03 |
|
|
View PDF |
| Oracle® Real-Time Collaboration Administrator's Guide 10g Release 1 (10.1.2) Part Number B25460-03 |
|
|
View PDF |
Oracle Real-Time Collaboration provides reports about conference histories, usage trend information, user feedback analysis, system incidents, and system security. Some aspects of these features require postinstallation configuration. This chapter describes the configuration steps, then describes how you can use the Oracle Real-Time Collaboration reports to manage your system. It contains the following sections:
The reports discussed in this chapter are available from both the Reports tab and the System tab. Users with business monitor or business administrator privileges can view the reports available from the Reports tab. Only users with the business administrator role can view the reports available from the System tab. See "Setting User Roles" for details about how to set these roles.
|
Note: This chapter provides an overview of the types of data presented in the reports, and how you can use them. Detailed descriptions of each item in each Oracle Real-Time Collaboration report are included in the online Help. For details about individual data points, click Help on any report Web page. |
Oracle Real-Time Collaboration keeps records about Web conferences and instant messages in two different ways:
Archives contain the historical data about individual conferences and instant messages. Archives are used by conference hosts and attendees, or persons who sent or received instant messages, to review the data they exchanged.
Reports provide diagnostic and management information to system administrators to let them analyze system performance.
The Archives pages show only those conferences or messages that the current user participated in, or conferences that the user has been granted access to by a conference host. Administrators do not have any special privileges to view archives of conferences or messages that they did not participate in.
If your users request access to a conference archive, forward their request to the conference host, who can assign the user privileges to view the conference using the Update button in the Archives pages. The online Help for Oracle Real-Time Collaboration describes the Archive page options in detail.
For more information about the creation and contents of archives, see Chapter 7.
The Conferences page under the Reports tab lets you view information about each individual conference. Users with either the business monitor or business administration roles may view the tab and its reports.
The main Conferences page includes basic information about each conference, including its duration, the list of attendees, any ratings or comments made by the host, and whether the conference finished normally or was abandoned or otherwise failed. You may want to use this page to get a general idea about conference traffic for a specific time period (Last 1 Day, Last 7 Days, and so forth). You also use this page to locate specific conferences in order to get more details about them. You can use the Filter By field to search for specific conferences by ID, title, or host's login name, or to search for conferences held on a particular site.
Clicking the Conference Details icon displays the Details page, showing basic conference statistics such as start and stop times, whether voice or data recording was used, whether recordings have been played back from the conference archives, and any feedback from the conference host.
Clicking the Diagnostics tab on the Details page displays a page that lists any events that took place during the conference. You can choose to view only errors or all events. You can also click links to view further diagnostic detail:
Archived log file lists every event that has taken place during this conference, including actions such as entering or exiting the conference, or changing the properties of the conference (for example, the host assigns presenter status to a participant). Use this page to review events that occurred during a conference, especially when troubleshooting a conference that may have had problems. This report is the same as the running log file report available from the Monitor tab while the conference was running (see "Monitoring Current Conferences" for details). All log files are also available from Logs under the System tab.
Instance diagnostics lists details about the Oracle Real-Time Collaboration server processes running on the instance that served this conference. You can use this information to manage current processes. You can also end processes directly from this page, if desired. This report is the same as the running diagnostics report available from the Monitor tab while the conference was still running.
Clicking the Attendees tab on the Details page displays the list of attendees that participated in this conference, and how long they participated. To see more information about an individual attendee, click Attendee Details next to the attendee's name. The resulting page lets you troubleshoot any specific issues an attendee may have had in a conference, including:
Information about how the attendee participated in the conference, including how long the attendee was in the conference, and whether the attendee attended anonymously, had to reconnect to the conference during the session, or used streaming voice.
The operating system and screen resolution of the computer the attendee used to connect to Oracle Web Conferencing, and the connection type used to connect the client to the Web Conferencing Server.
The Usage Report pages under the Reports tab provide metrics to let you analyze how the Oracle Real-Time Collaboration system is being used. You can check these reports to determine what conference modes and features are most often used, what messaging features are being used, who are the top users, and what sites have the most conference activity. Users with either the business monitor or business administration roles may view the report.
Four reports provide usage metrics. Each metric is based on one of two measurements:
Time (minutes or hours)
Usage numbers (number of users, conferences, messages, and so forth)
You can use the drop-down lists at the top of the report to display the data summarized by Days, Weeks, Months, Quarters, or Years. You can change the default ranges of these periods using the properties described in "Configuring Reports".
All reports give the count of various usage events for the current period and the percentage change over the previous period. Status arrow indicators let you easily see whether a rating trend is up or down. Graphs shows the trend of the events.
The Key Usage Metrics report provides summaries of the main metrics from each of the other reports. Use this report to get a high-level view of the number of persons using the Oracle Real-Time Collaboration system and the number and types of activities running on the system for the period.
The Web Conferencing report displays all usage statistics related to Web Conferencing. Use this report to determine the numbers and types of users and conferences; the lengths and sizes (in terms of attendees) of conferences; the features used within conferences (document sharing, voice streaming, and so forth); the number of recordings and playbacks; and the top users and sites for the time period.
The Presence and Chat report displays all usage statistics related to Oracle Messenger. Use this report to determine the number of messaging users, text and voice chat sessions, chat conferences, Web conferences started from chat, and files transferred during chat sessions for the period.
The Integration Services report shows what requests were made of Web Conferencing, Presence, and Messaging services by integrated services over the past week. Use this report to determine how much traffic on the system is being generated by the custom applications that you have created using Oracle Real-Time Collaboration SOAP and XML services. For details about creating custom applications, see Oracle Real-Time Collaboration Application Developer's Guide.
|
Note: The following data is available only in reports for the full Oracle Real-Time Collaboration system:
If you are logged in as a site administrator or are viewing usage reports for a site, the data listed here will not appear. |
A feedback form that appears at the end of every conference lets hosts give a comment (raw text feedback) in addition to rating a conference excellent, good, or poor, or providing no rating. The Feedback page under the Reports tab provides metrics evaluating this feedback, and lists the detail of every text comment. Use this report to watch for frequently asked questions, gather information about common user perceptions and issues, and respond to problems. Oracle strongly suggests that administrators review feedback reports at least once a week. Users with either the business monitor or business administration role may view the report.
|
Note: Some Oracle Real-Time Collaboration properties let you link hosts and attendees from the default feedback form to another URL, where you may display a custom-built Web form to gather additional feedback. Feedback you gather with a custom form is not included in this report. You can also use a property to suppress the feedback form entirely; if it is set to true, this report will not contain data. See "Configuring Feedback Methods" for details. |
You can use the drop-down lists at the top of the report to display the data summarized by Days, Weeks, Months, Quarters, or Years. You can change the default ranges of these periods using the properties described in "Configuring Reports".
The key metrics show the count of each rating for the current week and the percentage change over the previous time period. Status arrow indicators let you easily see whether a rating trend is up or down. A graph shows the trend of the four possible ratings over time.
The top ten conferences with poor, good, excellent, and no response ratings are listed, with their host comments. These are grouped into four tables by rating level. Only conferences with host comments are listed in the tables, so you can easily review and respond to poor comments, and compare the difference between users who rate the system highly and those who do not.
The QoS Report page under the Reports tab lets you view reports that summarize the quality of service provided by Oracle Real-Time Collaboration components to your users, and that list any incidents experienced by users while using Oracle Real-Time Collaboration tools. Users with either business monitor or business administration privileges may view the tab and its reports. Use these reports to evaluate the performance of your system, confirm issues raised by users in the Feedback report, and check the results of any performance tuning efforts.
The Web Conferencing report lets you determine how well the Real-Time Collaboration system has performed as users start and run conferences, download and run clients, and connect to conference processes. The report shows the number of conferences whose attendees had problems downloading the console client or connecting to the conference, had unacceptable join times, or who were disconnected during the conference.
You can check further details about the types of connections made (directly through the multiplexer or through mod_imeeting using HTTPS or an HTTPS tunnel), the general reasons for client download failure (for example, the attendee was using an unsupported platform), and the actual connection times in seconds or the speed of the network connection in milliseconds. Note that if you want more detail about join or download failures, you can check the Status report described later in this section.
As administrator, you can control the measure used for what is an "acceptable" join time or network connection using the AcceptableJoinLatency and AcceptableNetworkLatency properties. See "Configuring Quality of Service Measurements" for details.
The Incidents report displays the results of checks run as users attempt to enter Web conferences. You can see the number of successfully installed console clients and the number of failures, and the results of compatibility checks run on a user's system as the user attempts to connect, including details about unsupported platforms, device drivers, and so forth. Use this report to follow up on the causes for failures as users attempt to join a conference.
The Security page under the Reports tab lets you view information about the secure and key-protected conferences held on this system versus those that were not secure. User this report to determine how secure your company's conferences have been.
The report shows the count of various events for the current week and the percentage change over the previous week. Status arrow indicators let you easily see whether a rating trend is up or down. Graphs shows the trend of the events over the past months.
The following metrics are captured in the report.
Key Security Metrics: Summarizes the number of conferences and recordings that have used various methods to control access. Published conferences refers to conference archives that were published using the "List conference on public Web page" option in the Archive page for the conference. If this option was checked, the archived conference is included in the "Published" statistics for the Security report.
Conference Accessibility Statistics, Key-Protected Conference Statistics, and SSL-Encrypted Conference Statistics: Three sections of the report compare conferences by some method used to control access: the type of user invited to participate, whether a conference required a conference key, or whether a conference used SSL encryption. Then each section compares other attributes of each conference, such as whether it was published or what other access control methods were applied. Use this section to determine how many security measures are being applied to conferences at your site.
Security Statistics for Recorded Conferences: This section shows how many conference recordings are published, downloadable, or require a conference key in order to view them.
Two reports under the System tab let you monitor the activity of instances and components running within the Real-Time Collaboration system, and manage information about your Oracle Real-Time Collaboration hosts. Only users with the business administrator role can access the reports on this page.
The Status report lets you view the current status of components and instances in this system. Use it to check on general system status, check which component processes are running on which instances, and view the results of recent system availability tests. The report includes the following:
The current activity of instances and their components, including active conferences, chat sessions, and Web Client sessions.
The results of service availability reports run automatically by the system, using the runTests command. For more information about how to respond to the test results, see "Monitoring Service Availability".
Information about each running process.
Properties set on the system and instances, components, and sites within it.
You can expand or contract hierarchical lists of information, and see additional details about current conference sessions, Web client sessions, test results, and sites.
The Configuration report lets you record and view information about each host for this Oracle Real-Time Collaboration system. Use it to create new host names or change information about a host.
The Logs page under the System tab lets you view all logs recorded by various Oracle Real-Time Collaboration processes. Use these files to help you analyze the performance of various processes, and to troubleshoot specific issues by component, process, and date of the incident.
Log files are stored in the $ORACLE_HOME/imeeting/logs directory, and are recorded and named by date. Some logs are plain ASCII files, and others are XML files that display data in tables.
The Logs page lets you view the logs listed in Table 6-1.
Table 6-1 Logs Viewable in the System Logs Report
Some additional logs are available in the /logs directory. You can access all logs directly from your file system. See Appendix C, "Oracle Real-Time Collaboration Log Files" for details about the file names and directory structure of all logs.
You can control how often log files are updated, the level of detail stored in the logs, and where the logs are stored, using the following Oracle Real-Time Collaboration properties:
LogFlushInterval controls how often logs are updated. The default is every 10 seconds.
LogLevel controls the amount of detail stored in the logs.
LogPath controls where log files are stored.
See "Configuring System Logs" for details about setting these properties.
If you wish to remove old log files, you can copy the log files to a backup or archive device. As stated previously, all log files are stored in the $ORACLE_HOME/imeeting/logs directory.
Many log files are stored by date, with the date appearing at the end of the file name in MM.DD.YYYY format. You can review these dates and choose to delete files older than a certain date, or create a script to copy files to an archive location by their datestamp or the date in their file names.
You may use third-party monitoring software to monitor the status and availability of Oracle Real-Time Collaboration services. You can use the test servlets or the runTest command to gather status information as described in "Oracle Real-Time Collaboration Monitoring Interfaces". You can then use your monitoring software to produce availability or "uptime" reports showing service availability and history. If you post a home page for the report(s) on a web server, you can use the AvlURL property to display that page from the Availability sub-tab under Reports.
See "Configuring the Availability Report" for details about setting this property
You can e-mail reports to a list of recipients using the imtreport script, as follows:
Locate the imtreport script at $ORACLE_HOME/imeeting/bin/imtreport.
Using a text editor, open the imtreport script and edit it as follows:
FROM_ADDRESS: Enter the e-mail address of the sender of the reports.
RECIPIENTS: Enter the e-mail addresses of the recipients, separating each one with a comma. Do not use spaces between each e-mail address.
REPORT_TYPE: Enter the default report type. The initial default is set to USAGE. This is the report that will be sent if no report type is specified when you run the script. Valid values are QOS, USAGE, FEEDBACK, SECURITY, or ALL. ALL sends four separate e-mail messages to each recipient, one for each of the four reports.
To send the report(s), run the script from $ORACLE_HOME/imeeting/bin/imtreport as follows:
imtreport -type report
where report is either QOS, USAGE, FEEDBACK, SECURITY, or ALL. ALL sends four separate e-mail messages to each recipient, one for each of the four reports. If -type report is not specified, the default report is sent. The initial default is USAGE.
