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: support@easasoftware.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.

• remote EASAP/Excel Server - Many customers with significant Excel requirements choose to combine 'MS Excel Server Support' in an EASAP Server (complicated spreadsheets or high user load may require multiple EASAP/Excel Servers)

• remote Compute Server - Engineering simulations running a third party software like Matlab or CAD require only the Compute Server component.

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

• Go to 'Task Manager > Services > Open Services'
• Right-click 'EASA Tomcat8' select 'Properties'
• Click the 'Log On' tab
• Enter credentials for the local user ('EASA-user' in our example below)
• Click 'OK'

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:

• mysql.exe -u root -p
• mysql> create user 'remoteroot'@'%' identified by 'remotepass';
• mysql> grant all privileges on *.* to 'remoteroot'@'%' identified by 'remotepass';

2. Download the following file to a local folder:

• https://help.myeasa.com/resource/config.txt

3. Modify the configuration parameters as needed:

• DB_TYPE → the database type (default: mysql, mssql, postgres)
• DB_HOST → database hostname
• DB_PORT → port number
• DB_USER → database superuser
• DB_PASS → superuser password

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 support@easasoftware.com for troubleshooting advice.

We need to configure EASA machines to connect to the 'signer' database

1. On the EASA Server machine,

• edit <SERVERDATA>\easa-share\admin\config\signer.cfg.xml
• configure the following properties (for reference look in the other *.cfg.xml files in the same folder)
• hibernate.connection.username with the actual username
• hibernate.connection.password with the actual password
• hibernate.dialect with the correct path,
  • org.hibernate.dialect.MySQLDialect
  • org.hibernate.dialect.SQLServerDialect
  • org.hibernate.dialect.PostgreSQLDialect
• hibernate.connection.url with the actual IP address, port number, and database name in the required format,
  • jdbc:mysql://localhost:3306/db-name?autoReconnect=true
  • jdbc:sqlserver://localhost:1433;DatabaseName=db-name
  • jdbc:postgresql://localhost:5432/db-name

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'