Difference: APPX610UpgradeInstallation (29 vs. 30)

Revision 302022-10-28 - BrianRyan

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

APPX 6.1 Upgrade Instructions

>
>

APPX 6.1 (and greater) Upgrade Instructions

 
Changed:
<
<		This page provides the information needed to upgrade an existing APPX 5.4.5 (or higher) installation to APPX 6.1
>
>		This page provides the information needed to upgrade an existing APPX 5.4.5 (or higher) installation to APPX 6.1 and 6.2
 

Overview

Changed:
<
<		Release 6.1 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 (5.5.1 is recommended).
>
>		Release 6.1 (and greater) 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 (5.5.1 is recommended).
  This application requires Release 5.4.5 or higher (5.5.1 is recommended), 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.1.
Line: 16 to 16
 The Structure files are incompatible between 6.x and all previous releases. After installing 6.1 and migrating your applications, you will have to create new Struct files for all end user data files. This also means you cannot share the APPXIO files between Release 5 & 6. Files that are stored in an RDBMS can be shared if you choose, although this is not recommended.

The basic approach we will use for upgrading is:

Changed:
<
<
  1. Install APPX 6.1 in a new folder as if it was a new installation
>
>
  1. Install APPX 6.1 (and greater) in a new folder as if it was a new installation
 
  1. Install the migration applications in your existing 5.4.x or 5.5.x installation
  2. Run the migration utility for your System Administration files
  3. Install the migrated System Admin files in your new 6.1 installation & confirm all is well
  4. Run the migration utility for your applications
  5. Install the migrated applications
  6. Convert 0DX data files (optional)
Changed:
<
<
  1. Copy the end user data to Release 6.1
>
>
  1. Copy the end user data to Release 6.1 (and greater)
 
  1. Make any required changes to your applications
Changed:
<
<		This approach allows you to maintain your existing 5.x installation while migrating/installing Release 6.1. You can test Release 6.1 independently of your existing 5.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.1 (and greater). You can test Release 6.1 (and greater) independently of your existing 5.x installation. When you are ready to switch you just need to refresh the end user data.
  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. If you are comfortable with APPX in character mode, we recommend using character mode to run the migration utility for faster conversion.

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.

Changed:
<
<

1. Install APPX 6.1 in a new folder

>
>

1. Install APPX 6.1 (and greater) in a new folder

  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

Line: 63 to 63
 The conversion step creates a new set of System Administration files in Release 6.1 format. These are located in $APPXPATH/6SA/6SA/Data.

Enable any hook record (in your 5.x release) you disabled during this process.

Changed:
<
<

4. Install the migrated System Admin files in your new 6.1 installation

>
>

4. Install the migrated System Admin files in your new 6.1 (and greater) installation

  You are now ready to install the new System Administration files in your Release 6.1 folder. Follow these steps:
  1. Make sure no Release 6.1 APPX sessions are running. In particular, make sure to terminate the License Server if it's running.
Line: 82 to 82
 
  1. If your operating system does not have en_US.utf8 locale or you are using a different locale by overriding LANG environment variable, you must recreate the key files for DICTNARY and TOKEN files for all your applications. To do that, go to System Administration -> Database/Applications -> Design File Management -> Leave the application blank and set the version to 00 then go to "File Selection". Select all Token files by clicking on "Select" and setting the file name to "TOKEN" (To select all TOKEN files from all applications under version 00, only fill in the file name). Go back and click on "Rebuild Key Files". Do this for "DICTNARY" as well.
Log on to APPX 6.1, 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.1
Changed:
<
<		Finally, compare your Release 5.x 'appx.env' file to your Release 6.1 'appx.env' file, and add any necessary settings to the Release 6.1 version. Do not simply copy your Release 5.x file to 6.1, as you will lose some Release 6.1 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.1 (and greater) 'appx.env' file, and add any necessary settings to the Release 6.1 (and greater) version. Do not simply copy your Release 5.x file to 6.1 (and greater), as you will lose some Release 6.1 (and greater) 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
  It is not necessary to convert all your applications at once. For example, if you have a test version and a test database, you may want to just migrate those initially.
Changed:
<
<		When this step completes, you can proceed to installing the migrated applications in Release 6.1.
>
>		When this step completes, you can proceed to installing the migrated applications in Release 6.1 (and greater).
 

6. Install the migrated applications

To install the migrated applications, simply copy the folder(s) from the 'ConversionResults' path to $APPXPATH in Release 6.1.

Line: 143 to 143
 3. Enter the path to 3 0DX exported CSV files which you created on step 1, and the database you want to import the data under and click on the "Continue" button.

You will get a report that summarizes the conversion.

Changed:
<
<

8. Copy the end user data to Release 6.1

>
>

8. Copy the end user data to Release 6.1 (and greater)

 
Changed:
<
<		Next, we must copy the end user data to our Release 6.1 installation. As mentioned previously, the Structure files are completely different between Release 5.x and Release 6.1, so we must create new Structure files in Release 6.1.
>
>		Next, we must copy the end user data to our Release 6.1 (and greater) installation. As mentioned previously, the Structure files are completely different between Release 5.x and Release 6.1 (and greater), so we must create new Structure files in Release 6.1.
  Make sure to exclude 0DX data files from this step since they are already converted in previous step.
Changed:
<
<		FMS Type 9 files (APPX large file format) have changed on release 6.1. If you are using FMS Type 9 in your APPX 5.x version, you need to export them under release 5.x and then import them to APPX release 6.x.
>
>		FMS Type 9 files (APPX large file format) have changed on release 6.1 (and greater). If you are using FMS Type 9 in your APPX 5.x version, you need to export them under release 5.x and then import them to APPX release 6.x.
 
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.1 FMS group to point to a different location, otherwise Release 5.x & Release 6.1 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.1 (and greater) FMS group to point to a different location, otherwise Release 5.x & Release 6.1 will be accessing the same Structure files and that will not work.
 
Changed:
<
<		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.1 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.
>
>		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.1 (and greater) 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.
  Do not copy the 'Struct' folders, or alternatively, delete them after copying. For example, to copy database '123', we would copy all the files in R:\appx\data\123 to R:\appx600\data\123. After the copy is complete, we would delete all the Struct folders in R:\appx600\data\123.
View topic | History: r34 < r33 < r32 < r31 | 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