Difference: APPX610UpgradeInstallation (24 vs. 25)

Revision 252021-08-23 - MisaghKarimi

Line: 1 to 1

META TOPICPARENT	name="Main.Appx600Installation"

APPX 6.1 Upgrade Instructions

Line: 22 to 22

Install the migrated System Admin files in your new 6.1 installation & confirm all is well
Run the migration utility for your applications
Install the migrated applications

Added:

>
>

Convert 0DX data files (optional)

Copy the end user data to Release 6.1
Make any required changes to your applications

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.

Line: 106 to 107

When you are ready to proceed, click the 'Process' button.

Added:

>
> The conversion utility does some preliminary checks on your applications and tries to detect ILF statements that may be incompatible with release 6.x of APPX. You can either fix those issues in APPX 5.x and run the conversion again, or you can fix them in release 6.x of APPX after the conversion has been done.

The applications will be processed and a report produced showing the applications and files that were processed. Check the report for any error messages. Note that not every application uses all possible design files, so the 'FI_STRUCT_NOT_FOUND' message is not necessarily an error.

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.

Line: 120 to 123

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.

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.

Changed:

<
<

7. Copy the end user data to Release 6.1

>
>

7. Convert 0DX Data Files (Optional)

If your application uses 0DX map definitions, you need to convert those to release 6.x format. If you don't use 0DX or you don't have any map definitions in 0DX application, you can skip this step. A quick way to find out if your application has any map definitions is to verify the 0DX files under all databases (by leaving the database blank). If you see any of the 0DX files have any records in them, you need to do this step.

To convert your map definitions, you need to follow the following steps:

1. Export your 0DX files under release 5.x of APPX in CSV format. You have to do this for each database that has map definitions.

2. Run 0DX-00 CONVERT 5.X DATA FILES job. Leave the database blank.

3. Enter the path to 3 0DX exported CSV files, and the database you want to import the data under and click on "Continue" button.

You will get a report that summarizes the conversion.

8. Copy the end user data to Release 6.1

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.

Added:

>
> Make sure to exclude 0DX data files from this step since they are already converted in previous step.

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.

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.

Line: 139 to 160

Enable any hook record (in your 6.1 release) you disabled during System Admin file migration.

Once this step is complete, you should be able to run your applications under Release 6.1, subject to the application issues in the next section.

Changed:

<
<

8. Make any required changes to your applications

>
>

9. Make any required changes to your applications

There are some differences in Release 6 that may have an impact on your applications.

Line: 187 to 208

9. Regular Expression library has changed to support Unicode characters. The new library doesn't like blank or unescaped patterns. You will get a run-time error if it doesn't like the pattern.

10. As the result of the fix for bugs #799, #2498, and #4792, the way APPX finds a subroutine called by a GOSUB statement has changed. If you received "Duplicate Label" or "Could Not Compile GOSUB" error during em creation, it is because you called a subroutine without specifying an application id or called an internal subroutine (a subroutine within another subroutine) with an application id. We recommend making changes to your application to fix these errors, however, you can set APPX_USE_PRE_61_GOSUB environment variable to revert back to old behavior.

Added:

>
> 11. 0DX RAWXML, RAWXMLAT, and XELEMENT file structures have been changed to support Unicode characters. All Attribute Names, Element Names, and Values have been converted to Unicode fields.

Comments:

Read what other users have said about this page or add your own comments.

View topic | History: r34 < r33 < r32 < r31 | More topic actions...