Jump to: navigation, search

SpeechMiner to Upgrade Procedure

This document explains how to upgrade SpeechMiner from version to version

Pre-upgrade Requirements

  • Request the most recent release of the 8.5 software from your Genesys representative.
  • Request the Migration Console tool from your Genesys representative.
  • Verify that you are working with English US localization settings. You can not upgrade using localization settings that are not English US.
  • When upgrading to a later build for the same version, SMUpgrade is not required. Contact Genesys Customer Care to verify if you need an SQL script for the specific upgrade.

Upgrade Checklist

The following checklist summarizes all the procedures required for upgrading SpeechMiner. Make sure to complete all of the required procedures.

Item to Check Details
Check for Customization If any customizations were implemented on your DB, make sure that they are part of the new version, or that they can be used in the new version without changes. Contact Genesys Customer Care for assistance.
Purging Old Data Most systems have a data retention policy in place. Data (for example, audio, exploration data, and so on) that is older than the specified period of time is automatically deleted. If you do not have a data retention policy in place, it is recommended to determine what data should be saved and what can be discarded, since deleting the data before the upgrade will reduce both the time it takes to run the upgrade process and the storage-space requirements.

Upgrade Procedure

  1. Back up the SpeechMiner database in the SQL server.
  2. Run the Migration Console tool in the background, open the command line and run the following command (where <authType> equals -sql (server authentication) or -win (Windows authentication):
  3. TextMigration <authType> <dbserver> <dbName> [<dbuser> <password>]

    The Migration Console tool will move the text data from your database to the Store folders. All migrated text will belong to the systems site with ID=0.
  4. Verify that the Exit code is 0 (zero). 0 indicates that your files were successfully transferred from the database to the file system.
  5. Important
    If the Migration Console tool was not successful you will receive an error message. Once the source of the error is solved, run the Migration Console tool again until it is successful and you receive 0.
  6. Once the Migration Console tool is run successfully, stop the Uplatform service.
  7. Run the Migration Console tool again using the following command line (where <authType> equals -sql (server authentication) or -win (Windows authentication):

    TextMigration <authType> <dbserver> <dbName> [<dbuser> <password>]
  8. Important
    Do not continue with this procedure until the command that runs the Migration Console tool is successful and you receive 0. If the tool is not successful contact Genesys Customer Care for assistance.
  9. Uninstall SpeechMiner
  10. Copy the entire FullInstaller folder from the build 7169 kit to your local server to your local server.
  11. Install the new SpeechMiner (build 7169).
  12. Reboot your machine.
  13. Run the database update script. To receive the script click Database Script or from the SpeechMiner page under the Helpful Links title.
  14. Deploy SQLCLR: Using SQL management, run the commands that are in the C:\Program Files (x86)\Genesys\Software\Support\sqlclr.sql script in the SpeechMiner database.
  15. Run SMConfig and connect to the database that was upgraded.
  16. Click Save in Sites & Machines.
  17. Deploy the reports (not required for recording–only installations).
  18. In the SpeechMiner Configuration Tool > Services select the following:
    • Under Services select:
      • Create Performance Counters
      • Register services
      • Update config files
      • Encrypt config files
    • Under Select/Deselect All select the relevant machine.
    • Select Restart Services and select change status to run from the drop–down list.
  19. Open the SpeechMiner Web and check its functionality.
This page was last edited on April 11, 2018, at 11:26.
Comments or questions about this documentation? Contact us for support!