This section describes tasks involved in managing the content on your EASA system, which include:

• Configuring Clients available to users

• Copying EASAPs between EASA Installations

• Updating EASAPs

• Copying other EASA content between EASA Servers

Administrators of EASA can determine which of the available client types in EASA are allowed to be used by users to open EASAPs. Currently in EASA there are two client types:

• EASA Client

• Web Browser

One or both of the clients can be made available to users. The default is to allow both client types. To select which clients users are allowed to access, select Clients under the Configure tab in Administrator mode to be taken to the Allowed Clients page. On this page, simply check the boxes next to the clients to be allowed and click on the Apply button.

The ability to export an EASAP and then import it into a different EASA installation is available in Author mode under the Applications tab (See Author's Application Menu for more details).

EASA comes with a set of executable wizard tools that help you migrate your EASA Server Data folders to a new installation. 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.

Note: 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.4 start menu group there are two tools called Import Data and Settings (4.3.3) and Import Data and Settings (5.0).

These tools can be used to copy contents from an EASA Server Data folder of an earlier EASA installation to a new EASA 5.4 installation.

The version number signifies the older version, the Import Data and Settings (4.3.3) option should be used if moving data from EASA 4.3.3 or earlier version, the Import Data and Settings (5.0) option should be used to move data from EASA 5.0, 5.1 or 5.2 and the Import Data and Settings (5.3) option should be used to move data from EASA 5.3 to EASA 5.3.

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

Follow the instructions detailed in this paragraph if the source installation version is 4.3.3 or older.

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, and then 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.

Note: 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 EASA → EASA X.X → Import Data and Settings (4.3.3) application, where X.X represents your EASA version number. Alternatively, navigate to the <EASAROOT> folder of the target installation and run the Import433.exe application.

• Using the wizard prompts, navigate to and select the source installation folder then follow the instructions until the import wizard is finished.

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:

Note: 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.

• Start the target EASA installation. Log in and switch to Administrator mode.

• Navigate to the System > Backup tab and click “Rebuild job database”.

• By now, all of your EASA content should be imported and up to date for use with EASA.

Follow the instructions detailed in this paragraph if the source installation version is 5.0, 5.1 or 5.2.

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, and then 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.

Note: 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 versions 5.0, 5.2 and between.

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

• Using the wizard prompts, navigate to and select the source installation folder and the source installation data folder, then 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:

Note: 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 mode.

• Navigate to the System > Backup tab and click “Rebuild job database”.

• By now, all of your EASA content should be imported and up to date for use with EASA.

Follow the instructions detailed in this paragraph if the source installation version is 5.3.

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, and then 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.

Note: 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 represents your EASA version number. Alternatively, navigate to the <EASAROOT> folder of the target installation and run the Import53.exe application.

• Using the wizard prompts, navigate to and select the source installation folder and the source installation data folder, then 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:

Note: 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 mode.

• Navigate to the System > Backup tab and click “Rebuild job database”.

• By now, all of your 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).

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 as follows:

 <EASAROOT>\webapps\easa

For EASA versions 4.2 and earlier, the folder path was as follows:

 <EASAROOT>\EASA

In the tables that follow, you will need to substitute <EASAFOLDER> with these paths.

• Settings

• Database Connections

• Applications

• Results

Note: If results data is copied over, navigate to EASA→Administrator→System→Backup and 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:

Note: 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, in the new <SERVERDATA> folder, navigate to \easa\client and create a folder called “custom” if not present already.

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 <EASAFOLDER> 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:

Note: 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:

1. In the new <SERVERDATA> folder, navigate to \easa\client and create a folder called “custom” if not present already.
2. Rename the old EASA Server Data folder to indicate that it's a backup of the older version and place it in a convenient folder for backup purposes.
   
   
3. Configure the target EASA installation to use the <SERVERDATA> folder using the steps provided at Advanced Configuration of EASA.
   
   
4. Once configured, start the target EASA installation and, in Administrator mode, navigate to the System → Backup tab. Click “Rebuild job database”. This last step ensures that all Results data is imported correctly.

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 <EASAFOLDER> designation refers to the EASA Installation Folder, while <SERVERDATA> refers to the EASA Server Data folder, both of which were specified at installation time. These folders exist for both 5.3 and 5.4 versions of EASA.

For safekeeping purposes, the following files should be kept from the source installation folder as backups:

Delete the following folders as a preparation to migrate the old files to the new folder structure:

If you choose to migrate the old applications folder (where all published / unpublished EASAPs are) you will need to delete the new one first:

The following table shows path by path where to move source files from 5.3 inside EASA 5.4:

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:

Note: 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:

1. In the new <SERVERDATA> folder, navigate to \easa\client and create a folder called “custom” if not present already.
2. Rename the old EASA Server Data folder to indicate that it's a backup of the older version and place it in a convenient folder for backup purposes.
   
   
3. Configure the target EASA installation to use the <SERVERDATA> folder using the steps provided at Advanced Configuration of EASA.
   
   
4. Once configured, start the target EASA installation and, in Administrator mode, navigate to the System → Backup tab. Click “Rebuild job database”. This last step ensures that all Results data is imported correctly.

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