Changes between Version 20 and Version 21 of Software/Versions/RelNotesMuaOneTwoOne


Ignore:
Timestamp:
03/25/14 08:31:04 (5 years ago)
Author:
smith@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Software/Versions/RelNotesMuaOneTwoOne

    v20 v21  
    1212* The usual guidance and caveats apply, see https://iam.cf.ac.uk/trac/RAPTOR/wiki/Software/Upgrade this page for help on managing updated files during upgrades. 
    1313* If upgrading any of the components on Windows from v1.0.x to v1.2.1, see https://iam.cf.ac.uk/trac/RAPTOR/wiki/Software/UpgradeWindowsOneDotZeroDotExToOneDotTwoDotOne for a specific note about what looks like an error - but isn't - that you will encounter. 
    14 * If upgrading the Raptor ICA or MUA components on Windows from v1.0.x to v1.2.1, then it is very important to note that this upgrade with overwrite your ICA/MUA's event-release.xml (this is required to support some new features). If you've customised these files in any way (i.e. if your ICA is sending events to a Raptor MUA on a different host), you will have to edit event-release.xml again to point to the correct server. Your previous file will be available at event-release.xml.backup if you need to see what changes you previously made. 
     14* If upgrading the Raptor ICA or MUA components on Windows from v1.0.x to v1.2.1, note that this upgrade with overwrite your ICA/MUA's event-release.xml (to support some new features). If you've customised these files in any way (i.e. if your ICA is sending events to a Raptor MUA on a different host), you will have to edit event-release.xml again to point to the correct server (your previous file will be available at event-release.xml.backup). 
     15* If upgrading the Raptor MUA, it is always a good idea to back up your data in case something goes wrong. If using the HSQLDB, simply take a copy of the {{{MUA/conf/data}}} directory. If using a "real" database, consult your manual for instructions (e.g. use "pg_dump" for Postgres). 
    1516 
    1617=== Enhancements ===