Tables at Root level vs Site level

This topic has 4 replies, 5 voices, and was last updated 18 years, 3 months ago by Richard Hart.

Creator

Topic
September 18, 2006 at 12:39 pm #48783
Kathy Zwilling
Participant
Has anyone implemented the feature of Cloverleaf where you can put a table in the root level tables directory (unix) instead of at the site level and have it be seen at a global level by all sites?

We have a table that is used in multiple sites and would like to consolidate it into one place for updates and use by the interfaces. It works well but at the root level but one cannot travel to the root level tables directory to do editing.

I know we can copy the file into a site, edit it and copy it back but I wondered what others might be doing.

Thanks for your input.

Kathy
Creator

Topic

Viewing 3 reply threads

Author

Replies
- September 19, 2006 at 1:47 pm #59657
  Mark Thompson
  Participant
  Kathy,
  
  We created an additional site and soft linked the site Tables directory to the root Tables directory. Also did the same for the site tclprocs directory. That way we can use the GUI’s to view and edit root items.
  
  Reminder to self: Changing items in the root Tables directory may mean mulitple sites need “purge caches” or process restarts.
  
  On our AIX 5.2 system:
  
  rm -r $HCIROOT/newsite/Tables
  
  ln -s $HCIROOT/Tables $HCIROOT/newsite/Tables
  
  Second reminder to self: Double-check any backup or site migration utilities to see how they handle links.
  
  - Mark Thompson
  HealthPartners
- September 19, 2006 at 9:01 pm #59658
  Jim Kosloskey
  Participant
  Kathy,
  
  We created a site which is only a repository for ‘global’ objects – such as Tables, variants, Tcl procedures.
  
  We then use a symbolic link from the using site to the g
  
  ‘global’ site.
  
  We do not link from the Root site because an install might remove the soft links (it does with Tcl procedures) and we do not want to have to remember to restore the links.
  
  We have been doing this for a number of years, have many sites and all has worked well.
  
  There is an enhancement request in to have Cloverleaf(R) support a hierarchy structure for local an global objects in a multiple site architecture natively.
  
  Jim Kosloskey
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- September 20, 2006 at 7:11 pm #59659
  Anonymous
  Participant
  I prefer using symblolic links as Mark mentioned.
  
  thanks
  
  Reggie
- September 21, 2006 at 5:19 am #59660
  Richard Hart
  Participant
  We don’t use tables, but we share tclprocs, typically with an application site and a library.
  
  We use a series of makefiles for test/prod, but the creation is
  
  mktclindex {*.tcl,../LIB2/*.tcl}
  
  Our tclIndex file is
  
  set auto_index(top_code_security)
  ]
  
  set auto_index(top_code_smat_clean)
  ]
  
  set auto_index(top_code_smat_filelist)
  ]
  
  set auto_index(top_code_trx_id)
  ]
  
  set auto_index(Print)
  ]
  
  set auto_index(XlateMsg)
  ]
  
  …
  
  set auto_index(gen_code_msginfo)
  ]
  
  set auto_index(gen_code_printmsg)
  ]
  
  set auto_index(gen_code_resend)
  ]
  
  set auto_index(gen_code_splitter)
  ]
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.