Upgrade the MATRIXX Engine Chain

You can follow the procedure below to upgrade an engine chain for a single sub-domain to the latest version of MATRIXX Digital Commerce.

About this task

Before upgrading the engine chain with the procedures in this section, make sure that:
  • You have the upgraded pricing file available and you have followed the instructions in the discussion about upgrading My MATRIXX.
  • You have upgraded all of your MATRIXX Gateways and Web Apps and configured them to continue using the pre-upgrade MATRIXX schema by pinning the schema version. For more information, see the discussion about pinning and upinning schema versions.
  • You have read the information about Traffic Routing Agents (TRAs) in this documentation set, and are familiar with the different TRA functions and how they work with the MATRIXX Engine. For details, see the discussion about MATRIXX Digital Commerce core components in Architecture Overview.
  • You will upgrade each TRA-PROC and TRA-PUB cluster at the same time you upgrade MATRIXX Engine that it works with. You will upgrade TRA-RT-(SI/DR)s (for routing traffic to multiple sub-domains) in a later topic.

The following overview steps refer to the MATRIXX Digital Commerce servers and engines shown in the diagram in the discussion about general upgrade prerequisites. The other procedures in this section give details on the process.

Procedure

  1. Decide on an engine upgrade order. For information, see the discussion about setting the upgrade order.
  2. Back up the Engine configuration files.
  3. Update the Engine configuration on a staging server.
  4. Stop the target engine.
  5. Stop the TRA-PROC (or TRA-PROC with RCP) and TRA-PUB servers.
  6. Upgrade the target engine.
  7. Configure the target engine. This includes copying the upgraded /tmp/create_config.info configuration file to the ${MTX_CUSTOM_DIR} directory on any processing blade servers, and then running the configure_engine.py script.
    For details on creating this file, see the discussion about upgrading the engine configuration.
  8. Configure the target engine shared storage device (SAN).
    The shared storage device must be attached as a SAN mount on the publishing server with read-write permission, and attached on the processing servers as an NFS mount with read-only permission. For details, see the discussion about configuring the storage devices in Installation and Configuration.
  9. Install the latest Traffic Routing Agent RPM file on the target engine processing servers and publishing servers.
  10. Configure the TRA-PROC and TRA-PUB. For information, see the discussion about validating and starting a TRA HA pair in Installation and Configuration.
  11. Validate and start the TRA-PROC and TRA-PUB and then start the target engine.
  12. (For Major and Minor upgrades) If this is the first standby engine in the chain that you are upgrading, load pricing when the "waiting for manual price loading" message appears in the /var/log/mtx/mtx_debug.log on any of the processing servers of the engine being upgraded.
  13. After the target engine reaches a STANDBY state, upgrade the next engine.