Jump to: navigation, search

LFMT Checklist

Use this section as a proactive checklist for successful LFMT planning, deployment and usage.

Item # Description
1 Read this document thoroughly and plan your LFMT deployment carefully before starting the LFMT installation/deployment.
2 Given Genesys LFMT integrates to Genesys Engage components, ensure you have Genesys Engage knowledge, experience and training before installing LFMT.
3 Review the LFMT Architecture section to understand the LFMT architecture and components.
4 Review the New in this Release section to new release features/fixes.
5 Review the Additional Information section for details on TLS, Best Practices, FAQ's, Regex's and Release Notes prior to starting LFMT planning and deployment.
6 Review the Planning section to understand RDBMS sizing and requirements along with GAX dependencies.
  • This section also contains the LFMT Sizing XLS template which should be used to properly size your production LFMT deployment
  • If needed, this completed LFMT Sizing XLS template can be sent to Genesys Customer Care, via a standard Case for further sizing assistance/guidance/recommendations; create a Genesys Case with a Description of LFMT Sizing Assistance
  • Do not move onto production Deployment until your LFMT deployment has been planned/sized according to your specific site requirements
7 Review the Deployment section for Prerequisite and Deployment details.
  • Ensure DNS between the LFMT Host's and the Workbench Agent 8.5 Host's is functioning and robust
    • Hosts must be resolvable by hostname for LFMT to function properly
  • Aligning with other Genesys Engage products, LFMT leverages a Genesys CME Template and Application Object approach
  • CME Connections from/to certain Applications must be configured for LFMT to function successfully - Example LFMT CME Connections diagram
    • Connections Summary:
      • GAX connection to LFMT Collector(s) and LFMT DAP(s) - a GAX application may have multiple connections to more than one LFMT DAP object
      • LFMT Collector connection to GAX and LFMT DAP - an LFMT Collector application object must have only one connection to a LFMT DAP object
      • LFMT Indexer connection to LFMT DAP - an LFMT Indexer application object must have only one connection to a LFMT DAP object
  • CME Ports must be open/free on the host(s) for LFMT to function properly
    • Ports Summary
      • LFMT Collector Ports = default (i.e. 8001), ftmessaging (i.e. 8020) and sftmessaging (i.e. 8030)
      • LFMT Indexer Ports = default (i.e. 8002)
      • GAX / LFMT Client Ports = default (i.e. 8080), messaging (i.e. 9001) and ftmessaging (i.e. 9002)
      • Workbench Agents 8.5 Port = default (i.e. 7999), ftmessaging (i.e. 7101) and sftmessaging (i.e. 7102)
        • also ensure Port 2552 is also open/free on the Host(s) as this is used for Actor Messaging
  • Two of the LFMT Options/Settings do not have a default and their respective configuration is mandatory prior to starting the LFMT Applications in GAX
    • LFMT Indexer
      • retention_period
      • cls_location - ensure the user has write permissions to this path
    • LFMT Collector
      • cls_location - ensure the user has write permissions to this path
      • package_location - ensure the user has write permissions to this path
    • Review LFMT Options/Settings for details
  • Database connectivity
    • Ensure connectivity to the LFMT database is successful
    • i.e. correct username, password, database name
    • i.e. the database is configured to accept external connections
    • the LFMT DAP object must have a unique [lfmt]/site=<site_name_here> Site option configured - i.e. "Chicago_1"
    • an LFMT DAP object is needed for each and every LFMT Collector/Indexer pair
    • each LFMT DAP must connect to a different RDBMS database schema
      • i.e. LFMT DAP "Chicago_1" connects to RDBMS schema "Chicago_1" and LFMT DAP "Chicago_2" connects to RDBMS schema "Chicago_2"
8 The LFMT Workbench Agent 8.5 component has to be deployed on the respective Engage Hosts (i.e. sip, urs, gvp etc) from which log files are to be collected
  • If the Workbench Agent 8.5 component is not installed on the Engage Hosts (i.e. sip, urs, gvp etc) it will not be possible for LFMT to collect the respective Host Application log files.
  • Workbench Agent 8.5 is ONLY for LFMT
  • Workbench Agent 9.x is ONLY for Workbench 9.x
    • both Workbench Agents 8.5 and 9.x can be deployed on the same Host if/when both LFMT and Workbench tools are to be used
9 Review the LFMT Config Options/Settings section for LFMT configuration setting/option details.
10 Review the Using LFMT section for details on the usage of LFMT.
This page was last edited on September 12, 2022, at 08:43.
Comments or questions about this documentation? Contact us for support!