John,
I would make your Master Site its own site with that being its only purpose.
In other words, no integrations defined or running in it.
For Tcl, what i would do is to make sure the candidates to be ‘global’ (in the Master Site) are writtten such that they are usable in any site.
Any procs which are not written that way should be left where they are until they can be re-written if that is your intent.
You can move Procs one at a time, a few at a time, or all at once.
Obviously you will want to test this out in your Test environment first to get your procedures down.
After the move, you will need to do a mktclindex on both the site(s) tclprocs directory that contributed the Tcl procs as well as the Master Site.
Then you can either reindex and reload from the NetMonitor (can only do one at a time so maybe not for the en mass approach) at either the thread or process level – or – stop/start the processes which should now pick up the procs which have been moved (picked up from the Master Site).
So the most important step might be making sure the procs to be moved are good candidatees to be global.
Something to be aware of – you cannot ‘see’ the Tcl procs which reside in the Master Site from another site GUI – you need to be in the Master Site. You can reference the procs from the NetConfig or an Xlate for example but not to edit or even see in the GUI Directory tree.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
