This section describes tasks involved in managing existing content on an EASA system, which may include any of the following tasks:

• Copy EASAP's Across EASA Versions
• Import content from EASA 5.3 or 5.4 or 5.5 to EASA 6.0
  • Optional: Use a non-default local internal database
  • Optional: Use a non-default remote internal database
• Import content from pre-EASA 5.3 versions
  • Using the import tools
  • Manual import

An Author may export an EASAP to an .easap file and then import it into a different or more recent EASA Server instance.

Go to:

• EASA→Author→Applications

See Author's Application Menu for more details.

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…
• Now run the old installation's uninstaller to prevent conflict between the new EASA Tomcat service and the old one.

In EASA 6.0 a new installation will use a MySQL database.

For a customer running their own local internal database on the same machine as the EASA Server:

• Delete <EASAROOT>\db
• Run a database script for the database vendor:
  • MySQL EASA script
  • SQL Server EASA script

To run a remote internal database, Postgres in this example, on a different machine to the EASA Server follow these steps.

1. Delete <EASAROOT>/db
2. Download the JDBC driver for Postgres
   • https://jdbc.postgresql.org/download.html
3. Save the driver in,
   • <EASAROOT>\tomcat\lib\
4. Modify one property in <SERVERDATA>\easa\admin\config\easa.cfg.xml
   • <property name=“hibernate.connection.url”>
     • jdbc:postgresql://machine_name_or_ip_address:port_number/easa?autoReconnect=true
   • </property>
   • For the external database machine substitute correct values for the strings below in the url above
     • machine_name_or_ip_address
     • port_number
   • In the same file set,
     • <property name=“hibernate.dialect”>org.hibernate.dialect.PostgreSQLDialect</property>
5. Update the hibernate.connection.url, machine_name_or_ip_address and port_number in both of the files below,
   • <SERVERDATA>\easa-share\admin\config\
     • excel.cfg.xml
       • <property name=“hibernate.connection.url”>
         • jdbc:postgresql://machine_name_or_ip_address:port_number;databaseName=excel;
       • </property>
     • excelTesting.cfg.xml
       • <property name=“hibernate.connection.url”>
         • jdbc:postgresql://machine_name_or_ip_address:port_number;databaseName=excelTesting;
       • </property>
6. Run a script to create users, password, schema and populate tables with data (a MySQL script is available for reference)
7. Rebuild 'jobs' database:
   • Start the target EASA installation.
   • Log in and EASA→Set Mode→Administrator.
   • Navigate to the EASA→System→Backup tab.
   • Click “Rebuild job database”.

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 an EASA <SERVERDATA> folder of an earlier EASA installation to a new EASA 5.3 installation.

The version number signifies the older version, thus:

• 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 using the instructions provided below at Manual Import from EASA 4.3.3 or Older Versions.

From the start menu on Windows, navigate to the application:

• EASA→EASA x.x→Import Data and Settings (4.3.3)
  • ( x.x→is EASA version number)
• Alternatively, navigate 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 EASA→Set Mode→Administrator.
• Navigate to the EASA→System→Backup tab.
• Click “Rebuild job database”.

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

Follow the instructions detailed in this paragraph if the source installation version is 5.0 or newer.

• If you are copying between EASA installations on the same computer:
  • Ensure that both the source and target EASA Servers are stopped.
• If you are copying between EASA installations on different computers:
  • Ensure that the source EASA Server is stopped.
  • 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.

• From the start menu on Windows,
  • Navigate to the EASA→EASA X.X→Import Data and Settings (5.0) application, (where X.X →EASA version number).
  • Alternatively, run Import50.exe from <EASAROOT> of the target installation.

• 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.

Once the file operations are done, carry on following these steps:

• 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 the
  • 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. They represent the same processes used by the Import Data and Settings Wizard.

Note: 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
• Click 'Rebuild job database' after restarting the service.

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
• Create a folder called custom if not present already.

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