When upgrading to v7 frm v6.0.6 do my existing AM and CCM areas merge into a single area
4 answers
My knowledge is:
Comments
You do not need to rename any servers. Where in the documentation were you given the impression that you needed to? There is one part of the upgrade process where you have to make sure that you are using the same name in V7 as you used in V6 (and not just select the "use default name" box). This is to make sure that you are not renaming any servers. As to having two applications that look identical and are named the same ... the point is that in 7.0, there is one application (CCM) that provides the functionality that used to require two applications (CCM and AM). The AM functionality is now just a project area option. Because the CCM and AM functionality have a large number of integration points that are simplified if all the project areas are in the same application, this can greatly simplify your end user experience.
It is not the case that I will by default end up with only one application as currently I have been told (and the documentation on Knowledge centre also says it) that there is no capability to merge the existing CCM and AM databases so I end up with 2 CCM applications with one of them enabled for Architecture Management.
It is important not to confuse an "application type" with an "application instance". The application types are "CCM", "QM", "RM", etc. The "application instances" can be identified by their server URL, e.g. "https://myhost1:9443/ccm", "https://myhost2:9443/ccm"
Hi Benjamin,
Note that the context root of the RMM instance (including the port) stays the same after the upgrade (right?).
Yes, except for an anomaly that I was not aware of, until I researched this question. In particular, that anomaly is that if you had installed RTC 6.x and RMM 6.x in the same package group, then because of limitations in the Install Manager, you unfortunately have to create a new package group that has just RMM 6.x, and then have to "server rename" your RMM 6.x instance into a new server instance that is associated with the new package group. The server renamed instance will now have a new URL (if it is on the same server as the original RMM 6.x instance, the server renamed RMM 6.x instance will just have a different port number). Only then can you perform the upgrade to 7.x.
Comments
Thanks for providing the quote from the Upgrade Guide, since this let me track down the source of the confusion. In particular, what this is saying is that when you performing the upgrade, when you are done, you will have a "new instance" of EWM, and no longer have an instance of RMM ... namely ... your 6.x RMM instance now "becomes" an EWM instance. So where does this "move" issue come from? As I was researching your question, and clicking through the Interactive Upgrade Guide, I discovered the anomaly described in my comment in the other thread. But note that even if you had your 6.x RMM and 6.x RTC installed in the same package group, which means you need to move one of them into a new package group before you can upgrade (meaning you have to server rename one of those servers), you don't have to move it into a different server instance ... you can server rename the 6.x RMM to the new package on the same server instance ... but you will have to give it a new port number.
1 vote
For new customers starting with v7+ it is great that they have capabilities of 2 applications now in 1 CCM application.
However for older customers with v6 instances installed you will end up with 2 same applications (CCM) after upgrade while one of them is able to use AM capabilities. This is confusing for customers and We are being asked about it all the time.
Please try to work on some feature that enables merging AM + CCM into one CCM after upgrade. Otherwise it does not look good and confuse users.