Grouper Developers Forum

["GW Brown, Information Systems and Computing" <>]

Apologies for the late posting.

--On 18 September 2007 13:21 -0400 Jessica Bibbee <> 
wrote:

> 4. Building the UI - review Michael Gettes' recent experience
>   ( https://mail.internet2.edu/wws/arc/grouper-dev/2007-09/msg00025.html )
>
>    . API - UI - gsh relationship and multiple builds and multiple tomcats

One way of sharing `single` API and UI installations among multiple 
environments is to make use of symbolic links in Unix. There are very few 
core files which need differ between environments:

Grouper API:
Contents of conf, particularly:
  grouper.hibernate.properties
  sources.xml
  log4j.properties

Grouper UI:
  build.properties

I would envisage a utility script e.g. ginstall, which is configured with a 
working directory e.g. grouper-instances, and the location of grouper and 
grouper-ui.

`ginstall create mlist` would create:

grouper-instances/mlist
grouper-instances/mlist/grouper
grouper-instances/mlist/grouper/conf
grouper-instances/mlist/grouper-ui
grouper-instances/mlist/grouper-ui/build.properties.
grouper-instances/mlist/custom-grouper-ui

and symlinks to other files/directories in grouper and grouper-ui

`ginstall mlist` would cd to the particular instance and might put gsh on 
the path and modify your prompt.

In this way, the main parts of grouper and grouper-ui are shared, but 
configuration files can be modified for particular environments, and it 
would be easy to switch between environments.

Currently gsh.sh has hard-coded paths set at build time, however, it will 
be possible to overcome this i.e. provide GROUPER_CONF in the environment.

Gary

----------------------
GW Brown, Information Systems and Computing