Difference: APPX610UpgradeInstallation (27 vs. 28)

Revision 282021-10-04 - MisaghKarimi

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

APPX 6.1 Upgrade Instructions

Line: 78 to 78
 
    • SECDEPT.key
    • SECROLE.key
    • SECWG.key
Added:
>
>

  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

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.

Line: 122 to 124
  The migration tool does not create the structure files or process the Data Dictionary. This must be done in Release 6.1 for every application.
Added:
>
>
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 file 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 your application's version then go to File Selection. Select all Token files by clicking on "Select" and just setting the file name to "TOKEN". Go back and click on "Rebuild Key Files". Do this for "DICTNARY" file as well. Repeat this for all versions of your applications.
 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. Convert 0DX Data Files (Optional)

 
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