Other configuration files do not contain settings that sites need to change often. If you do change the settings in these files, they usually need to be migrated by hand to migrate them between releases. After migrating these settings, you need to retest the resulting configuration. The reason for this hand-edit is that only the standard set of .properties files are designed to migrate between releases.
However, you may want to include some of these nonstandard configurations in the application-update.properties file. You may want to do so if you are not upgrading versions, but rather are packaging changes between a staging and a production server, or are packaging changes to deploy at another site.
The following is an example of the secondary files you might want to deploy with comments describing when these files would be needed.
# ---- Secondary Files to Deploy ----
# These files are changed at few sites and typically do not need
to be packaged.
# However you may wish to review the list to see if you need any of these entries.
# If you update, do compare these files against the stock ARCHIBUS
# file to see if search order or there are differences.
# If you added a non-stock language, include your main configuration file.
# extension=\WEB-INF\config\context\compatibility\afm-config.xml
# If you changed default paginated report preferences or added your own
# report templates, include those preferences.
# extension=\web-inf\config\reports\docx\report.*
# If you have changed default drawing control properties, include those preferences.
# extension=i:\web-inf\config\controls\drawing-control.xml
| Copyright © 1984-2014, ARCHIBUS, Inc. All rights reserved. |