Product Selector

Fusion 5.12
    Fusion 5.12

    Upgrade Fusion Server 4.2.6 to Latest SP

    This article describes how to perform the following upgrade:

    • From version: 4.2.6

    • To version: Latest SP

    Unlike other Fusion upgrades, 4.2.6 SPs are a patched upgrade that can be applied directly to Fusion 4.2.6. If you are not already using Fusion 4.2.6, complete the upgrade to Fusion 4.2.6 before installing the latest Fusion 4.2.6 SP.

    You can view the application files to download at Fusion Server 4.x File Download Links.

    This upgrade is available to qualified customers whose Lucidworks plans include extended support.

    Consult Upgrade to Fusion 4.x for information on upgrading to a different version of Fusion.

    If you require a fresh installation of a Fusion 4.2.6 SP, consult Install Fusion 4.x.

    Preliminary upgrade steps (optional)

    If you are upgrading to apply the latest Log4j updates to your existing deployment, please follow the proceeding steps.

    1. Log in to the Fusion Admin UI with an administrator account.

    2. Select System → blobs

    3. Open webapp-admin-war → admin-webapps

    4. Delete the admin.war, insights.war, app-studio.war WAR by selecting each entry and clicking Delete Blob.

    For more information about blobs, see Blob Storage.

    Upgrade an existing Fusion installation (Linux, Windows)

    Linux

    To upgrade an existing Fusion installation on Linux:

    1. Place the fusion-4.2.6-service-pack-patch.jar and fusion-4.2.6-sp3.tar.gz on each server hosting Fusion services.

      The script does not update external Solr and Zookeeper installations.

    2. Shut down all Fusion services on each server that will receive the patched upgrade.

    3. Run the fusion-4.2.6-service-pack-patch.jar jar (java -jar fusion-4.2.6-service-pack-patch.jar) and follow the prompts.

    4. Start the Fusion services.

    Windows

    To upgrade an existing Fusion installation on Windows:

    1. Place the fusion-4.2.6-service-pack-patch.jar and fusion-4.2.6-sp3.zip on each server hosting Fusion services.

      The script does not update external Solr and Zookeeper installations.

    2. Shut down all Fusion services on each server that will receive the patched upgrade.

    3. Run the fusion-4.2.6-service-pack-patch.jar jar (java -jar fusion-4.2.6-service-pack-patch.jar) and follow the prompts.

    4. Start the Fusion services.

    Enable the Tika parser service

    Fusion 4.2.6 SPs include an asynchronous Tika parser service. This service is not automatically enabled upon upgrading. To enable the Tika parser service:

    1. Open fusion/conf/fusion.properties in a text editor.

    2. Add the following Tika entry to the end of the file.

      # Tika parser service
tika-server.port = 8889

# If your tika server is properly secured behind a firewall, then you can then set the
# -Dtika.server.allowLocalFileOptimization=true to allow you to use the "local file optimization" which reduces
# http overhead during local tika parses.
tika-server.jvmOptions = -Dtika.MAX_HEAP_MB=1000 -Dtika.NUM_PROCESSES=2 -Dtika.ALLOW_LOCAL_FILE_OPTIMIZATION=true

    3. In the log-shipper section of the file, add the following in a new line:

      log-shipper.logs.tika-server = java

    4. Save the file.

    5. Download the tika-server-log4j2.xml file.

    6. Add the TikaServer logging configuration to the fusion/conf directory.

    To automatically start the Tika parser service when starting Fusion, add tika-server to the group.default line. Otherwise, you can start the Tika parser server with the $fusion/bin/tika-server script.