Clovertech

How To Link All Sites so they can share the same config file

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › How To Link All Sites so they can share the same config file

  • Creator
    Topic
  • February 10, 2012 at 4:21 pm #52934
    Chris Hai Hoang
    Participant

      Hello everyone,

      I am new to Cloverleaf here and my question is, I created 3 new sites on the new Cloverleaf Interface Engine and they are dev1, dev2 and dev3 (in /opt/healthvision/integrator folder). How can I link them so they can share the same config files?

      OS: Redhat Linux 5.4 ES/AS

      Cloverleaf version 5.8

      Thanks in advance for your help.

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • February 10, 2012 at 6:42 pm #75985
        Jim Kosloskey
        Participant

          Chris,

          You probably only want to share some onjects (config files) among the sites like formats, tclprocs, tables, and potentially Xlates.

          Define a Master Site and place your objects in that site’s dirctory is the quickest method.

          However, to edit or even view thos common objects, you will need to actually be in the Master Site from the GUI.

          Another method used before the inception of the Master Site was to define a site you consider to be your ‘Master site’. Then soft link from your local sites to your ‘Master’ site for the objects involved. There are many issues with this approach so make sure you understand all of the pros and cons of this approach before embracing.

          email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

        • February 10, 2012 at 8:09 pm #75986
          Chris Hai Hoang
          Participant

            Hi Jim – Thanks for the information. It sounds like keeping these files (Tables, Xlate, formats, tclprocs) separate between live and dev (Live1 and Dev1) would be best.

          • February 10, 2012 at 8:16 pm #75987
            Jim Kosloskey
            Participant

              Chris,

              In my opinion you should have your dev/test environment on a different Cloverleaf platform than the Prod environment.

              You can still deploy the Master site on each platform and have multiple sites on each platform.

              So on your dev/test platform you could have an ADT site or set of sites; a LIS site or set of sites; A EHR site or set of sites, etc. All of these sites could then share the common objects for devl/test

              You could do likelwise for Prod (even name your Master Site the same as test/dev if you like).

              I don’t think it is prudent (although possible) to have your dev/test and prod defined as sites on one Cloverleaf.

              email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

            • March 15, 2012 at 5:07 am #75988
              Chris Hai Hoang
              Participant

                Thanks Jim. I have set them up as suggested.

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.