Deployment Procedure

License Reporting Manager 8.1.x

Genesys Telecommunications Laboratories, Inc. © 2012–2014

Contents

Introduction

Release Number Date Release Type
8.1.200.06 04/24/14 Hot Fix
8.1.200.05 10/30/13 Hot Fix
8.1.200.04 08/16/13 General
8.1.100.28 05/24/13 Hot Fix
8.1.100.26 03/26/13 General
8.1.000.22 04/03/12 General

Additional Information

Introduction

This deployment procedure applies to the releases of License Reporting Manager (LRM) 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 LRM using the package you received from Genesys via FTP.


Standard Deployment Procedure for Migrating to 8.1.1 or 8.1.2

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

Notes:

Pre-Installation Steps

Ensure that:

Installation Steps

  1. If migrating from License Reporting Manager release 8.0, you must first perform the Standard Deployment Procedure for Migrating to 8.1.0.

  2. Follow the installation procedure in the License Reporting Manager 8.1 Deployment Guide to install and configure the current release of LRM.

  3. To migrate from release 8.1.0 to either release 8.1.1 or 8.1.2, copy the upgrade810to811.sql file from the <LRM installation directory>/sql/oracle/ directory on the newly installed LRM server to the server where you installed the Oracle SQL Developer tool.

  4. Start Oracle SQL Developer and connect to the Oracle Database using the credentials for the user you configured with the main role to copy data from the old System LRM 8.1.0 database to the new database.

  5. Run the upgrade810to811.sql script to import data from the previous release to the new release. These migration scripts apply the necessary changes for the new release, but keep all previous non-temporary data intact for both the Local and System LRM databases. The data from the previous release remains available in the LRM reports.

  6. (Optional) To use a replicated database with different JDBC connection information on your LRM server, you must upgrade your Oracle or Microsoft SQL databases to the new database schema. This enables LRM to work with a replicated database containing preexisting data.

    Note: If your deployment does not use a replicated database, you do not need to perform this step. See (LRM-491) in the License Reporting Manager 8.1 Release Note.

You have successfully completed your deployment of License Reporting Manager.

Top of Page


Standard Deployment Procedure for Migrating to 8.1.0

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

Notes:

Pre-Installation Steps

  1. Ensure that your target computer meets the platform and component prerequisites that are listed in the Genesys Supported Operating Environment Reference Guide.

  2. Ensure that you have installation rights.

  3. You must have installed and configured Oracle Client and the SQL Plus utility.

  4. You do not need to stop any Interaction Concentrator applications, which provide data to License Reporting Manager, during this deployment.

  5. Ensure that the Local and System License Reporting Manager are not running.

  6. Create backup copies of both your Local and System LRM databases before you begin this deployment.

Installation Steps

  1. Navigate to the License Reporting Manager directory.

  2. Open and run the install.sh file in a terminal window.

  3. When prompted, enter the Host Name or press Enter for "Local Host".

  4. When prompted, enter the Configuration Server Name, Network port number, User name, and Password.

  5. From the displayed list, choose an application that you want to install. When prompted, enter the number of your chosen application.

  6. Enter the location in which you want your application to be installed. Provide the full path.

  7. A list of files that have been installed in your application’s destination location will be displayed, along with a message that informs you of your successful installation.

  8. Make sure you have set the proper ORACLE_HOME and ORACLE_SID environment variables in the Oracle Client and the SQL Plus utility.

  9. Note: The database administrator must have granted the Oracle schema/user execution access to the DBMS_LOCK package. To grant permission, run the following command line:

    grant execute on dbms_lock to <user>

    For example: grant execute on dbms_lock to lrm_sys_db

  10. Run the migration script lrm_migration_db_i.sh <username> <password> where username and password are those that are associated with the Local LRM database. Repeat this step for each Local LRM database in your environment.

  11. Run the migration script lrm_migration_db_a.sh <username> <password> where username and password are those that are associated with the System LRM database.

  12. Note: These migration scripts apply the necessary changes for the new release, but keep all previous non-temporary data for both the Local and System LRM databases intact.

You have successfully completed your deployment of License Reporting Manager 8.1.0.

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 License Reporting Manager 8.1 Deployment Guide first.

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

Top of Page