404
edits
Changes
no edit summary
IMSMANG stores translations of the application in several places. Translations and localisations of data elements are stored in the IMSMANG database and are backed up with the database backup. The .properties files used to translate the IMSMANG interface are stored externally to the database, but they can be added to the IMSMANG Backup as an option. If changes are made to the .properties files, it is recommended to back them up after each change as well as each time a full backup is made.
===Other Backup Considerations===
While IMSMANG Backup backs up all of the files used in the typical operation of IMSMANG, there are other customisable files that should also be backed up. These include:
* map customisations
IMSMANG does not automatically back up customisations made to maps used in IMSMANG. Users can make changes to the imsma.mxd file, create or modify ESRI style files, add symbology or make many other changes to maps, but these files are not included in the IMSMANG Backup and must be separately backed up and managed.
* base maps
It is recommended that information managers make backups of maps that are imported into IMSMANG for use on client computers. While IMSMANG Backup backs up the maps when they have been imported, these base map files are not managed within IMSMANG and should be backed up manually to allow for customisation and later import.
* external reporting tools
External reporting tools and other add-ons are not backed up by IMSMANG and should be backed up manually. These include any tools using ODBC connections to IMSMANG such as Microsoft Access databases, Microsoft Excel spreadsheets, OpenOffice connections and Crystal Reports. Information managers should ensure that these tools get backed up manually or automatically.