Installing EEE Service Packs
From EnablerWiki
Created: 27 January 2009. Last Reviewed: 27 May 2011
Installing EEE Service Packs
Contents |
Introduction
Magenta Retail periodically releases EEE Service Packs, which are primarily used to install fixes, but can also be used to install new functionality. Each service pack contains a document listing all the changes made in this release of EEE and all service packs including the current service pack.
All service packs are cumulative, so you only need to install the latest service release for a EEE version.
File Location
As a standard we always recommend that service packs (or service releases) should be copied to a specified location on your EEE server (or both servers if you have a multiple server configuration).
The recommended location is a subdirectory of EEE called Upgrades. Under this folder, would be a sub folder for each EEE version that has been installed on your server, and each of those versions will have a postinstall folder. Service release files should be copied to this folder as shown below in Figure 1 where SR-06 is the latest service release for EEE 1.40.
Figure 1
Installing a EEE service pack
The following screen shows the EEE Service Pack installation program. This screen is invoked from running EEEPatch.exe which is located in the root level of the service release pack. The fields in the EEE Patch screen are explained below.
Figure 2
- EEE SQL Server – Use the scroll arrow to select the EEE Server. If EEE is installed in a SQL Server instance, ensure that the instance name is selected. If you are unable to select the SQL Server from the drop down box, type the server name in the field on the right and click on the Refresh button next to the EEE Database field to refresh the list of available databases.
- EEE Database – Use the scroll arrow to select the EEE database that you are going to patch. When the database is selected, the Reporting Services URL and EEE Reports Folder fields will be automatically populated with data from the selected database.
- EEE Web Server directory – Enter the location of the web server directory. This will normally be C:\Inetpub\wwwroot\EEE.
- EEE URL – Enter the URL for the EEE Server. This is the URL normally used to run the EEE Web application. Localhost can be replaced with the computer name.
- Exporter File directory – This field is automatically populated with C:\EEE\Exporter. Enter the correct drive letter and folder if they are different to the default. This is the location that the EEE Exporter was originally installed.
- SQL DLL File directory – This field is automatically populated with C:\EEE\SQLDLL. Enter the correct drive letter and folder if they are different to the default. This is the location that magenta_sql.dll was originally installed.
- EEE Service File directory - This field is automatically populated with C:\EEE\EEEService. Enter the correct drive letter and folder if they are different to the default. This is the location that the EEE Service was originally installed.
- Copy Patch files from – This field is automatically populated with the drive and folder name that EEEPatch.exe was run from. You should normally not need to change this field.
The last line in the top half of the screen details the database version of the EEE database you have selected, and also the current EEE Version which is obtained from files in the specified EEE Web Server directory.
The bottom section of the patch screen, as shown in Figure 3, selects which components of EEE are being patched. Click on the APPLY PATCH button to start the installation of the service pack. The mandatory items for each service pack are “EEE Web Application” and “EEE Database”. If a component is not being updated during the service pack installation, you can remove the tick beside that component. Before proceeding, ensure that no users are in the EEE application, and that the EEE Export application is not running or scheduled to run while the service pack installation is occurring.
Figure 3
If you are upgrading multiple databases on the same server, you do not need to upgrade each component for each database you are upgrading. All components should be upgraded for the first database that is patched, but for the second and subsequent databases, you only need to patch “EEE Reports” and “EEE Database”. All other components are shared between all EEE database.
Service Pack Installation Logs
Each time a service pack is applied using the EEEPatch.exe, a log file is created in the same folder as EEEPatch.exe. This is a text document called EEEPatch_log_YYYYMMDDHHMMSS.txt. This text file logs all activity that has occurred as part of the service pack installation, and can be useful for any fault finding.
Service Pack Installation Errors
If an error occurs during the installation of the service pack, the installation will cease and a warning message will be displayed indicating an error occurred. If this happens, seek advice from Magenta Retail before proceeding any further. As a minimum, you should email the service pack installation log to the Magenta Retail helpdesk on support@magentaretail.com.au.
The most common service pack installation failures occur in the following instances:-
- When upgrading an application such as EEE Exporter, the application is running during the application of the service pack. This will prevent any .exe or .dll files being updated as they will be in use.
- A database incompatibility prevents the SQL upgrade scripts from completing successfully.
Installing a EEE service pack on multiple servers
When installing a EEE Service Pack in a multi server configuration, the following difference apply.
Database Server
All components except “EEE Web application” should be updated when applying the service release to a database server. The “EEE Web Server Directory” and “EEE URL” need not be specified.
Application Server
When upgrading an Application server, the tick beside ALL components except “EEE Web application” MUST be removed as you are only updating the Web application on this server. There is no requirement to specify a “EEE SQL Server” or a “EEE database”, but you must ensure that the “EEE Web Server Directory” and “EEE URL” are specified correctly.
