Upgrade > Upgrade the platform components > Upgrade Smart Analytics > Upgrade to Service Manager 9.50 Smart Analytics on Linux

Upgrade to Service Manager 9.50 Smart Analytics on Linux

If you have installed an earlier version of Smart Analytics, follow the instructions in this section to upgrade your Smart Analytics to SM 9.50 Smart Analytics.

To upgrade your Smart Analytics on a Linux system, follow these steps:

  1. Before you upgrade your Smart Analytics, complete these tasks:

    1. Make sure that all the index tasks are finished.

    2. Stop all the Smart Analytics services.

    3. Back up all the Smart Analytics files.

  2. Obtain the Smart Analytics installer for Linux.

  3. Unpack the .zip file and then execute the binary file (setupSmartAnalyticsLinuxX64.bin) from the command line.

  4. Read the introduction, and then press Enter.
  5. Read the License Agreement, and then press Enter repeatedly until you see DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENTS? (Y/N).
  6. Type Y, and then press Enter.
  7. Type 2 to select Upgrade, and then press Enter.

  8. Choose the version of Smart Analytics installed by typing the corresponding number, and then press Enter:

    • 1-Smart Analytics 9.40 or earlier
    • 2-Smart Analytics 9.41

  9. Continue with on-screen instructions, which vary based on the Smart Analytics version you selected in Step 7.

    ClosedSmart Analytics 9.40 or former

    If you selected Smart Analytics 9.40 or former, continue with these steps:

    1. Choose the current architecture of the Smart Analytics installed typing the corresponding number, and then press Enter:

      • 1-Standalone
      • 2-Distributed

    2. Specify the IP address of the machine on which you have installed Service Manager server, and then press Enter.

      You need to specify the IP addresses (or host names) of the Service Manager servers that are permitted to send administrative and query actions to the Smart Analytics servers. Use commas to separate multiple addresses (do not use a space before or after a comma).

      Note use a valid FQDN or IP address for the server address. Do not use the localhost or 127.0.0.1.

    3. Select the components that you want to upgrade by typing the corresponding numbers. Use commas to separate multiple choices (do not use a space before or after a comma). The servers that are available for upgrade vary depending on the Smart Analytics architecture you specified.

      Note  

      • For Smart Analytics components which were installed in the same root folder, upgrade them at the same time in a single upgrade process. Otherwise, components may not be uninstalled completely when you uninstall Smart Analytics.

      • Upgrade the components separately by performing the upgrade process multiple times under the following conditions:

        • Your current version of Smart Analytics is 9.34
        • The Smart Analytics components to be upgraded are installed in different parent folders or physical machines
      Architecture Components Available for Upgrade
      Standalone

      IDOL Server

      Image Server
      Distributed

      Smart Analytics Proxy

      Content Server

      Image Server

      Image Proxy Server

    4. Specify the parent folder where the selected Smart Analytics components are installed, and then press Enter.

      Note  

      • If you are upgrading the Smart Analytics proxy server, the folder should include the IDOL folder.
      • If you are upgrading a distributed content server, the folder should be the parent of the content folder.

    5. Follow the configuration steps to configure the components you selected. Press Enter after each configuration step.

      Note The number of copies (that is, the value of Replicas plus one) must be no more than the number of child servers. If you create more copies than there are child servers, DIH does not start.

    6. Check the pre-upgrade summary, and then press Enter.
    ClosedSmart Analytics 9.41

    If you selected Smart Analytics 9.41, continue with these steps:

    1. Specify the parent folder where the current Smart Analytics is installed, and then press Enter.
    2. The installer automatically detects and lists which components have been installed. Review the detected components, and then press Enter.
    3. Specify content folder names as needed, and then press Enter. By default, the installer automatically specifies all the content folder names.
    4. Specify image server folder names as needed, and then press Enter. By default, the installer automatically specifies all the image server folder names.
    5. Review the message that Smart Analytics is ready to upgrade, and then press Enter.
    6. Check the pre-installation summary, and then press Enter.
  10. Wait for the installation to complete, and then press Enter to exit the installer.

Post-upgrade actions

Perform the following actions after you upgrade your Smart Analytics:

  • When the installation is complete, do the following:

    • Check the StartAll.sh and StopAll.sh files under <Smart Analytics Installation>/Scripts folder for any commands that start or stop services not on your local machine. Delete or comment out such commands and then add source ./Start[Service Name of your previous content] or source ./Stop[Service Name of your previous content] as needed.
    • Delete all the start[Name of Service not on local machine].sh and stop [Name of Service not on local machine].sh files under <Smart Analytics Installation>/Scripts folder.

  • If you upgrade from Service Manager 9.41 to Service Manager 9.50, you need to do full re-index of Catalog_Library after you upgrade to Smart Analytics 9.50.

  • If you upgrad from Smart Analytics 9.40 or earlier versions to Smart Analytics 9.50, then during the upgrade process, the existing configuration files would be renamed to <component name>-old.cfg. After you finish the upgrade, compare it with the new configuration file. If there is any customized change made in the previous .cfg file and it is still valid, manually add it back to the new .cfg file.
  • If you upgraded from Smart Analytics 9.40 or earlier versions to Smart Analytics 9.50, you need to re-index the Hot Topic Analytics data. However, do not start a training for Smart Ticket.

  • If you upgraded from a distributed Smart Analytics to Smart Analytics 9.50, add the following lines before the [actions] section in the content[x].cfg file for the system to clean up expired documents:

    //--------------------------- Schedules ----------------------//
//expire and compact data everyday
[Schedule]
Expire=TRUE
ExpireTime=23:00
ExpireInterval=24:00

    Note With this configured, the system automatically deletes all the expired documents at 23:00 every day. By default, the expiration date for documents is set to 365 days.

  • If you upgraded a standalone Smart Analytics with version 9.34, locate the [Security] section in the <Content1>/content1.cfg file, and then add the // comment characters to the parameters as displayed in the following:

    [Security]

    SecurityInfoKeys=123,144,564,231

    DebugDecrypt=true

    //0=NT_V4

    //1=SharePoint

  • If you upgraded a distributed Smart Analytics proxy server with version 9.40 or former, the previous configuration files would be renamed to <component name>-old.cfg, and you need to manually modify the following configurations in the <SmartAnalytics>/IDOL/IDOLServer.cfg file:

    Configurations after upgrade Configurations in your previous file (<component name>-old.cfg) You need to modify the value to
    VirtualDatabases=1 VirtualDatabases=<x> VirtualDatabases=<x>

    [vdb0]

    dbname=Users

    type=combinator

    mapsto=0:Userss

    [VDB0]

    DbName=News

    Type=Combinator

    MapsTo=0:News

    Do not change
     

    [VDB<x>]

    DbName=my_database

    Type=Combinator

    MapsTo=<y>:my_database

    Note The number of x starts from 1.

    [VDB<x>]

    DbName=my_database

    Type=Combinator

    MapsTo=<y+1>:my_database

    Note  

    • You must add the VDB configurations by their number sequence.
    • There may be other content between two VDB configuration sections.
    • Make sure the total number of the VDB configuration sections equals to the number specified in the VirtualDatabases parameter.
    • There is no difference if you use the upper or lower case for the section name of [VDB<x>].
    [DistributionIDOLServers] Number=2 [DistributionIDOLServers] Number=<x> [DistributionIDOLServers] Number=<x+1>

    [IDOLServer0]

    Name=SmartSearch

    Host=127.0.0.1

    Port=20010

    DistributeByFieldsValues=GlobalSearch

    		   Do not change

    [IDOLServer1]

    Name=Content1

    Host=127.0.0.1

    Port=

    DistributeByFieldsValues=CONTENT1

    [IDOLServer<x>]

    Host=12.3.4.56

    Port=20010

    DistributeByFieldsValues=CONTENT<x>

    Note The number of x starts from 0.

    [IDOLServer<x+1>]

    Name=Content<x+1>

    Host=12.3.4.56

    Port=20010

    DistributeByFieldsValues=CONTENT<x+1>

    Note  

    • You must add the IDOL server configurations by their number sequence.
    • Make sure the total number of the IDOL server configuration sections equals to the number specified in the [DistributionIDOLServers] Number parameter.

  • If you upgrade from Smart Analytics 9.41 to Smart Analytics 9.50, you need to manually modify the following configuration sections:

    In the <SmartAnalytics>/IDOL/IDOLServer.cfg file:

    Existing configurations You need modify the configuration to 
    [IndexQueue]
IndexQueueInitialSize=10240
IndexQueueMaxHistorySize=500
IndexQueueMaxPendingItems=10240

[SetDateFields]
// Fields containing the document date
Property=DateFields
PropertyFieldCSVs==*/DREDATE,*/DREDATE_*,*/DATE,*/DATE_*,*/*_DATE,*/*_TIME

[Logging]
LogExpireAction=compress
LogOldAction=move
LogMaxSizeKBs=20480

    [IndexQueue]
IndexQueueInitialSize=10240
IndexQueueMaxHistorySize=10240
IndexQueueMaxPendingItems=0

[SetDateFields]
// Fields containing the document date
Property=DateFields
PropertyFieldCSVs=*/DREDATE,*/DREDATE_*,*/DATE,*/DATE_*,*/*_DATE,*/*_TIME,*/MODIFIED_EPOCH,*/LASTMODIFIED

[Logging]
LogExpireAction=Day
LogMaxOldFiles=7
LogOldAction=delete
LogMaxSizeKBs=102400

    In the <SmartAnalytics>/Level2proxy/IDOLServer.cfg file:

    Existing configurations You need modify the configuration to 
    [Server]







[IndexQueue]
IndexQueueInitialSize=10240
IndexQueueMaxHistorySize=500
IndexQueueMaxPendingItems=10240

[Logging]
LogExpireAction=compress
LogOldAction=move
LogMaxSizeKBs=20480

    [Server]
//store index data on disk only when the index cache is full or when the MaxSyncDelay(120 seconds by default) is reached.
DelayedSync=TRUE

[IndexCache]
IndexCacheMaxSize=102400


[IndexQueue]
IndexQueueInitialSize=10240
IndexQueueMaxHistorySize=10240
IndexQueueMaxPendingItems=0

[Logging]
LogExpireAction=Day
LogMaxOldFiles=7
LogOldAction=delete
LogMaxSizeKBs=102400

    In the <SmartAnalytics>/Content<x>/Content<x>.cfg file:

    Existing configurations You need modify the configuration to 
    [IndexQueue]
IndexQueueInitialSize=10240
IndexQueueMaxHistorySize=500
IndexQueueMaxPendingItems=10240

[SetDateFields]
// Fields containing the document date
Property=DateFields
PropertyFieldCSVs=*/DREDATE,*/DREDATE_*,*/DATE,*/DATE_*,*/*_DATE,*/*_TIME

[SetMatchFields]
PropertyFieldCSVs=*/*_MATCH,*/EDK_*,*/*_MATCH_INDEX, */*_MATCH_WEIGHT*,*/*_BOOLEAN

[Logging]
LogExpireAction=compress
LogOldAction=move
LogMaxSizeKBs=20480


[LanguageTypes]
GenericTransliteration=TRUE
Transliteration=false

    //The amount of memory to allocate to store the most commonly occurring terms. (using 500MB as term cache here, recommended range is 10240 to 2048000. ) 
[TermCache]
TermCachePersistentKB=512000 

//--------------------------- Schedules ----------------------//
//expire and compact data everyday
[Schedule]
Expire=TRUE
ExpireTime=23:00
ExpireInterval=24:00

[IndexQueue]
IndexQueueInitialSize=10240
IndexQueueMaxHistorySize=10240
IndexQueueMaxPendingItems=0

[SetDateFields]
// Fields containing the document date
Property=DateFields
PropertyFieldCSVs=*/DREDATE,*/DREDATE_*,*/DATE,*/DATE_*,*/*_DATE,*/*_TIME,*/MODIFIED_EPOCH,*/LASTMODIFIED

[SetMatchFields]
PropertyFieldCSVs=*/*_MATCH,*/EDK_*,*/*_MATCH_INDEX, */*_MATCH_WEIGHT*,*/*_BOOLEAN,*/IMPORTMAGICEXTENSION

[Logging]
LogExpireAction=Day
LogMaxOldFiles=7
LogOldAction=delete
LogMaxSizeKBs=102400

[LanguageTypes]
GenericTransliteration=TRUE
Transliteration=true

    After you modify the configurations, restart all related Smart Analytics components of which such configuration are modified. Then, on the machine where level2proxy is located, reload updated configuration files dynamically and regenerate match index by visiting the following URLs :

    • Reload updated configuration files dynamically:

      http://localhost:20011/DRERESET

    • Regenerate the match fields:

      http://localhost:20011/DREREGENERATE?Type=Match

      Wait for a few minutes for the regeneration to complete.

Send Help Center feedback