Take a snapshot of the VLA before proceeding with the upgrade
Once you have taken the snapshot of the VLA, execute the following steps to do the VLA upgrade:
Prerequisites
You are running version 1.3.1 VLA and have decided to upgrade it to version 1.4.1 VLA.
Procedure
SSH into the VLA as root.
Note:
If you are unsuccessful and see a "Network error:Connection refused" message, you may have to first start the SSH service on the VLA. To start the SSH service on the VLA, login as root from the vCenter VLA console. Enter the root password. You may then be asked to change the password for root account. Type in the new password twice. You then start the SSH service on the VLA using the sys_ssh command as depicted in the following figure:
You should now be able to SSH into the VLA successfully
Use any tool of your choice like wget, WinSCP, scp etc.
Execute the sys_software_update script to initiate the upgrade process. Specify the ISO file that you copied into the /system2 directory that will be used for upgrade of the VLA as depicted in the following figure:
Execute the reboot command.
Note:
Connection to the host will get closed due to the reboot. Once the VLA is up, SSH to the VLA as root. If you are unable to connect to the VLA via SSH, maybe the SSH service need to be started on the VLA. Follow the procedure in step 1 of this section to start the SSH service on the VLA. You will then be able to successfully SSH into the VLA.
Update the orchestrator workflows following the reboot of the VLA by executing the following command:
The older VMware Adapter for SAP Landscape Management that may have been installed on the SAP Landscape Management VM using the version 1.3.1 VLA will stop working following an upgrade to version 1.4.1 VLA.
Following the upgrade and reboot if you discover that the Tomcat vla-server is not available, based on the message on the console when you SSH to the VLA, the user password may have got cleared due to the upgrade process. Hence you will have to recreate the Tomcat user
Results
Upon successfully completing the previous steps, you should have upgraded the VLA from version 1.3.1 to version 1.4.1