Install Domain separation plugin in already live Production instance?

Go to solution
Suggy
Giga Sage

‎12-22-2022 09:31 AM

We have 2 customers running their own insances (instance A and B).

Now they have decided to use only 1 instance. 'A' instance will be as it is, 'B' will be released and start using 'A'.

 

On 'A' domain separation plugin needs to be activated. 

 

1. Is it fine to activate 'Domain separation' plugin in already running instance?

2. If so, are there any challenges? Any issues? Anything to be aware of? (Apart of managing 'B' data into their respective domain)

 

Labels:
0 Helpfuls
  • 1,049 Views
1 ACCEPTED SOLUTION

Go to solution
Tom Sienkiewicz
Mega Sage

‎12-23-2022 06:11 AM

You definitely need to look at B both from data and process perspective, to understand how the process/configuration might have to differ from A. There might be conflicting requirments or at least a need to have certain logic run only for either of the domains (BRs, client scripts. Flows etc.).

 

Now technically yes you can activate DS in a live instance. What is going to happen is all your data in instance A is going to be placed into the global domain and be visible for everyone. So you will need to decide which data needs to be moved to the dedicated domain for A.

Then before you bring in any data for B, you need to create logic/rules for putting this data into dedicated domain for B (for example as part of transform maps).

You also need to review and plan which data needs to be visible to both domains (any foundational data etc.). If you expect global reporting requirments from both A and B domains, create another domain above A and B with access to both, or at least create dedicated visibility config for a "global reporting" kind of domain and users.

 

You should also review the domain separation support level of different ServiceNow products. Some of them already have rules to put data into the correct domain, for others you need to configure those yourself.

 

It will help if you start by cloning your prod into a sandbox instance, then activate DS there and play around/do initial analysis there.

View solution in original post

6 REPLIES 6

Go to solution
Sumit Maniktal1
Tera Expert

‎01-02-2023 05:54 PM

I haven't done a similar exercise but worked on domain separated instance for a good amount of years. Activating domain separation in an already live instance seems not to be a problem but as Tom mentioned you need assessment of data & code. The moment you activate domain separation in single tenant instance all the data & code will move to global domain but then it also means that data & code is visible to all domains.  You need to further assess what data like foundation data needs to stay common & what data need to be in domain for only A to have visibility to. Also same process to be followed for code e.g. a business rule implemented to achieve a particular functionality only meant for domain A needs to be in domain A & not in global. Similarly you need to have a migration plan for domain B with respect to their specific data & code. Domain visibility at group level can also be used to grant cross domain visibility as needed. This is going to be a massive exercise and like any change involves risk.

 

Wish you good luck & let me know if you have specific question

Preview file
11 KB