Deployment Procedure

Genesys Info Mart

7.6.010.07

Genesys Telecommunications Laboratories, Inc. © 2010

Contents

Introduction
Deployment Procedure – General [09/08/10]
Additional Information


Introduction

This deployment procedure applies to the 7.6.010.07 General release of Genesys Info Mart, released 09/08/10. It describes how to deploy Genesys Info Mart using the package you received from Genesys.


Deployment Procedure – General [09/08/10]

To deploy this package, do one of the following depending on your current release:

Notes:

Pre-Installation Steps

  1. Set the run-scheduler configuration option to FALSE in the schedule section of the Genesys Info Mart Application object to temporarily stop Genesys Info Mart Server from launching ETL jobs.

  2. Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor the completion of the jobs.

  3. Stop the Genesys Info Mart Server.

  4. Create backup copies of both your Staging Area and Info Mart databases.

  5. Create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. These scripts perform the following tasks:

  6. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.

    To locate these SQL scripts, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

  7. Make a note of the application startup arguments if you customized them. The installation process will overwrite these arguments and you will lose any changes that you made.

Installation Steps

  1. Install the new Genesys Info Mart installation package:

  2. Update the 7.6 application startup arguments if you previously customized them.

  3. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against each Interaction Database (IDB) with Database Access Point role equal to ICON_CORE if you have not previously done so (ER# 206504724):


  4. If you are installing over release 7.6.001.07, issue the following SQL statements against each Interaction Concentrator database (IDB) with Database Access Point role equal to ICON_CORE (ER# 207130586):


  5. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Staging Area database if you have not previously done so (ER# 206504501):


  6. If you are installing over release 7.6.001.07, issue the following SQL statements against the Staging Area database (ER# 207130586):


  7. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Info Mart database if you have not previously done so (ER# 206620229):


  8. If you are installing over release 7.6.001.07, examine the following SQL commands and issue them against the Info Mart database if you have not previously done so (ER# 206112053):


  9. If you are installing over release 7.6.001.07, examine the following SQL statement and issue it against the Info Mart database if you have not previously done so (ER# 205563115):


  10. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Info Mart database if you have not previously done so (ER# 204783401):


  11. If you are installing over release 7.6.002.07 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 212799606):


  12. If you are installing over release 7.6.002.07 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 216377068):


  13. If you are installing over release 7.6.003.08 or an earlier 7.6 release and plan to take advantage of the new functionality introduced in the Genesys Info Mart 7.6 Maintenance Release 3 (release number 7.6.004.07) to extract UserEvent-based key-value pair data associated with voice interactions, issue the following SQL statements against each Interaction Concentrator database (IDB) with Database Access Point role equal to ICON_CORE (ER# 205973400):


  14. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with Database Access Point role equal to ICON_CORE or ICON_MM (ER# 183662866):


  15. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 218900695):


  16. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 205973400):


  17. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 218560659, 218834630):


  18. If you are installing over release 7.6.004.09 or an earlier 7.6 release and the Staging Area database is on DB2, issue the following SQL statements against the Staging Area database (ER# 223311605):


  19. If you are installing over release 7.6.004.13 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 226459195):


  20. If you are installing over release 7.6.004.13 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE (ER# 227546437):


  21. If you are installing over release 7.6.004.14 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE, ICON_MM, or ICON_OCS (ER# 225783911):

    ICON_CORE


    ICON_MM


    ICON_OCS


  22. If you are installing over release 7.6.004.14 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE (ER# 227766321):


  23. If you are installing over release 7.6.004.14 or an earlier 7.6 release, execute the upgrade_gim_76002_thru_76004_to_76005.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 208829385, 224984829, 207557859, 224160161)

  24. If you are installing over release 7.6.005.12 or an earlier 7.6 release, issue the following SQL statements against each Interaction Database (IDB) with Database Access Point role equal to ICON_CORE or ICON_MM if the database is on Microsoft SQL Server:


  25. If you are installing over release 7.6.005.12 or an earlier 7.6 release, execute the upgrade_merging_to_76006.sql script against the Merge Staging Area schema, if you have one configured. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 227541181, 121883861)

  26. If you are installing over release 7.6.005.12 or an earlier 7.6 release, execute the upgrade_stg_76004_thru_76005_to_76006.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 230639921, 229717291, 232148971)

  27. If you are installing over release 7.6.005.12 or an earlier 7.6 release, execute the upgrade_gim_76005_to_76006.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

  28. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the make_icon_cfg_indexes_for_gim.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CFG. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

  29. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_icon_indexes_for_gim_76005_thru_76006_to_76007.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE or ICON_MM. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

  30. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_iconmm_indexes_for_gim_76005_thru_76006_to_76007.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_MM. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

  31. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_icon_ocs_indexes_for_gim_76005_thru_76006_to_76007.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_OCS. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

  32. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_stg_76006_to_76007.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 237376182, 238593940)

  33. If you are installing over release 7.6.007.13 or an earlier 7.6 release and are using the new functionality introduced in the Genesys Info Mart 7.6 Maintenance Release 3 (release number 7.6.004.07) to extract UserEvent-based key-value pair data associated with voice interactions, execute the upgrade_icon_indexes_for_gim_76007_to_76008.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 246126748)

  34. If you are installing over release 7.6.007.14 or an earlier 7.6 release, execute the upgrade_stg_76007_to_76008.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 235721401, 199733383)

  35. If you are installing over release 7.6.008.15 or an earlier 7.6 release, execute the load_gim_staging_area.sql script against the Staging Area database. If Genesys Info Mart has been configured to use 15-minute level aggregates, then also execute the load_gim_staging_area_15.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 242363776, 249217428)

  36. If you are installing over release 7.6.008.15 or an earlier 7.6 release, execute the upgrade_gim_76006_thru_76008_to_76009.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

  37. If you are installing over release 7.6.008.15 or an earlier 7.6 release, execute the make_gim_agg_views_30.sql script against the Info Mart database if Genesys Info Mart has been configured to use 30-minute level aggregates, or execute the make_gim_agg_views_15.sql script if Genesys Info Mart has been configured to use 15-minute level aggregates. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 233795116, 235625870, 246948595, 249217428)

  38. If you are installing over release 7.6.009.09 or an earlier 7.6 release, execute the upgrade_stg_76008_thru_76009_to_76010.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 252456451)

  39. Restart the Genesys Info Mart Server.

  40. If you are installing over release 7.6.007.14 or an earlier 7.6 release, manually run Job_InitializeGIM using the Genesys Info Mart Administration Console.

  41. Set the run-scheduler configuration option to TRUE in the schedule section of the Genesys Info Mart Application object to resume the Genesys Info Mart Server schedule.

Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software.

If you encounter any issues with the deployment of this package, please contact Genesys Technical Support.

Top of Page