Revision as of 07:29, August 7, 2018 by Peter Chaplin (talk | contribs) (→‎Procedure)
Jump to: navigation, search

Migration from 8.5.1x to 9.0.x

General Migration Procedure from 8.5.1x to 9.0.x

Prerequisites

  • iWD 9.0 requires Java 1.8. Support for Java 1.6 and 1.7 is withdrawn in release 9.0.
  1. Backup all databases.
  2. Upgrade iWD dependencies to supported versions (see Preparing for Installation).
  3. Stop all iWD 8.5 components.
    1. iWD Manager's Tomcat.
    2. iWD Runtime Node.
    3. iWD Web.
  4. Install all components.
    1. Upgrade GAX plug-in to a new version (at least 9.0.002.07) by uninstalling the previous GAX plug-in and installing the new one (details here).
    2. Install History Node.
      1. Install History Node using this procedure. Set up JMS and JDBC Database Access Points (DAPs).
      2. Perform iWD History Node migration from the Event Log.
      3. Create a connection from Interaction Server to the JMS DAP.
    3. Data Mart
      1. Migration of data from iWD Data Mart 8.5 to iWD Data Mart 9.0 is not supported due to schema changes—see History Node Limitations.
      2. History Node should be installed already.
      3. Migration
        1. Create a new database for Data Mart.
        2. Complete a fresh installation of Data Mart as a separate application.
        3. Copy all necessary settings from the iWD Runtime Node 8.5 application.
        4. Copy all customized ETL scripts to the iWD Runtime Node 9.0 ETL directory (../iWD Runtime Node 9.0/etl). Note: If your Kettle plugins fail to work on an Oracle database, please set the following database parameters:
          • JDBC URL: jdbc:evo:oracle:@//<databasename>:1521/<SID>
          • JDBC Driver Class: evo.database.oracle.EvoDriver
          For more information about setting database parameters please refer to iWD GAX Plug-in Datamart help.
        5. Add the History Node application to the connections.
        6. Create a Configuration Server database JDBC DAP with configuration option [iWD]/role = cfgserver and add it to the Runtime Node connections (details here).
        7. Add a jdbc section with options url and driver-class to all created DAPs listed in the connections (details here).
        8. Change or set the Data Mart application to a new one for all necessary solutions using GAX / iWD / Datamart / <Solution>.
        9. Using GAX, change the ETL Scripts Directory to a new one for each solution.
        10. Check that your Data Mart Business Structure Solution has a timezone set.
        11. Check that in the Data Mart application the schedules/historical and schedules/intraday are set as valid Quartz cron expressions.
        12. [Optional] Disable the EventLog as it was replaced by History Node and JMS event logger.
    4. Stat Server Extensions
      1. Install the new 9.0 version. No other changes are required.
    5. iWD Manager
      1. iWD GAX Plugin must be updated already.
      2. Make sure iWD Manager 8.5 is stopped. Disable its autostart.
      3. Import new the iWD Manager 9.0 application templates (App and Server) as described in Installing iWD Manager and make applications from them.
      4. Install the iWD Manager 9.0 application itself to a separate folder.
      5. Create a connection from the iWD Manager server application to the History Node application by using GAX.
      6. Copy the required settings from the old iWD Manager application to the new iWD Manager server application by adding a connection from iWD Manager Server to Interaction Server.
      7. Copy the required settings from the old iWD Manager application to the new iWD Manager Application by adding the necessary permissions for the iWD access group (to make users able to login, to read filter list, and so on).
      8. Migrate options from the old iwd.properties file to iWD Manager Server Application Options. The detailed description of the properties can be found here.
        • Note: Parameter iwd.cfgConnectionTimeout is replaced by four independent parameters for each connection:
          • cfgConnectionTimeout for the Configuration Server connection.
          • ixnConnectionTimeout for the Interaction Server connection.
          • ucsConnectionTimeout for the Universal Contact Server connection.
          • msgConnectionTimeout for the Message Server connection.
      9. Migrate logging settings.
        1. If you use Centralized Logging, make sure that you've created a connection from iWD Manager Server to Message Server.
        2. Configure logging in accordance with the details in Logging.
      10. Make sure that host and port of the primary Configuration Server, and the application name of the iWD Manager Server, are presented in the General -> Command Line Arguments of the iWD Manager 9.0 Server.
      11. Run the separate iWD Manager Configuration Database to Configuration Server migration procedure.
      12. Open GAX and make sure that the Scripts -> iWD Manager folder is created and permissions to that folder are granted for the EVERYONE group.
    6. iWD Web
      1. Install a new iWD Web application as described in this series of topics.
  5. Start all iWD 9.0 components


iWD Manager Configuration Database to Configuration Server Migration Information

iWD Configuration Database migration is performed manually by a Python script similar to that used in 8.5.0 to 8.5.1 migration. To run the script, you need to provide the iWD Manager Configuration Database connection parameters (URL, login and password), and the GAX URL, username and password. The Python script takes the data from the IWD Configuration Database and sends it into the Configuration Server via the GAX API.

Procedure

  1. Install Python 2.7.
  2. Add environment variables:
    • Path=C:\Python27;C:\Python27\Scripts
  3. For Linux users some additional libraries may be required. To resolve this please deploy the following RPMs with the version appropriate for your OS version:
    • unixODBC-*.rpm (for example, for 64-bit RHEL6: unixODBC-2.2.14-14.el6.x86_64.rpm)
    • freetds-*.rpm (for example, for 64-bit RHEL6: freetds-0.91-2.el6.x86_64.rpm)
  4. Download the required Instant Client packages for your platform. All installations require either the Basic or Basic Light package.
  5. Unzip the packages into a single directory such as '"instantclient_12_2'".
  6. Set your environment's library loading path (for example LD_LIBRARY_PATH on Linux, or PATH on Windows) to the directory created in Step 2.
  7. Start your application.
  8. Refer to any detailed instructions on the download page of your platform for more information. Note: Python and Oracle client versions must both be either 32- or 64-bit.
  9. If there are any data with Unicode charaters to be migrated, ensure that the GAX application is configured to support UTF-8 encoding. You can do the following:
    • For Windows, add -Dfile.encoding=utf-8 to JavaServerStarter.ini under the [JavaArgs] section.
    • For Linux, add export JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=utf-8 to setenv.sh.
  10. Restart GAX.
  11. Unzip the migration.zip file. This should be located under the config/ folder in iWD Manager's installation directory.
  12. Install dependencies.
  13. From the folder where migration.zip was unpacked, run the following command:
    pip install -–upgrade -r requirements.txt
  14. Run the migration script for each tenant, include the Environment tenant:
    python main.py -g <gaxurl> -u <gax username> -p <gax password> -t <tenant> -y <db type> -d <db host> -r <db port> -n <db name> -s <db user> -w <db user password> --verbose
    The script parameters are as follows:
    • -g, --gaxurl—GAX URL address
    • -u, --username—GAX user name
    • -p, --password—GAX user password
    • -t, --tenant—Tenant Name
    • -y, --dbtype—iWD Configuration Database type (either Oracle or MSSQL)
    • -d, --dbhost—iWD Configuration Database host
    • -r, --dbport—iWD Configuration Database port
    • -n, --dbname—iWD Configuration Database name
    • -s, --dbuser—iWD Configuration Database user
    • -w, --dbpass—iWD Configuration Database password
    • --verbose—verbosity level
    Oracle example:
    python main.py -g http://192.168.123.132:8080/gax -u default -p password -t selenium -y oracle -d 192.168.123.123 -r 1521 -n xe -s iwd_user -w iwd_password --verbose
    MSSQL example:
    python main.py -g http://192.168.123.123:8080/gax -u default -p password -t selenium -y mssql -d 192.168.123.123 -r 1433 -n iwd_config -s iwd_user -w iwd_password --verbose

Post-installation—Configuring the Solution

Once you have installed iWD 9.0, for each configured Solution you must:

  1. Navigate to iWD GAX plugin -> Business Structure -> <Solution name>.
  2. Complete the Interaction Server JDBC URL and save the changes.

History Node Specific Migration Information

TLS Configuration

To configure TLS, please refer to Configuring TLS for iWD.

Specific migration procedures for iWD 9.0.005

The changes of Application type for iWD Manager Server, iWD History Node and iWD Web from Third Party Server to Genesys Generic Server result in the following migration requirements that are additional to the general migration procedure detailed above. If you are migrating from an 8.5.1x release to a 9.0.x release of iWD, please follow the general migration procedure first, then follow the 9.0.005-specific migration procedures in this section.

There are three 9.0.005-specific procedures to follow:

  1. Migrate iWD Manager.
  2. Migrate iWD History Node.
  3. Migrate iWD Web.

You must use this sequence. Do not restart the applications until all three procedures have been completed.

Migrate iWD Manager

Prerequisites

  • iWD Manager Installation Package with version 9.0.005.04+

Procedure

  1. Make sure iWD Manager is stopped.
  2. Export Options and Application Options from the iWD Manager Server application object into .xml files.
  3. Delete the previous installation of iWD Manager.
  4. Import the new application template.
  5. Create a new Application object for iWD Manager Server with type Genesys Generic Server..
    1. On the Connections tab of the Application object, add the connections to the Configuration Server and UCS.
    2. To enable the Centralized Logging feature, add a connection to Message Server on the Connections tab.
    3. Import the Options and Application Options from the .xml files you previously created.
  6. Install the new version of iWD Manager using the previously created Application objects.

Migrate iWD History Node

Prerequisites

  • iWD History Node Installation Package with version 9.0.005.04+
  • iWD Data Mart Installation Package with version 9.0.005.04+
  • iWD GAX Plug-in upgraded to version 9.0.005.04+

Procedure

Important
Make sure that you have upgraded the IWD GAX Plug-in to at least the 9.0.005.04 version.
  1. Make sure iWD History Node and iWD Data Mart are stopped.
  2. Export the Options and Application Options from the iWD History Node application object into .xml files.
  3. Delete the previous installation of iWD History Node.
  4. Import the new iWD History Node application template with type Genesys Generic Server.
  5. Create a new Application object for the iWD History Node using the previously uploaded template.
    1. On the Connections tab, add the connections to the Configuration Server, History Node DAP and Event Logger JMS DAP.
    2. Make sure that you have two ports (admin and default) configured on the Ports tab.
    3. Import the Options and Application Options from the .xml files you previously created.
    4. On the Tenants tab, add tenant you want to work with.
  6. Install the new version of iWD History Node using the previously created Application objects.
  7. Upgrade the iWD Data Mart which was using your iWD History Node to the new version.
  8. In the iWD GAX Plug-in, navigate to Business Structure, open the Solution you used to start History Node and choose the new Application object.

Migrate iWD Web

Prerequisites

  • iWD Web Installation Package with version 9.0.005.04+

Procedure

  1. Make sure iWD Web is stopped.
  2. Export the Options and Application Options from the iWD Web application object into .xml files.
  3. Delete the previous installation of iWD Web.
  4. Import new iWD Web Application template with type Genesys Generic Server.
  5. Create a new Application object for iWD Web using the template uploaded previously.
    1. On the Connections tab, add the connections to the Message Server, Interaction Server and Capture Points.
    2. Import the Options and Application Options from .xml files created previously.
  6. Install the new version of iWD Web using the previously created Application object.

Restart applications

When all components are successfully migrated, restart the applications.

Comments or questions about this documentation? Contact us for support!