These steps apply to an EASA Server with remote internal database (MySQL, SQL Server, or Postgres).
An EASA Server which utilizes a local internal EASA database will instead need to follow
Update from EASA 6.0 to EASA 6.1 with a local database
1. Contact us for link to download the EASA installer for Windows: firstname.lastname@example.org, then download it.
2. Stop the EASA 6.0 service if it is running.
By default, the EASA Server will run in plain http-mode, we may enable and configure https-mode later on.
1. Run the EASA installer *.exe file on the machine designated to be the EASA Server.
2. Select a new folder for <EASAROOT>.
3. Select which components should be installed on the EASA Server, first. We will adjust which components are selected when we run the installer on any other machines for an EASA cluster. Some common configurations are shown and described.
4. When you see “Default database files could not be found. Would you like the installer to download them now?” Click No.
5. Click 'Ignore' on the popup that states 'EASA requires a connection to an external database'.
6. At the final screen untick 'Start EASA Server now?' as we first have to modify the account Excel uses (next step) and configure the remote database ( part D. below).
7. By default the EASA Server will run as SYSTEM which will cause problems if 'MS Excel Server Support' was installed. Here we configure the EASA Tomcat service to run as a local Windows user with administrator privileges (for further background and detail read Configure EASA service to run as a non-SYSTEM user).
Now we run through many of the same steps in A. and B. for every remote EASAP Server, remote Excel Server, remote Compute Server, remote Web Service Server and any machine which combines these server roles.
1.Contact us for link to download the EASA installer for Windows: email@example.com, then download it.
2. Stop the 'EASA Tomcat' service.
3. Run the EASA installer *.exe file on the target machine.
4. Select a new folder for <EASAROOT>
5. Select which components should be installed on the target machine. Two common configurations are shown and described.
6. A window will prompt for a URL for the EASA Server, enter a URL using a hostname, static IP address, or common name if HTTPS will be or has already been configured. (ie. https://easa-server1/easa )
7. A window may prompt for an URL for an EASAP Server (historically JSF Server), enter an URL using a hostname, static IP address, or common name if HTTPS will be or has already been configured. (ie. https://easap-server1/jsf-easa )
8. If 'MS Excel Server Support' was installed, configure the 'EASA Tomcat' service to run as a local Windows user with administrator privileges (for further background and detail read Configure EASA service to run as a non-SYSTEM user).
We need to update the database schema to 6.1 and insert all the data from 6.0
A database administrator may do this part manually utilizing a SQL script for the new schema (outlined in Setup a new EASA 6.1 installation to use a remote database, the SQL script is in step 4) and migrating data. As the DBA must take care to backup the data and copy it back into the new schema, this detailed expertise is beyond the scope of this document.
Instead we provide, in the steps below, an automated database tool to achieve the migration, and outline how to use it if the remote database is MySQL and is accessed via its command line client. For Postgres or SQL Server the steps are very similar.
1. On the remote database machine, establish a 'remoteroot' user with 'all privileges'.
In MySQL this looks like:
2. Download the following file to a local folder:
3. Modify the configuration parameters as needed:
4. Download to the same folder the 'EASA database helper', https://help.myeasa.com/resource/edh.exe
5. Launch the *.exe and select the relevant upgrade path. Click 'Y' to confirm the choices in 'config.txt' are correct.
6. If the migration is not successful, contact firstname.lastname@example.org for troubleshooting advice.
We need to configure EASA machines to connect to the 'signer' database
1. On the EASA Server machine,
Below is an example of a portion of the modified 'signer.cfg.xml' config file with a MySQL database.
<property name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property> <property name="hibernate.connection.url">jdbc:mysql://192.168.12.56:3306/signer?autoReconnect=true</property> <property name="hibernate.connection.username">user</property> <property name="hibernate.connection.password">password</property> <property name="hibernate.dialect">org.hibernate.dialect.MySQLDialect</property>
2. Start the 'EASA Tomcat8' service.
Login as 'admin' and run a test query for each database from 'EASA > Configure > Databases > Configure Databases > Query tester'