Difference: APPX500to502Upgrade (7 vs. 8)

Revision 82020-02-11 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="Appx531Installation"

APPX 5 Special Installation Instructions for upgrading within the APPX 5.x series

Line: 24 to 24
 
    • Regenerate your Import subroutines. The new subroutine takes advantage of the new fields in XVALUE. The old subroutines will not be compatible.

Special Upgrade Instructions when upgrading to APPX 5.4.2

Changed:
<
<
  1. The internal header of 64 bit pointer files (FMS type 9) has changed in 5.4.2 (see bug http://bugtracker.appx.com/view_bug.jsp?bugid=3314). Release 5.4.2 will not be able to access 64 bit files created in a previous version until you run the recover process. From a command line, invoke APPX with the '-recover' flag as follows:
>
>
  1. The internal header of 64 bit pointer files (FMS type 9) has changed in 5.4.2 (see bug http://bugtracker.appx.com/view_bug.jsp?bugid=3314). Release 5.4.2 will not be able to access 64 bit files created in a previous version until you run the recover process. From a command line, invoke APPX with the '-recover' flag as follows:
 
$ /appx -recover PROSPECT.dat PROSPECTNEW.dat
APPX Recover Utility:
              Input Filename = PROSPECT.dat
Line: 58 to 58
 

Special Upgrade Instructions when upgrading to APPX 5.4.4

Release 5.4.4 includes new SSL certificates that are not compatible with older clients. In order for an older client to connect to 5.4.4 (or higher) you must set SSL to 'disabled' in the Advanced preferences. Alternatively, you can install the new 5.4.4 client first, it will still connect using the older SSL certificate. After all desktops have been upgraded, you can upgrade the engine.

Added:
>
>

Special Upgrade Instructions after upgrading to APPX 5.5.x from a release earlier than 5.4.x

You only need to perform these tasks manually if you are upgrading to 5.5.x from a release prior to 5.4.0. When upgrading to 5.5 from release 5.4.0 or higher, the installer will automatically handle these tasks.

These steps should be performed immediately after installing 5.5.x.

  1. Scratch all the files in the 0SA Struct folder:
    1. In Windows: del <appxpath>\0SA\Struct/*
    2. In Linux: rm -r <appxpath>/0SA/Struct/*
  2. Log on on APPX and from the main APPX menu, click on System Administration ->File Management -> System Admin Files and click on 'Create Files'. This will create new Structure files for those that have changed, and create new files for the new features.
  3. Scratch the Structure files for the DOCUMENT and STMT file in all your applications. For ease of use, you can scratch the Structure file for all applications, including the 0-apps, and then create all applications in the next step. Commands like 'rm -f <appxpath>/??/???/Struct/DOCUMENT.dat' and 'rm -f <appxpath>/??/???/Struct/STMT.dat' will do this in Linux.
  4. Run 'Create Files' for all your applications. This will create the new Structure files for DOCUMENT and STMT. Log on on APPX and from the main APPX menu, click on System Administration ->File Management -> Design Files. When prompted, blank out the Application and Version. This will select all applications, all versions. Then you can just click 'Create Files' to create the missing Structure files.
  5. The data files for DMO and 1EX are now in large file format (FMS Type 9). Your installation has them flagged as FMS 1, and you will not be able to run those applications. To change the FMS type, log on on APPX and from the main APPX menu click on System Administration ->File Management -> Database Files. Enter DMO/DMO for the Database and Application, then click 'Change FMS'. Enter 9 as the new FMS type and uncheck the 'Convert Files' flag. The files are already in FMS 9 format and do not need to be converted. Click 'Proceed' to change the FMS type, and then repeat for 1EX/1EX.
 

Comments:

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback