New Site Doesn’t have all procs

Kirby,

There are a few different ways you can accomplish this.  If you want to have a copy of these procs in each new site you create, then you can copy them into the $HCIROOT/siteProto/tclprocs directory and run the ‘mktclindex’ command while in that directory.  Whenever you create a new site, then the procs will be there.

Or if you just want to have these procs available to all sites (not physically copied), you can place them in the $HCIROOT/tclprocs directory.  Then all of the sites will have access to them, but they’ll only be physically in one place.

Depending on whether or not you need site specific versions of these (i.e. site1’s procs are customized, different from site2’s) or one size fits all will determine which way you want to go.

Just keep in mind that as you upgrade to newer versions of Cloverleaf, if you have your procs at the root level ($HCIROOT/tclprocs), then you’ll need port them to the new version, as the ‘site promotion’ process won’t capture these procs at the root level.

Hope this helps.

Jim Cobane

Henry Ford Health

If you’re on 5.6 or later, you can put your procs in the master site tclprocs directory.

Kirby,

If these are the Quovadx/HealthVision/Lawson supplied procs, then they are likely within the file named ‘recover_33.tcl’ (or similar name) in the $HCISITEDIR/tclprocs directory.

If you are going to start having multiple sites, I would encourage you strongly to move to 5.6 or above so that you can place your Xlates, Tables, tclprocs, etc… in the master site.  We have multiple sites here and use 5.6 and we had multiple sites when I was working for a previous employer on 5.3.  Trust me it is a godsend to be able to keep your procs in one place.

You can have a ‘master’ site in pre 5.6.

We have been multi-site here for versions 3.5 through 5.4 and set up our own ‘master’ site.

I is really fairly simple and our transition to the Cloverelaf supported madster site went quite smoothly.

You do a site init to create a site. This site will NEVER have a NetConfig nor will it ever be started. It is simply a directory structure to be a repository for your common objects (Tables, variants, procs, etc.).

Then you do symbolic links from your various sites to the ‘master’.

With Cloverleaf 5.6 and beyond the need for symbolic links goes away but now all your common objects are where they belong because when you get to 5.6 or beyond you simply make your ‘master’ site the Cloverleaf Master Site.

However, transitioning from a single site environment to a mulitple site environment should be undertaken after some thoughtful planning not just firing up new sites.

There are upsides and downsides to multiple site environments but overall I think multi-site is worth it.

I mainatain it is not whether you will be multi-site but when.

I have operated in a multi-site Cloverleaf environment for nearly 15 years. First with my former employer where we were either the first or among the first multi-site environments, through my current employer weher I brought in the concept.

Since I favor multi-site architecure right from the beginning someone else will need to point out what they see as advantages of single site but obviously there is less perceived administration.