Title:
Bug 73421:(Watson Migration Closure)In the last beta (I think) I raised an ER for supported, standardised CFADMIN settings storage in discrete files
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/
Reporter/Name(from Bugbase): Ben Davies / Ben Davies (Ben Davies)
Created: 10/31/2008
Components: Administrator, Administrator Console
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Major / Unknown
Locale/System: English / Platforms All
Vote Count: 3
Problem:
In the last beta (I think) I raised an ER for supported, standardised CFADMIN settings storage in discrete files. The thinking was that while those ’in the know’ could dabble with neocron.xml etc, working with these files was in no way supported by Adobe, undocumented and liable to change from release to release.
However having the data in discrete files is a huge advantage from a Server management point of view. CARs are an atomic and opaque storage format that suit one off backups and irregular migrations between servers. Having declarative settings in a plain text format that could be deployed and managed like source streamlines a lot of activities, such as:
- capturing application specific CFADMIN configuration in source control
- avoiding boilerplate CFADMIN API code in installers
- easy identification of CFADMIN setting differences between DEV/QA/Production
- easy deployment of settings using simple file copies or ant (and CFadmin API webmethod for refreshing, perhaps, or even auto-refresh)
The files themselves would a plain text file (probably XML) divided in an intelligent way for flexibility in deployment. Eg. 1 file per datasource, 1 file for all caching settings, etc.
Application overrides (if implemented) could then stored in application specific subfolders.
And the location of these (and all other configuration files/scripts or
resources likely to be changed or customised) would have a configurable root folder to allow non-standard defaults (I really hate messing with my application installation folders, and it is frequently a complication for backup requirements, change comprehension and source control).
Obviously security is a consideration for any
datasource (or other) passwords.
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3036525
External Customer Info:
External Company:
External Customer Name: Ben Davies
External Customer Email: 447227C844C7765A992015A8
External Test Config: 10/31/2008Attachments:
Comments: