Unbundling the Enterprise Manager Cluster Upgrade capability (1 of 5)

Blog Post created by Chaitan_Shet Employee on Jul 4, 2017

[Part 1 of 5]


Dear Customers,


Thanks for all your kind support and time you have given me and my team all along the EM Cluster Upgrade development phase. The EM Cluster Upgrade functionality (going GA soon!) is made up of 5 sub-features. 

This is a series of 5 blog posts. Each post would pick up one sub-feature that makes up the upgrade process, thus providing you an insight into what the sub-feature is, what it does, the value it provides, how to use it, screenshots


Please feel free to ask any questions or post your comments below

If you feel there is some sub-feature that could be valuable, please post it in your comments below



These are the sequence of steps that a user would follow to upgrade their EM's 

Discovery  -> Backup -> Pre-upgrade Checks -> Upgrade -> Post upgrade validation & Cleanup


Feature name




A production cluster is on APM 10.3 and needs to be upgraded to APM 10.5.2 SP1.



This phase kicks off the upgrade process for us users after you login into APM Command Center.


What does the discovery feature do?

A typical EM Cluster looks like this. 



For now let us put aside TIM and Agents (each of which have its own plans) as they are not part of the scope for this article.

This feature as the name indicates discovers these components that make up the EM Cluster. It discovers the:               1) Database (DaataBaaze - As my Czech mates would say and I simply love that word!  2) APM Team Center (ATC)/Webview 3) Collectors 4) MoM


How to use it?

1) Login into ACC and please follow the screenshots below ;-)


2) What does the 'add existing' step do? It allows us to transfer the installers and controllers (the piece that allows us to do the discovery) to each of the hosts that house the components that make up your EM Cluster. Upon clicking the 'add existing' drop down, you would be presented two options.


  • Automatic Discovery - In this mode you provide the hostname and the credentials to the server on which the Webview is installed. Again there are two options to login into the server based on the security policies in your organization. They are: 1) SSH Username and Password 2) Private Keys
  • Manual Discovery - Suppose your organization policies forbids you from doing a network transfer of any files over to these hosts, you could use the manual discovery option. Under this option you can manually copy the installer files over to the hosts that make up your EM Cluster.

In this example, we have selected to use the SSH Username and Password


3) Enter the hostname and credentials to the box where the Webview is installed and click on Discover



It would show you the status on the Discovery process

Upon completion of the Discovery process, you can also download the results into a log file


(Please click on the image above, to see it more clearly)

Upon completion of the discovery process, the user is presented with a screen (shown above) where on the left hand panel all the components that make up the EM cluster are shown along with the hostname on which it is installed. On the right hand side a user can see the summary information about the cluster.


You can also get a summary of every component by clicking on the left panel on the component on which you desire to get info upon. For example, I wanted to see the summary of the MoM and here is what it looks like. 



One key assumption made

For automatic discovery, the credentials for all the hosts that make up one single cluster are the same.



  • Can we discover multiple clusters with a single discovery?
    • No. We can discover one cluster at a time
  • Can we run multiple discoveries at once?
    • At present we recommend running one discovery at a time. i.e once you kick off a discovery, allow it to finish and only then kick off the discovery of other clusters?
  • What are all the components that are discovered?
    • MoM 
    • Collectors
    • DB
    • Webview (APM Team Center)
  • Can we run a discovery and then do an upgrade at some later point?
    • We would recommend you to run a discovery each time before you do an actual upgrade. The reason is because the configurations of the cluster (maybe a Collector was replaced) could have changed from the last time you ran a discovery


Thanks for your readership.......see ya in Episode 2, where I shall pick up the Backup functionality and extrapolate on it.


until next time....