About migrating from 11.1 to 11.2

To migrate your Tools and Frameworks installation from 11.1 to 11.2, you must first create backups of your configuration files and application content, then upgrade to the latest Tools and Frameworks package. Afterwards, you can restore Workbench configuration from your backups, and update application configuration from backups.

Migrating from Tools and Frameworks 11.1 to 11.2 consists of the steps below. They are described in detail in the following sections:

  1. Create backups:

    1. Back up Workbench configuration from the %ENDECA_TOOLS_CONF%\conf directory.

    2. Use the export scripts included with Tools and Frameworks 11.1 to export user information from version 11.1.

    3. Back up Workbench by running the export_site script for each application you are migrating.

    4. Back up any Forge data ingest configuration by creating a copy of the config\pipeline directory in your application.

    5. If you use CAS, back up config\CAS and config\MDEX directories.

    6. Optionally, back up each deployed application directory, for example, C:\Endeca\apps\Discover.

    7. Stop and uninstall your Tools and Frameworks 11.1 Workbench.

  2. Upgrade the MDEX Engine to 6.5.2.

  3. Upgrade Platform Services to 11.2

  4. Upgrade Tools and Frameworks to version 11.2.

  5. Restore Workbench configuration from the backups created in Step 1a.

  6. Restore each of your applications:

    1. Deploy the 11.2 version of your application.

    2. If you are using Experience Manager, and you want to use the workspace feature introduced in 11.2, export the deployment settings to a temporary directory.

    3. Restore Forge configuration from backups.

    4. Restore CAS configuration from backups.

      Note

      You should see a warning in the console that the Dgraph is down and search term expansions have to be manually updated by running the update_search_term_expansions script.

    5. Initialize your application.

    6. Repeat the substeps above for each application you are migrating.

    7. Restore Workbench user information using the import_users script.

    8. Restore Workbench content from the modified export file created in Step 6h by running the import_site script.

    9. Run a baseline update to load data into the Dgraph and start it.

    10. If you are upgrading to 11.2 for the first time, run the update_search_term_expansions script to add the searchTermExpansions property.

    11. Verify that Workbench configuration and application content are present in Workbench. Optionally, promote content to your live servers.

    12. Repeat the substeps from 6g above for each application you are migrating.

  7. If you are using Experience Manager, and you want to use the workspace feature introduced in 11.2, import the deployment settings you exported in Step 6b.

  8. Add the userState property to the following bean definitions in the Assembler context file for your application, assembler-context.xml:

    1. CartridgeHandler_RedirectAwareContentInclude

    2. CartridgeHandler_ContentInclude

    3. NavigationCartridgeHandler

  9. In the Assembler context file for your application, assembler-context.xml, delete the ecrStoreFactory bean. In 11.2, all store factory configurations must use FileStoreFactory. Update all references to the ecrStoreFactory bean to storeFactory, or the ID used in the FileStoreFactory bean.

  10. In the Assembler context file for your application, add the appName property to the Store Factory bean and the mdexResource bean: 

    <property name="appName" value="${workbench.app.name}" />

  11. Delete the store.factory property from the WEB-INF/assembler.properties file. 

    store.factory=ecrStoreFactory

Copyright © Legal Notices