Multiple projects on 1 TS: structuring files

Frederik

Hi!

Does anybody have a list of all the TS config and project files and their possible locations? This to integrate several projects on a TS server, and to structure the files in a easy to maintain way.

Background

Until now, we only had 1 project per TS server. We are now asked to change that, and put several projects together, on Solaris TS 5.5.2 SP4.

So, we need to think of structuring our global config and project files (e.g. iw.cfg, submit.cfg, scripts for CGI/menu-items & templating & workflow, opendeploy configs, etc) into well-organized directory structure.

The whole TS was set up here by an external consultant, now it's our job to do the integration.

To start that up, I'm planning to compile an exhaustive list containing every global config and project file (type), with mention of its default location, and other possible locations in the directory structure. It's a small task, just a matter of going through all the manuals and taking notes ;-)

But it occurred to me that perhaps somebody already did that exercise? Or having other advice? TIA.

Adam Stoller

Pretty much all the TS server configuration files are monolithic - i.e. there is only one per server. Configuration options for different branches and such are done *within* the configuration file *not* with distinct configuration files.

Of the ones you mentioned:
- iw.cfg is generally in /etc - about the only thing that is branch-configurable within it is the proxy settings.
- submit.cfg uses paths within it to distinguish settings for one branch from another
- CGI scripts are all located in IWHOME/httpd/iw-bin/ - in order to make them branch specific you need to provide that code within the script (or a wrapper) itself
- templating.cfg uses paths within it to distinguish settings for one branch from another
- available_templates.cfg (workflow) uses paths within it to distinguish settings for one branch from another
- deployment configurations are located within IWODHOME/conf/ only (I believe there's a feature request on file for allowing sub-directories or such within there)

About the only configuration files that are truly branch specific at this time are the templating datacapture.cfg and presentation templates.

Some folks have, I believe, conjured up processes for "compiling" the global configs from branch-specific components, but I'm not sure how successful they've been in doing that - and it's not officially supported.

Good luck,

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com