multiple .xconf files

[MikeLockwood]

We currently have:

- site.xconf,(the .xconf from wca),alcon_site.xconf (which has most properties that we've changed over time)

Just had a long meeting discussing our best practices relative to having properties in multiple files, what should go in each, where they should be in sequence, etc. This resulted from a property that we had duplicates of that caused a problem.

It seems that many people have a relatively sophisticated approach to this subject and handle with multiple .xconf files referenced from site.xconf. Looking foradvice / comments before we take action here to modfiy what we have. Especially interested if anyone has a document with "here's how we handle this."

thanks in advance

[VivekMadhav]

We have nv.xconf, location codebase/ext/nv/nv.xconf. All custom xconf entries are in nv.xconf. in declarations.xconf we have added an entry for nv.xconf. So when we execute xconfmanager all values from nv.xconf gets propagated. Key benefits:

a. all properties values at one place.
b. No need to have multiple .xconf files.
c. No entry in site.xconf

[pwilliams-3]

Hey Mike,
I have attached a document that explains how we manage multiple .xconf files in several different architectures depending on the situation.

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image001.jpg@01CEEA7D.F1F85B40]

[bellj]

An interesting approach and I had never heard of it.
I have two .xconf, one for all custom properties and one for troubleshooting (verbosities, etc.) in the Windchill folder and entries to them in site.xconf.

What is the benefit of have an entry in declarations.xconf over site.xconf?

joe bell
GSIMS Administrator
GPS Sustainment Information Management System
719-474-8899
bellj@gpssims.com<">mailto:bellj@gpssims.com>

[ddemay]

Mike et. al,



We do the same as below with one exception, we have a company_site.xconf to
override values only present in site.xconf. If the value is not server or
install specific and is business function, we have a codebase/company.xconf
similar to what is mentioned below linked from declarations.xconf. I also
tend to isolate heap and performance tuning recommendations to a separate
file as these are largely server specific. We also typically comment out
the xconf file for windchill configuration assistant, instead incorporating
desired changes into our own files.



I view site.xconf as some holy file never to be touched except at install
time when we link in our own file. Corny perhaps, but I just steer clear of
it with passion.



I also recommend version control site.xconf, declarations.xconf and the
codebase/company.xconf in Subversion or similar.



One other last point, we symbolically link / shortcut (NTFS junction) these
files to ones that also contain the hostname the file is for.



Dave