Monitoring Message Requests

Note: This functionality is only available for Opera versions 5.0+.

If the Opera Access Point Utility Service is running, the OEDS Request Log Summary screen allows you to monitor each request through Opera ADS, GDS, Opera Web Suite, and User Interface. To access the OEDS Request Log Summary screen, select Setup>Configuration>Channels>Monitoring.

Search Criteria

Complete one or more of the following search criteria, and then select the Search button to perform a query. The results appear in the grid at the bottom of the screen.

Date Options. Make a selection of either the Daily, Range, or Comparison radio buttons if you want to search for a date, a range of dates (up to one week), or to compare two different dates.

Date. Select the first date to be included in the search.

Date2. The second date is used when the Range or Comparison date options are used. You must enter the second date to be included in the query.

Channel. Select the channel from the list of values. This field is mandatory.

Hour. Select the hour the message was sent, or leave this field blank to include all times.

Message Type. Select the message type from the list of values, or leave this field blank to include all message types. The following message types are available: ACTIVITY, AVAILABILITY, BROCHURE, GUEST SERVICES, INFORMATION, MEETING ROOM, MEMBERSHIP, NAME, RESERVATION, RESV ADVANCED, SECURITY, STAYHISTORY, and UNITOWNERS.

Method. Select the method of the message request, or leave this field blank to include all messages.

Search Results Grid

Date. The date of the message request.

Hr. The hour of the message request.

Type. The message type.

OWS Scs. The number of successful messages.

OWS Fail. The number of failed messages.

OWS Time. The total time it took to send the message.

OEDS Request Log

Run the following services:

• OAP LOV SERVICE
• OAP UTILITY SERVICE

Application Parameters

Activate the following application parameter:

• OEDS REQUEST LOG

  If disabled, OEDS will not log messages.

  For detail message logging, set OEDS REQUEST LOG to SUMMARY & REQUESTS.

  For summarized logging, set OEDS REQUEST LOG to SUMMARY Only.

Tables

• oeds_request_log>Stores detailed message information

  

• oeds_request_log_summary>Stores summarized information

  

Process flow

• Message comes from OWS/ADS/GDS interface.
• OAP LOV service builds the request messages and inserts them in the RequestLogyyyyMMddHH.xml file.
• The requestLogDirectory and file size can be specified via the OEDS Configuration wizard. When the maximum file size is reached, a new file will be created.
• OAP Utility service will insert records from the XML file into the respective table at request log interval based on the application setting.
• The Request Log Insert Interval can be specified via the OEDS Configuration Editor.
• In oeds_request_log table, records older than 7 days will be purged by the OAP UTILITY SERVICE.
• Once we insert records from the xml file into the table, the XML file is moved to the following backup directory under the Logs folder: \\Backup_RequestLog\\
• Files in this folder will be purged as part of the OEDS log file purge. The OAP Utility Service purges the log file based on the log file purge offset.
• Once per day, the previous day's messages that took longer than 5 minutes to process will be emailed (Daily request time out). Email parameters can be set via the OEDS Configuration Editor.
• There is also a Manual Request Log Process (shortcut in the desktop) which can be used to email the daily request summary timeout data.

OEDS Configuration Editor

Request Log Directory and Request Log File Size

Request Log Insert Interval

Log Purge Offset

Request Log Email parameters:

See Also OPERA Channel Management for Versions 5.0+