These steps apply to an EASA Server with local internal MySQL database (the default installation).
An EASA Server which utilizes a remote internal EASA database will need to follow:
Update from EASA 6.0 to EASA 6.1 with a remote database
As the schema has changed slightly between EASA 6.0 and EASA 6.1
1. Contact us for link to download the EASA installer for Windows: support@easasoftware.com, then download it.
2. Download MySQL below, the default EASA with an internal database (or alternatively stop and follow these steps for a remote database).
Save this file into the same folder as the EASA installer.
3. Check there is enough disk space.
4. 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. For each subsequent machine in an EASA cluster we will adjust which components are selected at this stage of installation. Some common configurations are shown and described.
4. At the final screen untick 'Start EASA Server now?' as we have a configuration step to do first.
5. 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).
6. In 'Task Manager > Processes > Background Processes' confirm mysqld.exe is running, note its process ID, or PID.
In 'Task Manager > Services' confirm Tomcat8 service is running, note its process ID, or PID.
If 'MS Excel Support' was included, confirm there are EXCEL.exe or 'Microsoft Excel' background processes
7. Confirm a mysqld.exe background process and 'EASA Tomcat8' service are listening on the expected ports.
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 a 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 has been or will be 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).
9. For an EASAP Server manually copy the following properties from one file to another.
10. For an Excel Server manually set the following property in two files.
11. Login and certify that the example EASAP's ('Mortgage Calculator', 'Cantilever Plate' and 'Stock Screener') run correctly.
1. Stop the 'EASA Tomcat' service.
2. Make a backup copy of <EASAROOT>\tomcat\conf\server.xml and <EASAROOT>\tomcat\conf\easastore.jks
3. Update server.xml
4. Start the 'EASA Tomcat' service.
Two main changes:
Re-branding possibilities include:
.bannerBackground>tbody>tr:nth-child(1)>td>table>tbody>tr:nth-child(1)>td:first-child img{height:50px;} .bannerBackground>tbody>tr:nth-child(1)>td>table>tbody>tr:nth-child(2)>td.tabOffleft:first-child, .bannerBackground>tbody>tr:nth-child(1)>td>table>tbody>tr:nth-child(2)>td.tabOnleft:first-child{padding-left:25px;} .bannerBackground>tbody>tr:nth-child(1)>td>table>tbody>tr:nth-child(2)>td.tabOn, .bannerBackground>tbody>tr:nth-child(1)>td>table>tbody>tr:nth-child(2)>td.tabOffmid{padding:10px 20px;border-top-left-radius:5px;border-top-right-radius:5px;} .bannerBackground>tbody>tr:nth-child(2) td.tabOn, .bannerBackground>tbody>tr:nth-child(2) td.tabOffmid{padding:10px 20px;border-radius:0px;} .bannerBackground>tbody>tr:nth-child(2) td:first-child{padding-left:20px;} .bannerBackground>tbody>tr:nth-child(2)>td.tabOn .subSides{display:none;} .bannerBackground>tbody>tr:nth-child(2)>td.tabOn>table>tbody>tr:last-child{visibility:hidden} .bannerBackground>tbody>tr:nth-child(2)>td.tabOn>table{height:20px;}