User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
wiki:guides:admins:managing_easa_content [2016/08/15 10:02]
Brian Collins
wiki:guides:admins:managing_easa_content [2016/12/02 06:15] (current)
Brian Collins
Line 15: Line 15:
 ===== Configuring Clients in EASA ===== ===== Configuring Clients in EASA =====
  
-**Administrators** 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:+**Administrators** can determine which of the available client types in EASA are allowed to be used by users to open EASAPs. Currentlyin EASA there are two client types:
  
   * **EASA Client**   * **EASA Client**
Line 21: Line 21:
   * Web Browser   * 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, go to:+One or both of the clients can be made available to users. The default is to allow both client types. To adjust ​allowed ​clients per **User**, go to:
  
   * **EASA->​Administrator->​Configure->​Clients->​Allowed Clients**  ​   * **EASA->​Administrator->​Configure->​Clients->​Allowed Clients**  ​
Line 30: Line 30:
 ===== Copying Individual EASAPs Between EASA Installations ===== ===== Copying Individual EASAPs Between EASA Installations =====
  
-An **Author** ​has the ability to **export** an  EASAP to an **.easap** file+An **Author** ​may **export** an  EASAP to an **.easap** file
 and then **import** it into a different EASA installation. and then **import** it into a different EASA installation.
  
Line 41: Line 41:
 ===== Importing Content Between Older EASA Installations and EASA 5.3 ===== ===== Importing Content Between Older EASA Installations and EASA 5.3 =====
  
-EASA comes with a set of executable wizard tools that help you migrate ​your EASA **<​SERVERDATA>​** folder 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.+EASA comes with a set of executable wizard tools that help migrate ​an EASA **<​SERVERDATA>​** folder 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.
  
 ---- ----
Line 51: Line 51:
 ----- -----
  
-In the EASA 5.3 start menu group there are two tools called ​**Import Data and Settings (4.3.3)** ​and **Import Data and Settings (5.0)**.+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. 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, ​the **Import Data and Settings (4.3.3)** ​option should be used if moving data from EASA 4.3.3 or earlier version and the **Import Data and Settings (5.0)** ​option should be used to move data from EASA 5.0 or newer to EASA 5.3.+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.
-**Note:​** ​The Import Data and Settings Wizard is intended for use on a new EASA installation as it will delete any existing content. +
------+
  
 +----
 === EASA 4.3.3 or Older Source === === EASA 4.3.3 or Older Source ===
  
-Follow the instructions ​detailed in this paragraph ​if the source installation version is 4.3.3 or older.+Use these instructions if the source installation version is 4.3.3 or older.
  
-If you are copying between ​EASA installations on the same computer:+For two EASA installations on the same computer:
  
-  * Ensure ​that both the source and target ​EASA servers are stopped.+  ​* Stop both **EASA Servers** (this is absolutely mandatory!) 
 +  ​* Ensure both **EASA Servers** have stopped.
  
-If you are copying between ​EASA installations on different computers:+For two 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 suitable data transfer method such as an external hard drive, or over a network.+  *Copy the **<​EASAROOT>​** directory of the source installation from the source computer to the target computer ​(ftp over the network or use physical ​drive).
  
-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 4.3.3 or Older Versions.
- +
------ +
-**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 application:​ From the start menu on Windows, navigate to the application:​
-  * **EASA->​EASA X.X->​Import Data and Settings (4.3.3)** ( where X.X->​EASA version number) +  * **EASA->​EASA X.X->​Import Data and Settings (4.3.3)**  
-  *  Alternatively,​ navigate to the ''​<​EASAROOT>​'' ​folder of the target installation ​and run **Import433.exe**.+    ​* ( X.X->is EASA version number) 
 +  *  Alternatively,​ navigate to the **<​EASAROOT>​** folder of the target installation 
 +    * run **Import433.exe**
  
-  * Using the wizard ​prompts, navigate ​to and select the source installation folder ​then follow the instructions ​until the import wizard is finished.+  * At the wizard ​prompt: 
 +    *  Navigate ​to and select the source installation folder ​ 
 +    * Continue to follow the instructions
  
-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:+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:
  
 ^  Source: <​EASAROOT>​… ​ ^  Destination:​ <​SERVERDATA>​… ​ ^  Description ​ ^ ^  Source: <​EASAROOT>​… ​ ^  Destination:​ <​SERVERDATA>​… ​ ^  Description ​ ^
Line 92: Line 97:
 |**\admin\config**|**\easa\admin\config**|**.properties** files| |**\admin\config**|**\easa\admin\config**|**.properties** files|
  
-**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+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. ​   * Start the target EASA installation. ​
   * Log in and **EASA->​Set Mode->​Administrator**.   * Log in and **EASA->​Set Mode->​Administrator**.
Line 100: Line 105:
   * Click “Rebuild job database”.   * Click “Rebuild job database”.
  
-All of your EASA content should be imported and up to date for use with EASA.+All EASA content should be imported and up to date for use by the **EASA Server**.
  
 +----
 === EASA 5.0 or Newer Source === === EASA 5.0 or Newer Source ===