mercator directory structure and naming conventions

[holly75]

We are changing our Mercator directory structure to make it a little simpler for us. I would love to hear about any of your experiences with directory structures, suggestions you may have. I know that we need to keep a Systems directory for .msl. Speaking of the Systems directory, when we use the Command Server and deploy from NT to AIX, could we send the .tmp file to the Systems directory -or is that only reserved for the .msl?
Our proposed Dev directory structure is:

Mercator6.5
development
trees
application name
treename.mtt
enterprisetrees
treename.mtt
maps
mapname.mms and mdqname.mdq
deploymentscripts
ifd.msd
mapfiles
input or output textfiles.txt
mapconfigfiles
mapconfigfiles.txt
logfiles
logfiles.log
errorfiles
errorfiles.txt
archivefiles
archivefiles.txt

Also, any suggestions pertaining to naming conventions would be very helpful.
Thanks,
Holly

 

[ekimr]

Mmm....looks fine but things I would take into consideration are avoiding hardcoded paths in development maps (for trees,destinations, source?) - clearly these are to be avoided when porting to AIX but also are you having a directory for maps/trees that have been tested and are now in UAT then live? thus another 2 or 3 areas on your PC before a Map goes live.

What about workfiles?

I personally would leave MSL files with thier own directories and not think about tmp files.

You are breaking trees up by application? Do you want many trees to maintain if some fields are common cross applications?

Just some thoughts - not answers though!

 

[Willbert]

We've gone for

../merc65/<env>/apps/<app_name>/

where env is the environment (dev, uat.. etc) and then
/auditlogs
/adapterlogs
/data/
/dbint
/maps
/scripts
/trees
/workfiles

The directories under /data contain sub dirs depending upon the app requirements to hold all the working business data and archives. Its useful to keep workfiles, adapterlogs and auditlogs under their own directories for housekeeping. Obviously you don't need the /trees or /dbint on the server (AIX) side.

All of this application stuff sits in a seperate LV to the actual Command/Event Server stuff. We have opted to keep the /systems directory along with the Event server code as we are running multiple instances of the Event Server, and it is the easiest way of keeping track which ES is executing which systems (also 5.0 makes you do this). We have prefixed our .msl files with the app_name that they relate to, so that we can x-ref them back.