Update core modules using the script.

During this step, you will update the core modules on all of the servers. Core modules must be updated prior to any others, and they must be updated from the command line using the launch-update script.

Procedure

  1. Stop all of the services by typing the following command from the C:\Program Files\APG\bin directory:
    manage-modules.cmd service stop all
  2. Use Windows Task Manager to verify that all of the APG services have stopped. Manually stop any services that are stuck in the “Stopping” state for more than a few minutes.
  3. The launch-update script is delivered through the module-manager, so update the module-manager module by typing the following command from the C:\Program Files\APG\bin directory:
    manage-modules.cmd update module-manager
  4. Launch the script from <install directory>\Tools\Module-Manager\<version no.>\bin by running launch-update.cmd.
    For example, the Module Manager version can be <install directory>\Tools\Module-Manager\1.16u3\bin.
    Note: Upgrade from 6.8u5 and 7.0u8 to 7.2.0.1 does not need event migration, as both of these have Elastic Search database. Also, running the event migration task throws an exception, which can be ignored.
  5. Review the modules that will be updated and the SolutionPacks that will be reconfigured.
  6. At the Proceed? prompt, press Enter to launch the update.
    The script starts updating modules. Let the script run uninterrupted. Once completed, the script lists which modules and SolutionPacks were updated and reconfigured successfully.
  7. To review the list of installed modules and their update status, type this command from the C:\Program Files\APG\bin directory:
    manage-modules.cmd list installed
    At this stage of the upgrade, only a few block-type modules should need to be updated. These will be updated later through the UI.

What to do next

After the launch-update script runs, the Windows collector indicates successful update of the Java module.

Note: It is normal for the Topology-Mapping Service on the primary backend, the frontend, or the additional backend to remain stopped at this point. The service will start automatically when the SolutionPack for VMware Smart Assurance M&R Health is upgraded on these systems.