Upgrading
For a successful upgrade, it is important to understand the changes between your current version and the version you are upgrading to. In some cases, you will need to do a "stepped" upgrade, as you can't upgrade directly from some older versions to the current version. In the case of v8.1, your upgrade path is limited to upgrading from v8.0.5, v8.0.6, or v8.0.7.
If you are upgrading a cluster node, refer to Active-Passive Failover Clustering--Installing or Upgrading or Active-Active HA Cluster - Installing or Upgrading the Server .
Before upgrading your EFT installation to EFT v8.1, please read and understand the following information.
- EFT v8.1 supports upgrades only from v8.0.5, v8.0.6, and v8.0.7. The EFT installer will prevent you from upgrading if it detects an installed version that is not supported in the v8.1 upgrade path.
- The previous (32-bit) version of EFT (v8.0.5, v8.0.6, or v8.0.7) will be uninstalled automatically.
- When the previous (32-bit) version of EFT is uninstalled, the EFT service account is discarded. You must recreate the Windows service account for EFT service to use. For details of creating the EFT service account, refer to Windows Account for the EFT Service.
- Server Backups shall be done prior to upgrades (this includes any WTC customizations).
- If you are using an Oracle database, you must install both the 32-bit ODAC drivers for the report writer, and the 64-bit ODAC drivers for EFT to work with Oracle.
- On the RSA Authentication server, if EFT is not configured as the fully qualified domain name, for example: EFTServer2019.test.globascape.net (fully qualified name), and is instead listed as just EFTServer2019, it is possible that post-upgrade RSA Authentications may fail and the EFT log may report an error message: "RSA Authentication Agent is not initialized." (This is configured on the RSA server, not in EFT, and the sdconfi.rec file is copied from the RSA Server to EFT.)
To upgrade EFT and its modules
-
Close all unnecessary applications so that the installer can update system files without rebooting the computer.
-
Start the installer. The Welcome page appears.
-
Read the Welcome page, and then click Next. The License Agreement page appears.
-
Read the license agreement, and then click I agree to accept it. Clicking Cancel aborts the installation.
-
If you are upgrading or reinstalling, the version detected page appears.
-
Click Upgrade then click Next. The Choose Components page appears.
- Click Next. The ARM selection page appears.
-
If you want to configure auditing and reporting, click Next.
-
If you do not want to configure auditing and reporting, click Skip auditing and reporting configuration, and then click Next to skip the database configuration pages. You can still configure the database later, if you want. (Skip to step 18.)
-
If you want to manually create the database later, click Skip auditing and reporting configuration, and then refer to Manually Creating the ARM Database in SQL Server or Manually Creating the ARM Database in Oracle when you're ready to create the database. (Skip to step 18.)
-
Specify the type of database, SQL Server or Oracle, that EFT is to use. You will need the connection information available to point EFT to the database. If you already have a database to use, then you do not need to install SQL Server Express. (If you are using the "no db" installer, you will not see the "Install SQL Server" option.)
-
Install SQL Server Express
- SQL Server Express is provided for use in a trial. It is not intended for production use. During installation, a default system administrator account (the "sa" account) will be created within SQL Server Express. The EFT administrator account password will be used as the password for this "sa" account. Click OK to continue SQL Server Express installation and follow prompts to complete SQL Server Express installation.
-
Use existing SQL Server:
-
Click Use an existing EFT ARM database. The configuration page appears.
-
Specify Windows or SQL Authentication. (Windows mode allows you to connect through a Microsoft Windows NT or Windows 2000 user account. SQL allows you to connect using either Windows Authentication or SQL Server Authentication.)
-
Specify the host address or instance name.
-
Specify the database server SA or privileged user account name (for example, sa).
-
Specify the database server SA or privileged user account password.
-
(Optional) Click Next or Test to test the connection to the database. If the test fails, click Yes to verify database connection details or No to continue without configuring the database.
-
Use existing Oracle database:
- Click Create a new schema. The configuration page appears.
- Specify the database host address and the EFT-specific schema name and database administrator credentials, and then click Test or Next to test the connection to the database. (If you have installed Oracle Database Express Edition (XE) for testing/demo purposes, the instance name is XE and the User Name is SYSTEM.)
- If the test fails, click Back to verify the configuration or click Next and then Next again to open the Oracle Technology Network download page and download "Oracle Data Access Components for Windows" driver, if necessary.
- After the test is successful, click Next. The Confirm Database Upgrade page appears.
- Click Install. When installation is complete, a Completed page appears.
- Click Next. On the final page, select or clear check box to start the administration interface, create a shortcut to the administration interface on the desktop, show the installation log, and/or start the EFT server service.
-
Click Finish.
When you install EFT, the EFT administrator Interface check box must also be selected. After you have installed EFT and the administration interface on one computer, you can install the administration interface on other computers for remote administration. (To install the administration interface on a remote computer, refer to Installing the administration Interface Remotely.)
