Jump to: navigation, search

Migration to LFMT 8.5.101

Moving from 8.5.000.xx/8.5.100.xx to 8.5.101.xx

LFMT Components

It is required that all of the LFMT components are updated to 8.5.101.xx (LFMT Client, Indexer, Collector, and Workbench Agent). These components are not backwards compatible with the 8.5.100.xx versions.

Important
After updating the LFMT Client to 8.5.101.xx, please ensure that there is not an "original-gax-lfmt.jar" file in the {GAXInstall}/webapp/WEB-INF/lib directory. If this file does exist, please delete the file.

Database

Moving from LFMT 8.5.000.xx/8.5.100.xx to 8.5.101.xx does require a schema update to the already existing database tables. The update scripts are provided in the {CollectorInstall}/utilities/dbscripts folder. After the scripts have been run, all data will be preserved in the existing database.

Moving from 8.5.000.xx > 8.5.100.xx

LFMT Components

It is required that all of the LFMT components are updated to 8.5.100.xx (LFMT Client, Indexer, and Collector). These components are not backwards compatible with the 8.5.000.xx versions. The Workbench Agent release 8.5.100.xx is also required to be deployed to all application hosts. Please see the Workbench Agent deployment guide for further information.

Database

Moving from LFMT 8.5.000.xx to 8.5.100.xx does not requires any schema changes to the already existing database tables. The same provisioned database from LFMT 8.5.000.xx can continue to be used for LFMT 8.5.100.xx.

Moving from 8.1.xxx to 8.5.xxx

LFMT 8.5.xxx encompasses major changes to the tool's design and deployment. Currently, a migration path from LFMT 8.1.xxx to LFMT 8.5.xxx does not exist. For questions concerning how to best move to the LFMT 8.5.xxx architecture, please contact Genesys Customer Care.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on October 12, 2018, at 10:42.