At EASA > Author > Applications an Author may:

• Export an EASAP to an *.easap file
• Import it into another EASA Server

Author's Application Menu has greater detail.

1. Login as an Author or an Administrator
2. Navigate to: EASA > System > Backup
3. At 'EASA > System > Backup' click 'Rebuild user database' but do not click 'Yes' …yet
4. Copy the source <SERVERDATA>\easa\admin\config\usergroupconfig.ccl to the target <SERVERDATA>easa\admin\config\ folder
5. Copy the source <SERVERDATA>\easa\admin\config\userconfig.ccl to the target <SERVERDATA>easa\admin\config\ folder
6. Again back at 'EASA > System > Backup' click 'Rebuild user database' now click 'Yes'

The EASA installer does this automatically, simply use the location of the existing <SERVERDATA> folder when prompted in step B.5

From EASA 6.0 a MySQL local database is installed by default which the EASA Server depends on (we call this the 'EASA internal' database).

Many customers wish to run this database in dedicated machine and they may wish to run SQL Server instead of MySQL.

Additionally, in EASA 6.1 the schema was changed slightly.

For these reasons the upgrade steps (which includes automatic import of EASAP's) are very specialized.

• Choose the relevant steps
  Update from EASA 6.0 to EASA 6.1 with a local database
  Update from EASA 6.0 to EASA 6.1 with a remote database

Since EASA 5.3 the structure of <SERVERDATA>, the 'data folder' allows a new <EASAROOT> or 'installation folder' to be installed directly and to use the earlier <SERVERDATA> without loss of data.

To upgrade:

• <SERVERDATA> should be copied and saved locally as a backup.
• Leave the prior installation in place, EASA 6.0 will automatically detect <SERVERDATA>
• Download the installer for the target EASA version
• Run the installer
• When a <SERVERDATA> is detected from 5.3, 5.4, or 5.5 a window will ask if it should be used
• Click 'Yes'
• Installation will proceed
  The new EASA 6.0 installation version is compatible with and will utilize the older version's EASAP's, results, etc…
• Run the old installation's uninstaller to prevent conflict between the new EASA Tomcat service and the old one.

From EASA 6.0 a new installation will use a MySQL database by default.

EASA comes with a set of executable wizard tools that help migrate an EASA <SERVERDATA> folder to a new installation, these tools are distributed in EASA 5.5. The requirements to run each tool are identical to running the EASA installer itself with the additional condition that the new EASA installation has to be on the same machine and operating system as the previous source installation.

To upgrade from pre-EASA 5.3 to a more recent EASA version, download and install EASA 5.5 then run the import tool corresponding to the old EASA version. The import tool will bring <SERVERDATA> up to the folder structure introduced in EASA 5.3 which is compatible with later releases.

Simply backup <SERVERDATA> and install the more recent version on top of the original <SERVERDATA>; each EASAP, results files and folder and other files and data will be automatically accessible in the new install.

Version-specific details follow.

Warning: Using any of the Import Tools will automatically invalidate any existing licenses on the target installation. As a result, having the new license ready before using the tool is recommended.

In the EASA 5.3 start menu group there are two tools:

• Import Data and Settings (4.3.3)
• Import Data and Settings (5.0)

These tools can be used to copy contents from the <SERVERDATA> folder of an earlier EASA installation to a new EASA 5.3 installation.

The version number signifies the older version:

• Import Data and Settings (4.3.3) - move from EASA 4.3.3 or prior
• Import Data and Settings (5.0) - move data from EASA 5.0 through 5.3

The 'Import Data and Settings Wizard' is intended for use on a new EASA installation as it will delete any existing content.

Use these instructions if the source installation version is 4.3.3 or older.

For two EASA installations on the same computer:

• Stop both EASA Servers (this is absolutely mandatory!)
• Ensure both EASA Servers have stopped.

For two EASA installations on different computers:

• Copy the <EASAROOT> directory of the source installation from the source computer to the target computer
  (ftp over the network or use a physical drive)

If copying the entire EASA installation between computers is not a viable solution, you may choose to manually copy relevant content from EASA 4.3.3 or Older Versions, see Manual Import from EASA 4.3.3 or Older Versions.

To run, first navigate to the import wizard, either:

• From the Start menu find: EASA >EASA x.x > Import Data and Settings (4.3.3) (where x.x is EASA version number)
• Go to the <EASAROOT> folder of the target installation

Run Import433.exe.

At the wizard prompt:

• Navigate to and select the source installation folder
• Continue to follow the instructions

Optionally there may be 'custom code' files obtained from EASA Technical Services. Determine whether the old versions of the custom code files can be carried forward to the new installation or else new files will need to be delivered. Review the class names stored in the *.properties files. The following table details where these files are:

Do not overwrite the *.properties files above as this may replace important properties with defaults. Instead, compare, review, then merge the files line-by-line.

• Start the target EASA installation.
• Log in and click: EASA > Set Mode > Administrator
• Navigate to: EASA > System > Backup
• Click 'Rebuild job database'

All EASA content should be imported and up to date for use by the EASA Server.

Follow these instructions if the source installation version is 5.0 or newer,

1. If you are copying between installations on the same computer, ensure that both the source and target EASA Servers are stopped.
2. If you are copying between installations on different computers, ensure that the source EASA Server is stopped.
3. Copy the <EASAROOT> directory of the source installation from the source computer to the target computer using a suitable data transfer method such as an external hard drive, or over a network.

Ensure that the target EASA Server is stopped.

If copying the entire EASA installation between computers is not a viable solution, you may choose to manually copy relevant content using the instructions provided below at Manual Import from EASA 5.0 or Newer Versions.

To run, first navigate to the import wizard, either:

• From the Start menu find: EASA >EASA x.x > Import Data and Settings (5.0) (where x.x is EASA version number)
• Go to the <EASAROOT> folder of the target installation

Run Import433.exe:

• Using the wizard prompts,
• Navigate to and select the source installation folder and the source installation data folder
• Choose which content you would like to import out of: Results, Languages, Applications, Settings
• Finish the import wizard.

Optionally there are files related to custom codes. These are supplied by the EASA Technical Services team and should be reviewed whether the old versions of the custom code files can be carried forward to the new installation or new files are to be delivered. The class names stored in the *.properties files should also be reviewed accordingly. The following table details where these files are:

Warning: The .properties files above should not be copied over as important properties could be lost by overwriting the default files. Instead, they should be compared and reviewed to determine which lines should be merged into the new files.

Next, start the EASA service on the target machine, log in and switch to Administrator:

• Navigate to: EASA > System > Backup
• Click 'Rebuild job database'

All of EASA content should be imported and up to date for use with EASA.

Use of the 'Import Data and Settings Wizard' is recommended in most cases. However, in some cases (particularly under the advice of an EASA Support Representative), it may be necessary to take manual control of the migration process. If the new installation is on a different machine or operating system than the previous source installation or if the Import Tools cannot be used by any other reason, manual import is available. This method includes copying of the old files to the appropriate folders on the new installation folder structure and as a result you need access to both file systems (in case of different machines).

The table below will detail which files you need to copy from the source folder an where to put them in the new data folder. The <EASAROOT> designation refers to the EASA Installation Folder, while <SERVERDATA> refers to the EASA Server Data folder, both of which were specified at installation time.

Optionally there are files related to custom codes. These are supplied by the EASA Technical Services team and should be reviewed whether the old versions of the custom code files can be carried forward to the new installation or new files are to be delivered. The class names stored in the *.properties files should also be reviewed accordingly. The following table details where these files are:

Warning: The .properties files above should not be copied over as important properties could be lost by overwriting the default files. Instead, they should be compared and reviewed to determine which lines should be merged into the new files.

• In the new <SERVERDATA> folder, navigate to \easa\client and create a folder called 'custom' if not present already.
• Rename the old EASA <SERVERDATA> folder to indicate that it's a backup of the older version
  • Place the folder in a convenient folder for backup recovery.
• Configure the target EASA installation to use the <SERVERDATA> folder using the steps provided at Advanced Configuration of EASA.
• Once configured, start the target EASA installation and, in Administrator-mode, navigate to: EASA > System > Backup
• Click: Rebuild job database
  …This ensures that all Results data is imported correctly.

Tables depicting file system locations of content to be copied are provided below. These are the changes made with the: Import Data and Settings Wizard

Destination folders for Settings, Applications and Results must be emptied or deleted before old content is copied over. This is to say, data should not be merged.

The location of the EASA application files on the source installation will vary depending on version.

• For EASA 4.3, the folder path was: <EASAROOT>\webapps\easa
• For EASA versions 4.2 and earlier, the folder path was: <EASAROOT>\EASA

Substitute <EASAROOT> for the paths below.

• Settings

• Database Connections

• Applications

• Results

Whenever 'Results' data is copied over,

• Navigate to: EASA > System > Backup
• After restarting the service click: Rebuild job database

Optionally there are files related to custom codes. These are supplied by the EASA Technical Services team and should be reviewed whether the old versions of the custom code files can be carried forward to the new installation or new files are to be delivered. The class names stored in the *.properties files should also be reviewed accordingly. The following table details where these files are.

The *.properties files above should not be copied over as important properties could be lost by overwriting the default files. Instead, they should be compared and reviewed to determine which lines should be merged into the new files.

• In the new <SERVERDATA> folder,
  • Navigate to: \easa\client
  • If not present already, create a folder called: custom

Should you require further explanation or assistance with the manual folder migration process, please email support@easasoftware.com.