Master Site Use and Switch Over

[Michael Lacriola]

Hello all. I hope Jim K is listening on this one.

I finally have time and need to begin the use of master sites.

Question 1: How many can I have? I would like to create 2, one for test, one for prod.

Question 2: I would like to begin using it for tables and tclprocs mostly at first until I get my variants squared away. How do I begin moving things over? Do I just copy the table into the master site, delete it from the other site and set the other site to use the master site? I would suppose I would need to stop/restart engine processes that use that table (safest). With tclprocs, same thing would occur except that I would have to run mktclindex in master site and the other site that will use it the master site?

I’m available for any conversation. I have several tclprocs that are used quite frequently all over my engine sites and would be much easier to have it in one area.

Suggestions welcome.

Topic

[Mark Thompson]

Michael,

1) You are limited to 1 master site per Cloverleaf root.  This is unfortunate — it would be very nice to set the master site at the site level instead of the root level.

2) Your migration scheme is pretty good.  Set the master site first.  Move tables, tcl procs (with mktclindex on master site), then bounce affected processes.  You can purge caches (for tables) and reindex (for Tcl procs), but restarting the process is safer.

The very safest way is to make the changes with any affected sites shut down.  That prevents the extremely small possiblity that a seldom-used proc gets called for the first time before you re-index or bounce.

- Mark Thompson
HealthPartners

[Author]

Replies