Deployment Procedure

Genesys Info Mart 8.1.x

Genesys Telecommunications Laboratories, Inc. © 2011–2017

Contents

Introduction

Release Number Date Release Type
8.1.402.11 06/22/17 Hot Fix
8.1.402.10 08/31/15 Hot Fix
8.1.402.09 06/19/15 Hot Fix
8.1.402.08 03/13/15 Hot Fix
8.1.402.07 11/24/14 General
8.1.401.05 10/24/14 Hot Fix
8.1.401.02 09/22/14 General
8.1.400.12 07/30/14 General
8.1.301.07 07/02/14 Hot Fix
8.1.301.06 04/23/14 Hot Fix
8.1.301.05 03/20/14 Hot Fix
8.1.301.04 03/06/14 General
8.1.300.14 12/23/13 General
8.1.202.04 11/08/13 Hot Fix
8.1.202.03 09/30/13 Hot Fix
8.1.202.01 08/23/13 General
8.1.201.06 07/12/13 Hot Fix
8.1.201.05 06/21/13 Hot Fix
8.1.201.02 04/25/13 General
8.1.200.21 03/18/13 General
8.1.103.07 02/04/13 Hot Fix
8.1.103.05 12/14/12 Hot Fix
8.1.103.03 10/30/12 General
8.1.102.02 09/05/12 General
8.1.101.07 08/20/12 Hot Fix
8.1.101.05 07/23/12 Hot Fix
8.1.101.04 07/11/12 General
8.1.002.08 04/12/13 Hot Fix
8.1.002.07 07/06/12 Hot Fix
8.1.002.05 04/30/12 Hot Fix
8.1.002.03 04/02/12 Hot Fix
8.1.002.02 02/10/12 General
8.1.001.07 01/17/12 Hot Fix
8.1.001.05 12/20/11 General
8.1.000.28 11/18/11 Hot Fix
8.1.000.25 10/07/11 General

Additional Information


Introduction

This deployment procedure applies to the releases of Genesys Info Mart listed in the Release table, above. Click the link in the Release table for the version you are deploying to jump to a description of how to deploy Genesys Info Mart using the package you received from Genesys. Most releases use the same standard deployment procedure.

If your release requires a specialized procedure, the link in the Release table takes you to a header specifying the version number and date of the release. Click the header, and the procedure will open.


Standard Deployment Procedure for Migrating to 8.1.4

To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.

To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.

Notes:

Pre-Installation Steps

  1. For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.

    The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.

  2. For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.

    The default location for these scripts is the sql_scripts directory within the Genesys Info Mart installation directory.

  3. For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application object. You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.

  4. 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.

  5. 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.

    If your system includes a second instance of Genesys Info Mart Server in the active-active configuration, ensure that the ETL cycle has been suspended on both servers, to prevent possible concurrency problems if the IDB(s) need to be updated as part of the migration and the second Genesys Info Mart Server attempts to extract from an IDB while the update_IDB script is running.

    Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in IDBs, Genesys Info Mart will process that data after you complete the migration.

  6. If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:

    1. Set the run-aggregates option to FALSE in the [schedule] section of the Genesys Info Mart Application object.
    2. Stop the aggregation job from the Genesys Info Mart Manager.
  7. Wait for any currently running jobs to finish. Use the Genesys Info Mart Manager to monitor completion of the jobs. To do so, open Genesys Info Mart Manager and periodically click Refresh to check the updated status of the jobs.

    Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.

  8. Stop the Genesys Info Mart Server.

  9. Create a backup copy of your Info Mart database.

  10. If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.

Installation Steps

  1. Install the new Genesys Info Mart installation package:

  2. In the Release Note, review the "New in This Release" section for the release to which you are upgrading. Identify if any configuration option changes affect customizations that you may have made in your Genesys Info Mart deployment. If necessary, modify configuration settings in the Genesys Info Mart Application or other configuration objects, as required, to transfer custom settings for your deployment.

    Because release 8.1.x no longer uses relative values to determine when calendar dimensions start (for example, date-time-start-year = -1 is no longer valid), verify the validity of the date-time-start-year setting for existing calendars. If you used a relative value for the date-time-start-year option in the [date-time] and any custom [date-time-*] sections, change the setting to the appropriate absolute value. Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.

  3. (For Oracle users only) If you are migrating from a release earlier than 8.1.103.05, grant permissions to the Info Mart database user by issuing the following commands against the Info Mart database:

    GRANT
      CREATE SESSION,
      CREATE PROCEDURE,
      CREATE SEQUENCE,
      CREATE TABLE,
      CREATE VIEW to <Info Mart user>;
    GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;

  4. Restore any customizations in startup arguments, start the Genesys Info Mart Server, and check for error messages:

    Note: Genesys recommends that you set an alarm condition for log event 55-20152.

  5. If you need to run Job_MigrateGIM, Genesys Info Mart Server will automatically be in the correct state to perform the migration.

    Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes. If your system includes a second instance of Genesys Info Mart Server in the active-active configuration, ensure that the ETL cycle has been suspended on both servers.

    Launch Job_MigrateGIM from the Genesys Info Mart Manager. To do so, perform the following steps:

    1. Open the Genesys Info Mart Manager.
    2. Click Run Job to open the Run Job dialog box.
    3. Select Job_MigrateGIM.
    4. Click OK.

    Allow this job to complete before continuing.

    Notes:

  6. If you stopped ICON as part of the migration preliminaries related to preventing deadlocks or concurrency problems on IDB, start ICON.

  7. If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.

  8. If your deployment uses Genesys-provided aggregation, in addition to re-creating the Info Mart tenant views (see Step 7), you must also update the tenant aliases. For more information, see the description of the updateAliases runtime parameter in the Reporting and Analytics Aggregates Deployment Guide and the section about updating tenant aliases in the Reporting and Analytics Aggregates User’s Guide.

  9. Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.

  10. If the Genesys Info Mart database is partitioned, launch Job_MaintainGIM from the Genesys Info Mart Manager. To do so, perform the following steps:

    1. Open the Genesys Info Mart Manager.
    2. Click Run Job to open the Run Job dialog box.
    3. Select Job_MaintainGIM.
    4. Click OK.

  11. 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.

  12. If you are using Genesys-provided aggregation, set the run-aggregates configuration option to TRUE in the [schedule] section of the Genesys Info Mart Application object, to resume running the aggregation job in automated mode.

Top of Page


Standard Deployment Procedure for Migrating to 8.1.3 or 8.1.2

To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.

To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.

Notes:

Pre-Installation Steps

  1. For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.

    The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.

  2. For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.

    The default location for these scripts is the sql_scripts directory within the Genesys Info Mart installation directory.

  3. For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application object. You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.

  4. 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.

  5. 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.

    Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in IDBs, Genesys Info Mart will process that data after you complete the migration.

  6. If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:

    1. Set the run-aggregates option to FALSE in the [schedule] section of the Genesys Info Mart Application object.
    2. Stop the aggregation job from the Genesys Info Mart Administration Console.
  7. Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor completion of the jobs.

    Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.

  8. Stop the Genesys Info Mart Server.

  9. Create a backup copy of your Info Mart database.

  10. If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.

Installation Steps

  1. Install the new Genesys Info Mart installation package:

  2. In the Release Note, review the "New in This Release" section for the release to which you are upgrading. Identify if any configuration option changes affect customizations that you may have made in your Genesys Info Mart deployment. If necessary, modify configuration settings in the Genesys Info Mart Application or other configuration objects, as required, to transfer custom settings for your deployment.

    Because release 8.1.x no longer uses relative values to determine when calendar dimensions start (for example, date-time-start-year = -1 is no longer valid), verify the validity of the date-time-start-year setting for existing calendars. If you used a relative value for the date-time-start-year option in the [date-time] and any custom [date-time-*] sections, change the setting to the appropriate absolute value. Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.

  3. (For Oracle users only) If you are migrating from a release earlier than 8.1.103.05, grant permissions to the Info Mart database user by issuing the following commands against the Info Mart database:

    GRANT
      CREATE SESSION,
      CREATE PROCEDURE,
      CREATE SEQUENCE,
      CREATE TABLE,
      CREATE VIEW to <Info Mart user>;
    GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;

  4. Restore any customizations in startup arguments, start the Genesys Info Mart Server, and review the Genesys Info Mart log.

    Note: Genesys recommends that you set an alarm condition for log event 55-20152.

  5. If you need to run Job_MigrateGIM, Genesys Info Mart Server will automatically be in the correct state to perform the migration.

    Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes.

    Launch Job_MigrateGIM from the Genesys Info Mart Administration Console v8.0.100.04 or higher. To do so, perform the following steps:

    1. Open the Administration Console window.
    2. Select the Schedule tab.
    3. Click Run Job….
    4. From the menu that opens, select Job_MigrateGIM.

    Allow this job to complete before continuing.

    Notes:

  6. If you stopped ICON as part of the migration preliminaries related to preventing deadlocks or concurrency problems on IDB, start ICON.

  7. If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.

  8. If your deployment uses Genesys-provided aggregation, in addition to re-creating the Info Mart tenant views (see Step 7), you must also update the tenant aliases. For more information, see the description of the updateAliases runtime parameter in the Reporting and Analytics Aggregates Deployment Guide and the section about updating tenant aliases in the Reporting and Analytics Aggregates User’s Guide.

  9. Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.

  10. If you are migrating to release 8.1.200.21 in an Oracle deployment with a partitioned Info Mart database, execute the following SQL statements to prevent a possible post-migration problem because of unavailable partitions:

    begin execute immediate 'alter table CTL_AUDIT_LOG add PARTITION GIM__MAXVALUE VALUES LESS THAN(MAXVALUE)'; exception when others then if sqlcode in (-14074) then null; else raise; end if; end;
    begin execute immediate 'alter table CTL_ETL_HISTORY add PARTITION GIM__MAXVALUE VALUES LESS THAN(MAXVALUE)'; exception when others then if sqlcode in (-14074) then null; else raise; end if; end;

  11. If the Genesys Info Mart database is partitioned, run Job_MaintainGIM from the Genesys Administration Console.
  12. 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.

  13. If you are using Genesys-provided aggregation, set the run-aggregates configuration option to TRUE in the [schedule] section of the Genesys Info Mart Application object, to resume running the aggregation job in automated mode.

Top of Page


Standard Deployment Procedure for Migrating to 8.1.1

To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.

To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.

Notes:

Pre-Installation Steps

  1. For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.

  2. The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.

  3. For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.

  4. The default location for these scripts is the sql_scripts directory within the Genesys Info Mart installation directory.

  5. For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application object. You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.

  6. 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.

  7. 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.

    Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in Interaction Databases (IDBs), Genesys Info Mart will process that data after you complete the migration.

  8. Verify that Genesys Info Mart has transformed all extracted data. If necessary, rerun the transformation job manually. For information about running a job on an unscheduled basis, see the chapter about working with jobs in the Genesys Info Mart Operations Guide.

  9. If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:

    1. Set the run-aggregates option to FALSE in the [schedule] section of the Genesys Info Mart Application object.
    2. Stop the aggregation job from the Genesys Info Mart Administration Console.

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

  11. Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.

  12. Stop the Genesys Info Mart Server.

  13. Create a backup copy of your Info Mart database.

  14. If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.

Installation Steps

  1. Install the new Genesys Info Mart installation package:

  2. Review the "New in This Release" information in the Genesys Info Mart 8.1 Deployment Guide. Identify if any configuration option changes affect customizations that you may have made in your Genesys Info Mart deployment. If necessary, modify configuration settings in the Genesys Info Mart Application or other configuration objects, as required, to transfer custom settings for your deployment.

    Because release 8.1.x no longer uses relative values to determine when calendar dimensions start (for example, date-time-start-year = -1 is no longer valid), verify the validity of the date-time-start-year setting for existing calendars. If you used a relative value for the date-time-start-year option in the [date-time] and any custom [date-time-*] sections, change the setting to the appropriate absolute value. Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.

  3. For each IDB from which Genesys Info Mart will extract ICON details, run the appropriate Genesys Info Mart–provided SQL scripts—located in the <GIM root>/sql_scripts/<dbms> folder—to add to each IDB the views and indexes that Genesys Info Mart requires.

    Note: If the scripts do not complete correctly, analyze the problem by referring to the log file, resolve any issues, and then run the update script again. If problems persist, or if for any reason you decide to terminate the migration process, run the update script from your pre-migration release of Genesys Info Mart.

  4. (For Oracle users only) If you are migrating from a release earlier than 8.1.103.05, grant permissions to the Info Mart database user using the following commands:

    GRANT
      CREATE SESSION,
      CREATE PROCEDURE,
      CREATE SEQUENCE,
      CREATE TABLE,
      CREATE VIEW to <Info Mart user>;
    GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;

  5. (For Oracle users only) If you are migrating to release 8.1.101.07 or earlier 8.1.1 release, manually configure the jdbc-url option in the [gim-etl] section on the Options tab of all DAPs that Genesys Info Mart uses, to ensure that Genesys Info Mart will use the correct JDBC connection parameters. For more information about configuring the jdbc-url option, see the chapter about configuring DAPs in the Genesys Info Mart 8.1 Deployment Guide.

    Note: The Genesys Info Mart 8.1 Deployment Guide describes the jdbc-url option as applicable to non-JDBC DAPs only, but the option is supported on JDBC DAPs as well. (ER# 307205061)

  6. Restore any customizations in startup arguments, start the Genesys Info Mart Server, and review the Genesys Info Mart log.

    Note: Genesys recommends that you set an alarm condition for log event 55-20152.

  7. If you need to update the Info Mart database schema, Genesys Info Mart Server will automatically be in the correct state to perform the migration.

    Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes.

    Update the Info Mart database by launching Job_MigrateGIM from the Genesys Info Mart Administration Console v8.0.100.04 or higher. To do so, perform the following steps:

    1. Open the Administration Console window.
    2. Select the Schedule tab.
    3. Click Run Job….
    4. From the menu that opens, select Job_MigrateGIM.

    Allow this job to complete before continuing.

    Notes:

  8. If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.

  9. If your deployment uses Genesys-provided aggregation, in addition to re-creating the Info Mart tenant views (see Step 8), you must also update the tenant aliases. For more information, see the description of the updateAliases runtime parameter in the Reporting and Analytics Aggregates Deployment Guide and the section about updating tenant aliases in the Reporting and Analytics Aggregates User’s Guide.

  10. Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.

    For example, if you are migrating to release 8.1.x directly from release 8.0.0, you might need to check the values of the IS_ONLINE column in the MEDIA_TYPE table to see whether all media types are correctly identified as online (real-time communication, such as chat) or offline (responses may be deferred, such as e-mail).

  11. Be aware that Genesys Info Mart migration does not go back to manipulate existing data (in other words, data that was processed before migration). In particular:

  12. If the Genesys Info Mart database is partitioned, run Job_MaintainGIM from the Genesys Administration Console.
  13. 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.

  14. If you are using Genesys-provided aggregation, set the run-aggregates configuration option to TRUE in the [schedule] section of the Genesys Info Mart Application object, to resume running the aggregation job in automated mode.

Top of Page


Standard Deployment Procedure for Migrating to 8.1.0

To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.

To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.

Notes:

Pre-Installation Steps

  1. For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.

  2. The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.

  3. For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.

  4. The default location for these scripts is the sql_scripts directory within the Genesys Info Mart installation directory.

  5. For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application object. You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.

  6. 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.

  7. 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.

    Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in Interaction Databases (IDBs), Genesys Info Mart will process that data after you complete the migration.

  8. Verify that Genesys Info Mart has transformed all extracted data. If necessary, rerun the transformation job manually. For information about running a job on an unscheduled basis, see the chapter about working with jobs in the Genesys Info Mart Operations Guide.

  9. If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:

    1. Set the run-aggregates option to FALSE in the [schedule] section of the Genesys Info Mart Application object.
    2. Stop the aggregation job from the Genesys Info Mart Administration Console.

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

  11. Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.

  12. Stop the Genesys Info Mart Server.

  13. If you also plan to upgrade Reporting and Analytics Aggregates (RAA), temporarily disable aggregation so that Genesys Info Mart and RAA do not attempt to migrate their database schemas at the same time. To disable aggregation, set the aggregation-engine-class-name option to none in the gim-etl section of the Genesys Info Mart Application object.

  14. Create a backup copy of your Info Mart database.

  15. If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.

Installation Steps

  1. Install the new Genesys Info Mart installation package:

  2. Review the "New in This Release" information in the Genesys Info Mart 8.1 Deployment Guide. Identify if any configuration option changes affect customizations that you may have made in your Genesys Info Mart deployment. If necessary, modify configuration settings in the Genesys Info Mart Application or other configuration objects, as required, to transfer custom settings for your deployment.

    Because release 8.1.x no longer uses relative values to determine when calendar dimensions start (for example, date-time-start-year = -1 is no longer valid), verify the validity of the date-time-start-year setting for existing calendars. If you used a relative value for the date-time-start-year option in the [date-time] and any custom [date-time-*] sections, change the setting to the appropriate absolute value. Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.

  3. For each IDB from which Genesys Info Mart will extract ICON details, run the appropriate Genesys Info Mart–provided SQL scripts—located in the <GIM root>/sql_scripts/<dbms> folder—to add to each IDB the views and indexes that Genesys Info Mart requires.

    Note: If the scripts do not complete correctly, analyze the problem by referring to the log file, resolve any issues, and then run the update script again. If problems persist, or if for any reason you decide to terminate the migration process, run the update script from your pre-migration release of Genesys Info Mart.

  4. (For Oracle users only) Grant permissions to the Info Mart database user using the following commands:

    GRANT
      CREATE SESSION,
      CREATE PROCEDURE,
      CREATE SEQUENCE,
      CREATE TABLE,
      CREATE VIEW to <Info Mart user>;
    GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;

  5. Restore any customizations in startup arguments, start the Genesys Info Mart Server, and review the Genesys Info Mart log.

    Note: Genesys recommends that you set an alarm condition for log event 55-20152.

  6. If you need to update the Info Mart database schema, Genesys Info Mart Server will automatically be in the correct state to perform the migration.

    Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes.

    Update the Info Mart database by launching Job_MigrateGIM from the Genesys Info Mart Administration Console v8.0.100.04 or higher. To do so, perform the following steps:

    1. Open the Administration Console window.
    2. Select the Schedule tab.
    3. Click Run Job….
    4. From the menu that opens, select Job_MigrateGIM.

    Allow this job to complete before continuing.

    Notes:

  7. If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.

  8. If you disabled Genesys-provided aggregation because you also want to upgrade RAA (see Pre-Installation Step 10), re-enable aggregation. To do so:

    1. Stop Genesys Info Mart Server.
    2. Reset the aggregation-engine-class-name option to "GIMAgg.GimInterfaceImpl.AggregationImpl" in the gim-etl section of the Genesys Info Mart Application object.
    3. Restart the Genesys Info Mart Server.

  9. If your deployment uses Genesys-provided aggregation and there were Info Mart schema changes, in addition to re-creating the Info Mart tenant views (see Step 7), you must also:

  10. Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.

    For example, if you are migrating to release 8.1.x directly from release 8.0.0, you might need to check the values of the IS_ONLINE column in the MEDIA_TYPE table to see whether all media types are correctly identified as online (real-time communication, such as chat) or offline (responses may be deferred, such as e-mail).

  11. Be aware that Genesys Info Mart migration does not go back to manipulate existing data (in other words, data that was processed before migration). In particular:

  12. If the Genesys Info Mart database is partitioned, run Job_MaintainGIM from the Genesys Administration Console.
  13. 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.

  14. If you are using Genesys-provided aggregation, set the run-aggregates configuration option to TRUE in the [schedule] section of the Genesys Info Mart Application object, to resume running the aggregation job in automated mode.

Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

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

Top of Page