Using update sets with domain separation configaration - best practice?

[akosadravetz]

We are planning to implement a domain separated structure with several domains under the top, each having some unique configurations. Now we are only testing it in a developer environment, using one update set and backing it up regularly.

Normally (in a non-domain separated model) it is enough to export the update set and import it to another instance (e.g. other dev or a non-prod), and it works like a charm, but what about importing an update set from a domain separated structure? What is the best practice to do that? We've just had our first try, but ran into hundreds of errors. Does the update set contain everything about the domain separation? Or do we have to manually configure the hierarchy first before importing the update set?

Thanks for sharing your experiences!

[michalewandowsk]

Hi,

You can list all your domains by visiting Domains Admin > Domains. Then after you filter your list and you have all domains you want to export - right click on the header of the table and select 'Export > XML'. In this way you'll export all domains from the list, so no need to do it one-by-one.

Reg. the check. I don't know ad-hoc method for doing this. Maybe I would simply run background script to check domain-name:sys_id pairs on DEV, then would do the same for any other instance and after parsing output data I would compare sys_ids. But, I think it's not needed as XML files transfer complete data payload - together with sys_id and any other attributes.

[darpanap]

HI Michal

That's great, thanks for the Update.

Now that i have domains xml file for Dev instance, i will just mention the next steps to be taken, please correct me if i am wrong.

1)I would now go and import the domain xml file being in "Global Domain".

2) Now i need to import the update set, so i will again being in Global Domain, goto Retrived updateset under system update sets->Import Update Set from XML

3) Once uploaded i will Preview the update set(Hopefully i should not get any error now since i have exported and imported the domains as well for Dev to Prod)

4) Once Previews i will commit the update set.

Result: Since i have committed the update set, now my Application, modules, tables, workflow etc, would be present under the domain i have created them in my Dev instance. All my applications would be now listed in my application picker if successfully imported.

Thanks

Darpana

[michalewandowsk]

I would say yes, but I'm not in your instance so cannot be 100% sure. But basically, if domains were only problem during commitment, transferring them to target instance before committing update should work.

[darpana]

Hi Michal

Thanks for the information.

It worked perfectly fine in production instance for domain separataion and achieved great results.

Thanks u so much for your help.

[amaradiswamy]

Hi michal,

Will there be any negative implications if I change ui action condition to not to check for domain and commit the update set?

Thanks

Swamy