Skip to Content
0
Former Member
Jul 23, 2013 at 05:24 PM

Migrate Universe 3.1 to 4.0 issues with connection

23 Views

So I am attempting to migrate a universe, webi, Qaaws from 3.1 to 4.0 for a dashboard. I am using the Upgrade Management Tool (UMT) in order to do this. I have gone through and done this several different orders and they all lead back to issues with the universe. I have tried migrating (Incremental Upgrade) the universe, followed by webi, then qaaws all separate instances, as well as doing them all at once (all scenarios selecting migrate dependencies as well).

Everything will succeed - as it should. The first issue is with the QaaWS. When opening them in the QaaWS designer, the links were incorrect and seemd to strip the number from the end (ex: server name: "testserver01" displayed as: "testserver"). I have determined that the issue is with the universe. When I import the universe in Universe Design Tool, it force closes - UDT has experienced an error and force closes on me. When I open the universe as a local copy, then export it, I can then go and re-publish the webservices, and it gives me the correct address as "testserver01".

When I go to view the universe in the CMC, under properties > connection..nothing is displayed, it is blank. My question is, am I missing something during the migration that would cause the connection to show up as blank? 😕

I have tested taking a universe in 3.1 production, "promoting" to 3.1 test, and in the CMC>Properties>Connection, it still shows up as blank. However, in the 3.1 Universe Designer, the connection was visible there - but not in CMC properties of the exact same universe. I saved the universe in the Designer, exported the universe, checked CMC properties, then the connection info was there. I would open the universe that was migrated from 3.1 to 4.0 in UDT, save, export as I had done (above) with the 3.1 universe, but it force closes on me.

Thank you for all the help