Solutions

How to gain the new "Web Searches" reports in Reporter 9.2 while retaining custom reports and scheduled tasks

Solutions ID:    KB3807
Version:    3.0
Status:    Published
Published date:    05/21/2010
Updated:    05/08/2012
 

Problem Description

To use the new report features added in Reporter 9.2, you must create a new Reporter database and proxy access logs must be processed into this new database.

Any custom or scheduled reports will be unavailable under a new database and would have to be manually recreated.

To preserve your customization and scheduled reports, follow these steps:

Resolution

  1. Back up the entire Blue Coat Reporter 9 installation folder (for example:. C:\Program Files\Blue Coat Reporter 9), including any database storage folders if they are not stored in the default location.
    This allows you to restore Reporter to its original state in the event of any failure.
     
  2. Log into the Reporter Management Console and create a new database (the name does not matter) but do not assign a log source at this time..
     
  3.  Go to Administration > System Overview.

    Under Database Overview, take note of the database location for the database you'll be rebuilding.
    Additionally, note the location of the new database that was just created.

    Example:
    OLD DB   F:/reporterdb/database_aeeb887064f911df9593f3ca467e146a/
    NEW DB  F:/reportedb/database_0ce4878043fb11df8f31f0004da0935d/
     
  4. Stop the Reporter service.
     
  5. Go into the folder containing the old database to rebuild, as gathered in step 4
     
  6. Delete everything under that folder, leaving the folder itself intact and empty.

    NOTE: If you have upgraded to Reporter 9.3.x or newer:
    Create two subfolders in the empty database folder, named video and main.
     
  7. Delete the top level folder containing the new database.
     
  8. Go into the Reporter installation folder (by default: C:\Program Files\Blue Coat Reporter 9\settings\databases).
     
  9. Locate the CFG file that corresponds to the old database. Copy its file name to the clipboard or a notepad and delete the file.
       
  10. Locate the CFG file that corresponds to the new database and rename it with the name of the old CFG file.
     
  11. For this part, you need to know the new and old database IDs. This is the second part of the database folder name:
    For example: database_aeeb887064f911df9593f3ca467e146a
    The ID is aeeb887064f911df9593f3ca467e146a
     
  12. Open up the renamed CFG file in a text editor.
     
  13. Find and replace all occurrences of the new database ID with the old one.
     
  14. Start the Reporter service. There will be no data in the database, but any custom reports, scheduled tasks, etc, are preserved.
     
  15. Assign a log source to the database so it starts processing access log files again.
    You are now able to use the new Reports that were added in Reporter 9.2.1.1.

NOTE: LINUX users can find their complete Reporter installation at: /opt/bc/reporter.

 


Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question