Some name

The first question is: why? After that, it's a matter of defining the nodes, channels, services, etc for the teo systems and linking them. Since they are two GRMS systems, it's unlikely you can use the delivered stuff because it might get confused. Just treat them as you would any other two applications you wanted to link.

The Dragon is correct – it is weird that you want the same configs in both. Sounds like you simply want to clone. That’s easily done on the data base level.

I was on a project where they had four separate HR systems and had to integrate them into ELM. My approach was to give each gateway a unique name such as COMMON1, COMMON2, etc. That allowed me to use all other delivered parts.

Why? A common reason is because the ""main"" HRMS is too much work to upgrade at the present but the business wants a module available in a newer version of HRMS so they install a second instance and integrate the two until they can upgrade the main.

Another common reason is to deploy something to the internet because some shops require separate web server, app server and database instance for anything accessed from outside the firewall.