
VMware vRealize Orchestrator Cookbook
By :

Here we will describe the update process for the Orchestrator appliance as well as the best way to get from 5.x or 6.x to 7. As a Windows install isn't supported in 7 anymore, please see the recipe Moving from Windows to appliance in this chapter. If you are updating a cluster, please see the recipe Upgrading a cluster in Chapter 3, Distributed Design first.
We need an older version of Orchestrator as well as access to a VMWare webpage.
There are two methods for updating the appliance. First there is updating via an ISO file and second, directly accessing the update repository.
Before you start updating
Make sure you have a backup or at least a snapshot of the Orchestrator VM. If you are using an external database, make a backup of the DB as well.
Follow these steps if you wish to use the ISO file.
https://[Orchestrator]:5480
Follow these steps if you wish to use the VMware repository. Your Orchestrator needs a HTTPS connection to the VMware website ( vmware.com )
https://[Orchestrator]:5480
.After we have the update source in place, we can finally update the appliance.
The update process of Orchestrator is pretty simple and straightforward. All versions have the default repository configured and with Internet access, you can use it directly.
Before you update, you should always read the release notes of the newest Orchestrator release to see if there are any problems you might encounter. The update from 5.5 or 6.x to 7 is pretty easy and just requires the newest 7 ISO.
If you are upgrading from 5.5 or 6 to 7 you might want to change the authentication to vsphere to make use of the vSphere 6 features.
In the Update | settings, there is also the ability to automatically check for updates as well as to automatically check and install updates. I personally wouldn't use the feature in any production setting; an update should always be a controlled process.
After an upgrade, you need to check your workflows. I have had several cases where a method, a standard library workflow, or a plugin wasn't working the same anymore. If you find something like that please report it to VMware so they can fix it in the next release.
If your Orchestrator has no Internet connection but you would still like to use the repository feature and you have a web server (for example IIS), you can do the following:
.zip
Update Repository Archive from vmware.com.\build\mts\release\bora-3571217\publish\exports\Update_Repo
.manifest
and package-pool
. Make sure that the folders are browseable and that they are accessible. In IIS you might need to add the .sig
and .sha265
file type as a text/scriptlet
MIME type.https://[Orchestrator]:5480
.
The recipe Upgrading a Cluster in Chapter 3, Distributed Design.
Change the font size
Change margin width
Change background colour