Migrate to 8.5.010

This page provides the standard Deployment Procedure for migrating to Pulse 8.5.010.xx.

Important

Pulse requires a staged migration. Review the available migration paths for your release.

Migrate to 8.5.010.xx from 8.5.x or 8.1.4

To deploy this package, do the following:

• To deploy this installation package within a new environment, follow the instructions in the Genesys Pulse Deployment Guide.
• To install the 8.5.010.xx release of Pulse over the prior 8.5.x or 8.1.4 release, use this Deployment Procedure and refer to the Genesys Pulse Deployment Guide as needed.

Notes:

• Review all steps before performing any of them.
• Plan a time when you can complete the installation in one continuous session.
• This procedure is valid only for Genesys Administrator Extension (GAX) and Pulse installed with jetty.
• Rollback to a previous release causes Pulse to lose all widgets previously created by users, because all widgets are automatically converted to release 8.5 during migration.
• After migration from Pulse 8.1.4 to 8.5.010, all widgets from the Custom dashboard are placed into a tab named Custom. To see the Default dashboard you must create a new dashboard and select the Reset to Default Dashboard from the menu.
• If you have widgets for CampaignGroups created in Pulse 8.1.4, Pulse 8.5.010 displays the message No Objects. Please check widget configuration. To make these widgets work, edit them to reselect required objects.
• The KPI Widget may change the Headline object as the result of migration from 8.1.4 to 8.5.010. If this is the case, edit the affected widget by setting up the appropriate Headline object.
• After migration from Pulse 8.5.000 to Pulse 8.5.010, historical data collected during the previous day is lost, which prevents Pulse from loading the line charts until new data is available. After Collector starts, Pulse can display historical data after the first new snapshot is created. This impacts line charts.

Installation Steps

1. Stop both Pulse Collector and GAX.
2. Uninstall Pulse and Pulse Collector.
3. Upgrade GAX. See the GAX upgrade procedure.
   Important

   The GAX upgrade procedure contains options that you must use to enable Pulse migration:

   • Retain the existing GAX Application object for use with Pulse 8.5.
   • Do not retain Pulse files from a previous version.
4. Remove Pulse files (pulse.jar, pulse-proto.jar, protobuf-java-2.5.0.jar) from <GAX installation folder>/plug-ins directory.
5. If the previous release of Pulse was 8.1.400.xx, then you must change options of Data Access Point object used to connect to Pulse database. In the DAP options, change value of role options in the [GAX] section from ezpulse to pulse.
6. Start GAX.
7. In GAX, upload the Pulse Installation Package and Template:
   1. Navigate to Administration > Installation Packages and click the plus sign.
   2. Select Installation Package Upload (template uploaded separately) and click Next.
      1. For Upload a Package, select the zipped file that contains the Pulse Installation Package, which contains the ip_description.xml file as well as setup.exe on the root level.
      2. For Upload an XML template, select the XML Template file Pulse.xml from the Templates Installation Package directory.
      3. For Upload an APD template, select the APD Template file Pulse.apd from the Templates Installation Package directory.
   3. Click Finish.
8. Deploy the Pulse Installation Package and Template:
   1. Click the Pulse Installation Package to open the Properties tab.
      Important

      The Pulse Installation Package status should be complete.
   2. Click the related icon and choose Install to open the IP Deployment Wizard.
   3. Enter details in the required fields and finish the installation.
   Important
   The IPCommon InstallPath should be an empty folder for the Pulse installation (for example C:\genesys\GCTI\Pulse8.5.010).

9. For a High Availability (HA) deployment repeat steps 1 through 6, and 8 for a second GAX. In step 8, you must select a second GAX server.
10. Migration from Pulse 8.1.4 only:
    1. Optionally, update options inside the pulse_statistics.cfg file from the scripts folder to a particular social media that is configured in eServices solution (for example, facebook, twitter, facebooksession, facebookprivatemessage). See eServices documentation for more details.
    2. Import the pulse_statistics.cfg file from the scripts folder to the Stat Server Application Options to create new stattypes within both the primary and backup Stat Server Application objects.
       Tip

       In the first step of this file import uncheck Override.
       Important

       To calculate the % Ready Time in the Queue KPIs template, set the queue-use-pseudo-actions option in the [statserver] section of Stat Server Application object to false.
    3. After the pulse_statistics.cfg file is imported, restart the Stat Server application.
    4. (Optional) To prevent Pulse from updating the Genesys-provided templates to release 8.5 when Pulse starts, create the new option install_templates with its value set to false in the [pulse] section of the GAX Application object. If you also want the ability to remove any template using Pulse, create the option editable_templates with its value set to true. See the Configuration Options in the Genesys Pulse Deployment Guide for details.
11. Back up the Pulse Collector configuration options to a file:
    1. In GAX, navigate to Configuration > Environment > Applications.
    2. Select the Pulse Collector Application object.
    3. Open the Application Options tab.
    4. Click More.
    5. Choose Export to save the file.
12. In GAX, upload the Pulse Collector Installation Package and Template:
    1. In GAX, navigate to Administration > Installation Packages and Click the plus sign.
    2. Select Installation Package Upload (template uploaded separately) and click Next.
       1. For Upload a Package, select the zipped file that contains the Pulse Collector Installation Package (for example, \PulseCol\version\linux\b1\ip, which has the Installation Package description file).
       2. For Upload an XML template, select the XML Template file (Collector.xml from the Templates Installation Package directory).
       3. For Upload an APD template, select the APD Template file (Collector.apd from Templates Installation Package directory).
    3. Click Finish.
13. Deploy the Pulse Collector Installation Package and Template:
    Tip

    You can also install Genesys Pulse Collector directly on the server by executing the Genesys Pulse Collector installation procedure from the Genesys Pulse Collector installation package, then uploading the Genesys Pulse Collector template (Collector.apd) using Configuration Manager.
    1. Click the Pulse Collector Installation Package to open the Properties tab.
       Important

       The Pulse Collector Installation Package status should be complete.
    2. Click the related icon and choose Install to open the IP Deployment Wizard.
    3. After the host selection, enter the Pulse Collector application name from the previous release as the application name and finish the installation.
       Important

       The InstallPath should point to an empty folder.
14. Update the Pulse Collector Application options:
    1. In GAX navigate to Configuration > Environment > Application Templates.
    2. Select the new Pulse Collector Application Template.
    3. Open the Application Options tab.
    4. Click More.
    5. Select Export to save the file with the Pulse Collector Template options.
    6. Navigate to Configuration > Environment > Applications.
    7. Open the Properties of the Pulse Collector Application object.
    8. Open the Application Options tab.
    9. Click More.
    10. Select Import and select the file you saved with the Pulse Collector Template options.
    11. Check Override.
    12. Apply the changes.
    13. If required, update the new options according to recommendations in the Genesys Pulse Deployment Guide. Also, you can use the backup file of the Pulse Collector configuration options as a guide of what to change.
15. Stop GAX.
16. In the Pulse installation folder, open the scripts folder to select the upgrade script for your RDBMS.
17. Execute the upgrade SQL script on your Pulse DB schema.
18. From the Pulse installation folder, within the dbtool folder, create the configuration file dbtool.cfg using the sample provided:

    db.type=<dbtype>
    db.url=<url for connection to db>
    db.user=<database username>
    db.password=<database password>
    config_server.host=<configuration server host>
    config_server.port=<configuration server port>
    config_server.username=<username to connect to configuration server>
    config_server.password=<password to connect to configuration server>
    

19. From the command line, run: dbtool.bat -m
20. Start GAX.
21. Start Pulse Collector.
22. All users must clear their browser cache.

You have successfully completed your deployment of Pulse.

What do I do next?

• Migrate to Pulse release 8.5.101.
• Review the Pulse migration path to migrate to an earlier release.