Jump to: navigation, search

Migration Steps from LFMT 8.1.250.xx to 8.1.260.xx

The following five major components exist in the LFMT application system. The steps for migration for each component have been highlighted, as applicable.

Important
Upgrading LFMT does not require the need to re-push shared keys to remote application server hosts.

LFMT Client

  1. Stop Log Indexer and all Log Collector schedules through the GAX application.
  2. Stop the GAX application that hosts the LFMT plug-in.
  3. Navigate to the existing LFMT GAX plug-in location <GAX_HOME>/webapp/WEB-INF/lib
  4. Delete the .jar files associated with LFMT version 8.1.250.XX from the above location.
  • cctools-utils-8.1.242.02.jar
  • gax-lfmt-8.1.250-SNAPSHOT.jar
  • Proceed installing the LFMT Client version 8.1.260.xx following the steps of the installer (install.sh or setup.exe).
  • Start the GAX application that hosts the LFMT plug-in.
  • Log into the GAX application that hosts the LFMT plug-in.
  • Navigate to the Manage Log Collection section in the Configuration tab.
  • Save the current settings. This will update plug-in options set in the 8.1.250.XX version of LFMT.
  • Important
    Existing Log Collector schedules saved in the 8.1.250.XX version of GAX do not except the new exception option when edited in LFMT 8.1.260.XX.
    Important
    After upgrading the LFMT Client you may need to clear your browser cache to see changes in the interface.

    LFMT Server

    Install the LFMT Server version 8.1.260.xx following the steps of the installer (install.sh or setup.exe).

    Important
    If the location of LFM_HOME changes, be sure update the system environment variable and restart the LFMT host.

    LFMT Log Index Database

    LFMT version 8.1.260.XX requires the user to complete an upgrade of the log file index database. To complete this upgrade please execute the upgrade script for the matching DBMS against the current log file index database. Three upgrade scripts are provided in the LFMT Server utilities directory. These scripts are named as followed:

    • lfmdb_81250XX_to_81260XX_ora.sql
    • lfmdb_81250XX_to_81260XX_mssql.sql
    • lfmdb_81250XX_to_81260XX_postgres.sql

    LFMT Application Configuration

    Create and remove the following options in the LFMT configuration options

  • Create the following options in the app_config section of the LFMT configuration:
    • absolute_cls_folder_path=<value of absolute_prod_folder_path>
    • retention_period=<value of prod_retention_period>
  • Remove the following options in the app_config section of the LFMT configuration:
    • absolute_prod_folder_path
    • absolute_temp_folder_path
    • cls_archive
    • prod_retention_period
    • temp_retention_period
    • arch_retention_period
    • reduce_bandwidth_usage
    • Use_C_Indexer
    • compress_logs_after_indexing

    (Optional) Cygwin deployments

    LFMT verison 8.1.260.XX now provides users with the ability to upgrade existing Cygwin deployments on remote Windows hosts. This process is optional, but does provide updated Cygwin libraries. To complete these upgrades please complete the following procedure:

    • Locate and extract the cygwin.zip file that is found in the <LFMT Server Install Directory>\utilities directory.
    • Create a new network shared folder from the extracted cygwin.zip file.
    • Locate or create the cygwin_conf.txt file described in the section Deploying Cygwin automatically to other Windows Hosts.
    • Right-click on the command prompt and select “Run as administrator”.
    • Navigate to the directory containing the deploy_cygwin.pl file.
    • Enter perl deploy_cygwin.pl. When prompted to upgrade existing deployments, enter y.
    • Continue following the prompts.
    Important
    During the execution of upgrading you will be asked to define and installation location on the remote host. Be sure that this location is the same as was defined in the initial deployment of Cygwin.
  • This page was last modified on February 27, 2015, at 11:33.

    Feedback

    Comment on this article:

    blog comments powered by Disqus