While the details and steps of each upgrade are slightly different, they have much in common and follow the same basic steps. This section describes the overall update flow. Its sub-sections describe the specific steps for the different upgrade scenarios. The following table shows the possible versions from which you can upgrade and the versions to which they can be upgraded:

Table 1. VLA Software Updates

Version

Can be Upgraded to

1.3.1

1.4.1

1.4.0

1.4.1

1.4.1

1.5.0

1.5.0

1.5.1

1.5.1

1.6.0

Caution:

Before performing any update, you should snapshot your VLA VM. In case the update does not produce a working environment, you can revert, from snapshot, to your current working system. The upgrade program will prompt you to ensure you have taken the snapshot before it allows you to proceed.

Note:

If you have already installed a VMware Adapter for Landscape Management on your LaMa system, you should first uninstall the adapter (Refer Uninstall the VMware Adapter for SAP Landscape Management on Microsoft Windows) before proceeding with the following VLA upgrade steps.

Upgrading the VLA involves the following high level events:

  1. Download an ISO file that contains the new version of the VLA to a specific directory on your existing VLA system.

  2. Run the upgrade program on your existing VLA, from the specific directory, providing the name of the file you downloaded in Step 1.

    This step mounts the ISO file and installs new and updates existing RPM files in your existing VLA's filesystem.

  3. Reboot the VLA

    Note:

    During the first boot after running upgrade, the 1.4.1 software does the following, depending on your previous version of the VLA:

    • From 1.3.1, it creates a new database used by the SA-API server (for vRA integration). 1.3.1 did not contain the SA-API server (for vRA integration). It was added in 1.4.

    • From 1.4, it updates the database used by the SA-API server (for vRA integration).

  4. Manually update the workflows in the VMware vRealize Orchestrator with versions installed on the VLA as part of Step 2.

    The VLA server and SA-API server (for vRA integration) leverage these workflows for some of its work. Each version of the VLA has its own set of said workflows.