Difference: APPX600UpgradeInstallation (12 vs. 13)

Revision 132020-11-16 - MisaghKarimi

Line: 1 to 1
 
META TOPICPARENT name="Main.Appx600Installation"

APPX 6.0 Upgrade Instructions

Line: 7 to 7
 

Overview

Changed:
<
<		Release 6.0 has significant changes to the format & content of the System Administration files and Application Design files. As a result, these files must be migrated to the new format. A migration utility for the System Admin (6SA) and Application Design (6AD) is provided. This should be installed in your Release 5.4.x installation.
>
>		Release 6.0 has significant changes to the format & content of the System Administration files and Application Design files. As a result, these files must be migrated to the new format. A migration utility for the System Admin (6SA) and Application Design (6AD) is provided. This should be installed in your Release 5.4.x or 5.5.x installation.
  This application requires Release 5.4.5 or higher, it will not run on earlier releases. Also note that Locked applications cannot be migrated, they must be unlocked, migrated and then re-locked in 6.0.
Line: 15 to 15
  The basic approach we will use for upgrading is:
  1. Install APPX 6.0 in a new folder as if it was a new installation
Changed:
<
<
  1. Install the migration applications in your existing 5.4.x installation
>
>
  1. Install the migration applications in your existing 5.4.x or 5.5.x installation
 
  1. Run the migration utility for your System Administration files
  2. Install the migrated System Admin files in your new 6.0 installation & confirm all is well
  3. Run the migration utility for your applications
  4. Install the migrated applications
  5. Copy the end user data to Release 6.0
  6. Make any required changes to your applications
Changed:
<
<		This approach allows you to maintain your existing 5.4.x installation while migrating/installing Release 6.0. You can test Release 6.0 independently of your existing 5.4.x installation. When you are ready to switch you just need to refresh the end user data.
>
>		This approach allows you to maintain your existing 5.x installation while migrating/installing Release 6.0. You can test Release 6.0 independently of your existing 5.x installation. When you are ready to switch you just need to refresh the end user data.
 
Changed:
<
<		The entire process may take a few hours, depending on the amount of data involved. Users can continue to work with your Release 5.4.x applications and data while you are migrating, subject to the usual requirement of not copying files that others are actively updating.
>
>		The entire process may take a few hours, depending on the amount of data involved. Users can continue to work with your Release 5.x applications and data while you are migrating, subject to the usual requirement of not copying files that others are actively updating.
  It is assumed the reader is familiar with APPX System Administration concepts and knows how to define new applications, new databases, etc. It is also assumed the reader knows how to copy files, set/check permissions, etc.

This release has increased memory requirements, and performance in some areas is slow. We are aware of these issues, and they will be addressed in the next patch release.

1. Install APPX 6.0 in a new folder

Changed:
<
<		Install a fresh copy of APPX in a new folder on your server. Refer to APPX600LinuxNewInstallation for Linux/Unix servers and APPX600WindowsNewInstallation for Windows servers. If you are using APPX_MONITOR_KEY, this must be set to a different value than your 5.4.x installation.

2. Install the Migration Applications in Release 5.4.x

>
>		Install a fresh copy of APPX in a new folder on your server. Refer to APPX600LinuxNewInstallation for Linux/Unix servers and APPX600WindowsNewInstallation for Windows servers. If you are using APPX_MONITOR_KEY, this must be set to a different value than your 5.x installation.

2. Install the Migration Applications in Release 5.x

  There are 2 migration applications: 6SA for the System Administration files, and 6AD for Application Design files. Download the Migration Utility and follow these steps:
  1. Add application 6SA/00 to your Applications file.
Line: 64 to 64
  You are now ready to install the new System Administration files in your Release 6.0 folder. Follow these steps:
  1. Make sure no Release 6.0 APPX sessions are running. In particular, make sure to terminate the License Server if it's running.
Changed:
<
<
  1. Copy $APPXPATH/6SA/6SA/Data/* from your 5.4.x folder to $APPXPATH/0SA/Data in your 6.0 folder. Do NOT copy the Struct folder.
>
>
  1. Copy $APPXPATH/6SA/6SA/Data/* from your 5.x folder to $APPXPATH/0SA/Data in your 6.0 folder. Do NOT copy the Struct folder.
 
  1. Check permissions of $APPXPATH/0SA/Data in your Release 6.0 installation to make sure APPX users have read/write access.
  2. Delete these specific .key files in $APPXPATH/0SA/Data:
    • EDITMSG.key
Line: 75 to 75
 
    • SECDEPT.key
    • SECROLE.key
    • SECWG.key
Changed:
<
<		Log on to APPX, go to System Administration -> System Setup -> System Administration File Management and run 'Create Files'. This will create new .key files for the ones you just deleted. This is necessary because the keys in those files contain Unicode fields. Release 5.4.x cannot create a Unicode aware key file, so we must recreate it under 6.0
>
>		Log on to APPX, go to System Administration -> System Setup -> System Administration File Management and run 'Create Files'. This will create new .key files for the ones you just deleted. This is necessary because the keys in those files contain Unicode fields. Release 5.x cannot create a Unicode aware key file, so we must recreate it under 6.0
 
Changed:
<
<		Finally, compare your Release 5.4.x 'appx.env' file to your Release 6.0 'appx.env' file, and add any necessary settings to the Release 6.0 version. Do not simply copy your Release 5.4.x file to 6.0, as you will lose some Release 6.0 settings. This is a good time to review these settings to see if they are still required. If you are not sure what a setting is used for, use the Environment Variable Wizard to check it.
>
>		Finally, compare your Release 5.x 'appx.env' file to your Release 6.0 'appx.env' file, and add any necessary settings to the Release 6.0 version. Do not simply copy your Release 5.x file to 6.0, as you will lose some Release 6.0 settings. This is a good time to review these settings to see if they are still required. If you are not sure what a setting is used for, use the Environment Variable Wizard to check it.
  If you changed your 'appx.env' file, log off & on again. Check your System Administration files to make sure everything was migrated correctly, i.e., Users, Printers, Forms, Applications, Databases, etc.
Line: 115 to 115
  For example, let's assume our conversion results path was R:\appx\data\ConversionResults. We converted 2 applications, both in version GA. The migrated applications will be in R:\appx\data\ConversionResults\GA. Our Release 6 version is installed in R:\appx600new\, so I would copy (or move) the 'GA' folder to 'R:\appx600new\data'. If I converted more than one version at a time, there would be multiple folders in the conversion results folder, and they would all be copied/moved to $APPXPATH in Release 6.0.
Changed:
<
<		The migration tool does not copy Resources. If you are using any, you must manually copy the Resource folder from the Release 5.4.x location to the Release 6.0 location.
>
>		The migration tool does not copy Resources. If you are using any, you must manually copy the Resource folder from the Release 5.x location to the Release 6.0 location.
  The migration tool does not create the structure files or process the Data Dictionary. This must be done in Release 6.0 for every application.

The easiest way to do this is to go to 'Applications' in System Administration and select the first migrated application. Then choose 'Design File Management', and from there, run 'Create Files', then 'Process Data Dictionary'. Repeat this for each migrated application.

7. Copy the end user data to Release 6.0

Changed:
<
<		Next, we must copy the end user data to our Release 6.0 installation. As mentioned previously, the Structure files are completely different between Release 5.4.x and Release 6.0, so we must create new Structure files in Release 6.0.
>
>		Next, we must copy the end user data to our Release 6.0 installation. As mentioned previously, the Structure files are completely different between Release 5.x and Release 6.0, so we must create new Structure files in Release 6.0.
 
Changed:
<
<		If you are using an FMS group to redirect APPXIO files from their standard location, then you will have to change the Release 6.0 FMS group to point to a different location, otherwise Release 5.4.x & Release 6.0 will be accessing the same Structure files and that will not work.
>
>		If you are using an FMS group to redirect APPXIO files from their standard location, then you will have to change the Release 6.0 FMS group to point to a different location, otherwise Release 5.x & Release 6.0 will be accessing the same Structure files and that will not work.
  If you are using an FMS group to point to an RDBMS it will technically work, since each release of APPX has its own Structure files but this is not recommended. Instead, change the FMS group in Release 6.0 so that its files are unique. For example, you could add a prefix to the table naming scheme and then use the RDBMS utilities to copy the existing data to the new naming scheme.
View topic | History: r18 < r17 < r16 < r15 | More topic actions...
 
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