Is it possible to migrate just one universe of many? We’ve got separate BOXXX.keys set up each for their own instance, (PROD, DEV, QA) - can I move one universe from DEV to QA? Does anyone know?
Thanks,
Nancy
Listserv Archives (BOB member since 2002-06-25)
YES YOU CAN,
You already have the universe on your hard drive, once you change your bomain.key you can navigate between the different instances. Change your bomain.key to QA and export the new Universe from your hard drive to the QA repository. If that doesn’t work, save the universe that you want to migrate to a floppy, go to the QA instance and export it from your floppy. You do have to either create a new connection or use one that is appropriate.
hope this helps!
Aris
Listserv Archives (BOB member since 2002-06-25)
I’m surprised that Steve Krandel hasn’t jumped all over this one yet. 
There’s a gotcha when you use multiple security domains. If you export a universe to a different security domian, it gets assigned a different universe ID. Once that happens, all the documents that use that universe won’t be able to recognize it anymore. You’ll have to go into each document and manually reassociate it with the universe into order to make it aware of the new universe ID.
The most widely recommended way to “dev”, “qa”, and “prod” universes (and documents) is to have just one security domain, and multiple universe and document domains. If you want to have "dev, “qa”, and “prod”, you would have a total of six domains - three universe and three document - in addition to the security domain. That way, you won’t have to switch BOMain.key’s and you won’t have to worry about universes getting new ID’s.
There are some legitimate reasons to have multiple security domains, of course, such as if you want to “dev”, “qa”, and “prod” the security domain itself (although this isn’t usually necessary unless you’re really paranoid), or if you have a global deployment and you need local security domains for better login times.
BTW, if you ever meet Steve in person, ask him to explain the “12-step” process to you. It’s fun to watch his face contort when he even thinks of it.
Regards,
Paul
Listserv Archives (BOB member since 2002-06-25)
Hmmm… how come Steve Krandel hasn’t jumped all over this one yet?
There’s a gotcha when you use multiple security domains. If you export a universe to a different security domian, it gets assigned a different universe ID. Once that happens, all the documents that use that universe won’t be able to recognize it anymore. You’ll have to go into each document and manually reassociate it with the universe into order to make it aware of the new universe ID.
The most widely recommended way to “dev”, “qa”, and “prod” universes (and documents) is to have just one security domain, and multiple universe and document domains. If you want to have "dev, “qa”, and “prod”, you would have a total of six domains - three universe and three document - in addition to the security domain. That way, you won’t have to switch BOMain.key’s and you won’t have to worry about universes getting new ID’s.
There are some legitimate reasons to have multiple security domains, of course, such as if you want to “dev”, “qa”, and “prod” the security domain itself (although this isn’t usually necessary unless you’re really paranoid), or if you have a global deployment and you need local security domains for better login times.
BTW, if you ever meet Steve in person, ask him to explain the “12-step” process to you. It’s fun to watch his face contort when he even thinks of it.
Regards,
Paul
Listserv Archives (BOB member since 2002-06-25)