This topic describes how to upgrade to MDEX Engine 11.3.2 from the following earlier versions :

To upgrade the MDEX Engine:

  1. Stop Endeca services using the Services console on Windows, or the $ENDECA_ROOT/tools/server/bin/shutdown.sh script on UNIX.

  2. Back up the MDEX Engine installation directory of the earlier version.

    This step is useful in case a rollback is necessary. You do not restore any data from this backup after the upgrade.

  3. Uninstall the MDEX Engine using the Add and Remove Programs utility in the Control Panel on Windows, or by using an rm command on UNIX.

  4. Install MDEX Engine 11.3.2. For instructions, see the MDEX Engine Installation Guide.

  5. Modify the PlatformServices/workspace/conf/eac.properties file, and change com.endeca.mdexRoot to the new value of ENDECA_MDEX_ROOT.

    (This ensures that the EAC starts MDEX Engine jobs using the correct value for the ENDECA_MDEX_ROOT environment variable. )

  6. Restart Endeca services by using the Services console on Windows, or the $ENDECA_ROOT/tools/server/bin/startup.sh script on UNIX.

  7. Rerun a baseline update.

  8. If you are using the Presentation API to build your front-end application, install it on the server running your Web application. For instructions, see Presentation API Installation Instructions and Release Notes.

    Note: If you do not upgrade your frontend application to the version of the Presentation API that comes with the MDEX installation, you may need to use the--back_compat flag of Dgraph when you start the Dgraph engines after migration. Use of the --back_compat flag is necessary when the current version of the Presentation API is not supported by the upgraded version of Dgraph by default. For more information about the -back_compat flag, see the Oracle Commerce Guided Search Administrator's Guide.

  9. If you are using the Assembler to build your front-end application, download and install Tools and Frameworks. For instructions, see the Tools and Frameworks Installation Guide.

  10. (Recommended) Modify any front end application code that uses the Assembler API to use the upgraded version of that API.

  11. (Recommended) Re-index your data using the upgraded version of dgidx.

  12. If necessary, upgrade other Oracle Commerce Guided Search components, such as Content Acquisition System, Tools and Frameworks, and Platform Services.

    To determine the compatibility of the MDEX Engine with other installation packages, see the Oracle Commerce Guided Search Compatibility Matrix available on the Oracle Technology Network.


Copyright © Legal Notices