Difference: MovingAPPXFilesBetweenPlatforms (3 vs. 4)

Revision 42016-03-02 - JeanNeron

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

Moving APPX Applications and Data Between Platforms

The above title is not accurate, but it does represent a typical migration that these instructions are designed to describe. An accurate title would be "Moving APPX files between platforms of differing 'Endians'", but if you don't know what an Endian is, that's not very useful.

Line: 59 to 59
 7. Process your Data Dictionary, create your Enduser Datafiles, and go!

Applications - Method 3 - Consolidated Portdata File

Changed:
<
<
In Release 4.2.0 a Single File Design File import/export option was added. This creates a single file containing the entire application that can be moved to the target system. It does not require any special processing (i.e., appx -e or appx -i).
>
>
In Release 5.4.4 a Single File Design File import/export option was added. This option exists in versions prior to 5.4.4 but had various problems and should not be used in earlier versions.

This creates a single file containing the entire application that can be moved to the target system. It does not require any special processing (i.e., appx -e or appx -i).

  To use this option, follow this procedure:
Line: 77 to 79
  7. Process your Data Dictionary, create your Enduser Datafiles, and go!
Deleted:
<
<
NOTE: In all releases up to 5.4.3, this option will not transfer the AUDTHIST file. This file contains the audit history for the application. Your application will still run without this file, so it is optional. If you do want to transfer the audit information, transfer the file manually using either of the file by file approaches above.


 

Data - Method 1 - File by File (brf format)

This approach requires you to process the files when moving them between platforms. This works for all versions of APPX. Follow these steps:

Line: 90 to 89
  3. Convert your brf formatted exported data from Portdata format into ASCII format by running 'appx -e=<filename>' for every file in the Portdata directory.
Changed:
<
<
4. Move your ASCII-formatted export files (the ones without the '.dat' suffixes) to the target system in the $APPXPATH/<database>/<application>/Portdata folder. Create it if necessary. Be sure and use a binary, and not an ASCII type transfer.
>
>
4. Move your ASCII-formatted export files (the ones without the '.dat' suffixes) to the target system in the $APPXPATH/<database>/<application>/Portdata folder. Create it if necessary. Be sure and use a binary, and not an ASCII type transfer.
  5. If your $APPXPATH/<Database>/<Application>/Portdata contains any *.dat files, delete, move, or rename them.
 
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