2.2 Upgrading from 2.6.2 to 3.5.1.1

2.2.1 2.6.2 to 3.5.1.1 on SLES

Preparing for the Migration and Upgrade (SLES)

Table 2-1 Preparing for Data Migration

Task

Details

Make sure that the Retain server is connected to the Internet

  1. Verify that the Retain server is connected to the Internet, so that the installer can download and upgrade Java to the correct version.

    If your server isn’t connected to the Internet, see Installing Java on a Server with no Internet Connection.

Ensure SMTP Is Working in Retain

  1. The Migration Tool must be able to email migration status messages. Otherwise, it will stop and display an error message.

Get the 3.5.1.1 software

  1. Download the Retain 3.5.1.1 .zip file.

  2. Copy the file and unzip it on the following:

    • The Retain server that you are upgrading.

    • Every server that is running a Retain Worker.

    • The server from which you are running the Database Migration Tool if it’s not the Retain server.

Decide where to run the Migration Tool

  1. When possible, run the migration tool on the server where the database is running.

  2. If you need to run the migration from a separate server, do the following:

    1. Copy the following file to the other server:

      /var/opt/beginfinite/retain/RetainServer/WEB-INF/cfg/ASConfig.cfg

    2. Note the file location on the other server so that you can specify it when you run the Database Migration Tool.

Ensure Adequate Disk Space

  1. Database migration requires enough empty disk space to allow for:

    • ~1 X current_database_size: For a backup copy of the existing 2.x database.

      Plus

    • ~1 X current_database_size: For the new 3.x database, which is about the same size as the 2.x database.

      Or

      Up to 10 X current_database_size (temporary, MySQL only): MySQL query constraints and settings can cause the migration process to temporarily consume up to 10 times the current disk space.

      See the next step.

  2. If you use a MySQL database or you require additional empty disk space for the migration to run, you can add a tmpdir setting to the my.ini file that points to a volume where there is available disk space.

  3. If you use MS SQL or Oracle, make sure your DBA is aware of the need for temporary additional disk space.

Ensure Adequate RAM

  1. Make sure the database server has enough RAM (ideally 18 GB).

  2. Devote at least 1 GB RAM (preferably 8 GB) to the Migration Tool process, independent from the RAM used by the other processes running on the server.

If you use MySQL

Retain 2.6.2 specified MySQL 5.1 as the supported version.

Although it is assumed that you have migrated your system to a later version in the interim, be aware that Retain 3.5.1.1 requires MySQL 5.5 or later.

Back up the Database and the Retain Server

The database migration should run smoothly. However, best practice always dictates backing up systems before making major changes.

  1. Back up your database and the Retain server immediately before starting the database migration.

    If you need assistance identifying where Retain’s components are stored, see Finding Retain’s Storage Paths.

Make sure the database index is prepared

  1. Make sure there is an index on the recip_id column in the t_recp_properties table.

    If this index does not exist, Recipient migrations take substantially longer.

    • For MySQL

      1. Log in to MySQL and run this query:

        show indexes from database-name.t_recp_properties \G

      2. If the recipients index is missing, create it with this query:

        CREATE INDEX idx_recip_id ON t_recp_properties (recip_id);

    • For MS SQL

      1. In SQL Server Management Studio, expand Databases > your Retain database > dbo.t_recp_properties > Indexes.

      2. If the recipients index is missing, create it with this query:

        GO
        CREATE NONCLUSTERED INDEX idx_recp_value
        ON t_recp_properties (recip_id)
        INCLUDE (value)

    • For Oracle

      Ask your Oracle DBA for assistance with determining the status of the recipients index.

Check for database fragmentation and rebuild if needed

NOTE:MySQL fragmentation issues are fixed during the Retain upgrade. If you use MySQL, you can skip to Disable Transaction Logging.

  1. If your Retain deployment uses an MS SQL or Oracle database, check for fragmentation issues in the following indexes:

    • attachment

    • Document

    • Email

    • t_msg_properties

    • t_recipients

    • t_recp_properties

    For MS SQL

    1. In SQL Server Management Studio, expand the indexes folder.

    2. Double click an index to display its fragmentation percentage.

    3. For indexes that require rebuilding, right click the index and choose the Rebuild option.

    For Oracle

    1. Ask your Oracle DBA for assistance with checking and rebuilding indexes.

Disable Transaction Logging

Because Transaction Logs consume a lot of disk space, leaving logging enabled during migration could cause the system to run out of space.

  1. Assuming that you are backing up your database before starting the migration, Micro Focus strongly recommends that you disable Transaction Logging afterward, by doing the following:

    For MySQL

    1. Edit the /etc/my.cnf file.

    2. Insert a pound sign (#) at the beginning of the following line.

      log-bin=mysql-bin

      So that it reads

      #log-bin=mysql-bin

    3. Save the file.

    4. Make sure to restore the original setting after the migration completes.

    For MS SQL

    1. Access the Retain database properties, and change the recovery model to Simple.

      For more information, see Set Database Recovery Model (SQL Server) on Microsoft.com.

    2. Make sure to change the model back after the migration completes.

    For Oracle

    1. Consult with your Oracle database administrator.

Disable Jobs

Micro Focus recommends disabling archive jobs during the migration.

Continuing to run Jobs during the migration process has been known to cause database racing conditions, which cause the migration tool to stop.

Although the tool can be restarted when this happens, it is best to avoid potential issues with an interrupted migration.

Migrating the SQL Database from 2.x to 3.x (SLES)

Table 2-2 Migrating the Database (SLES)

Dialog/Section

Details

  1. Working as the root user, open a terminal prompt and navigate to the folder that you prepared in Get the 3.5.1.1 software.

  2. Enter the following command:

    ./RetainInstall.sh

    The installation script asks whether this is an upgrade and presents four options as responses.

Choose (1-4):

  1. Type 2 and press Enter.

    The installation sets up the required version of Java and prepares a directory for running the data migration. The tool reports each action on the screen for your information.

Run Migration Program?

  1. Type Y and press Enter.

Run Migration [y/n]?:

  1. If your database is smaller than 150 GB, skip to the next row.

    If your database is larger than 150 GB, you need to increase the Java memory heap (assuming you have sufficient memory installed for the other services, such as the Retain server, database server, etc.).

  2. Type n and press Enter.

  3. In the folder that you prepared in Get the 3.5.1.1 software, open the migrate3 folder.

  4. Edit the MigrateConfig file.

  5. Change the values for the following settings to allocate more RAM.

    Four GB (4096M) is the suggested minimum; eight GB (8192M) is optimal.

    1. Change Xms256M to Xms4096M (minimum) or Xms8192M (optimal)

    2. Change Xmx1024m to Xmx4096m (minimum) or Xmx8192M (optimal)

  6. Save the MigrateConfig file and close the editor.

  7. Enter the following command to run the migration tool.

    ./BeginMigration.sh

  8. Skip the next row, then continue.

Run Migration [y/n]?:

  1. Type y and press Enter.

Press ENTER

  1. If you are running the Migration Tool on the Retain server, press Enter and continue with the next row.

    If you are not running the migration tool on the Retain server, you are prompted for the path to the ASConfig.cfg file.

    1. Type the path to the ASConfig.cfg that you copied to the server in Decide where to run the Migration Tool.

    2. Press Enter.

Use GUI instead of Console [y]:

  1. The program displays more tips regarding the ASConfig.cfg file, then prompts for three migration tool settings.

    • GUI instead of Console [n]: Press Enter.

    • Refresh stats Interval (15 seconds): Press Enter, or type a different interval and press Enter.

    • Exit automatically when migrated item count hits zero [n]: Do not change the default. Press Enter.

      WARNING:Although the migration tool can run for as many cycles as needed to migrate all archived items, the tool itself can only be run one time.

      Because some organizations choose to keep their archiving jobs running for the first migration cycle (not a best practice), it is common that running jobs archive additional items in the 2.x database after the cycle ends. If you stop the migration tool when items are still being archived in 2.x, the additional items can’t be migrated to 3.x and are effectively lost to Retain.

      If you must continue running jobs during the migration, you might consider stopping all jobs about one day before the migration concludes.In most cases you will then only need one additional cycle to confirm that everything has been migrated.

      You could also stop all jobs after the first cycle, and then run additional cycles until all items have been migrated.

      In all cases, do not choose the Exit Immediately option until all jobs have been stopped and the last migration cycle reports that no new items were archived.

      Otherwise, as already stated, items archived in the 2.x database but not migrated to 3.x are effectively lost.

Please verify all settings before choosing to proceed with the migration.

  1. The program displays the configuration settings for your review, then lists 6 options:

    • 1 Message Store settings: Type 1 and press Enter if you need to adjust any of the message-store database access settings.

    • 2 Configuration settings: Type 2 and press Enter if you need to adjust any of the configuration database access settings.

    • 3 Mailer settings: Type 3 and press Enter if you need to adjust any of the SMTP settings.

    • 4 Interface settings: Type 4 and press Enter if you want to change any of the UI settings you specified earlier.

    • 5 Proceed with Migration: Type 5 and press Enter if you want to proceed with the migration.

    • 6 Exit: After you have started the migration tool, only type 6 when the most recent migration cycle showed no new items migrated.

      HINT:If the first migration cycle has not yet started, you can use this option to stop the migration tool and run the process later. The choices you have made are kept.

 

  1. After you type 5 and press Enter, the migration tool does the following

    • Upgrades the schema

    • Checks the database version

    • Disables deletion jobs

    • Checks the SMTP configuration

    When all checks pass, you can press Enter to continue.

GWAVA Retain Migration

  • Each step of the migration progress displays at the terminal prompt.

    IMPORTANT:Do not interrupt the migration process after it begins.

    Depending on the size of your archive, this process can require days, weeks, or even months to complete. However, assuming that you have followed the instructions in the previous sections, your Retain services will continue to function normally and the process should run well to completion.

  • If any errors occur during the migration, see the migration log in the Migrate3 directory for details.

  • Fix the errors and run the job again by opening BeginMigration.sh. The migration picks up where it left off.

  • If the system runs out of disk space, you must restore the 2.x database backup, fix the space problem and run the migration again.

    For assistance, contact Micro Focus support.

  • If you are required to restore the 2.x database and start over for any reason, make sure to also do the following:

    1. Edit the ASConfig.cfg file.

    2. The previous migration attempt will have reset the <storageEngine> parameter to database_process.

      Change the parameter to standard before rerunning the migration.

  • When the migration finishes, Retain sends an email to notify that the first migration cycle completed.

After the first pass completes

  1. If you haven’t already done so, disable all Retain Jobs.

  2. Click the Wait 5 minutes for another pass button.

    If you don’t click the button, another pass runs in an hour.

When 0 items were migrated on the last pass

  1. Wait for the next migration cycle to complete.

  2. Check the status email.

  3. If no new items were archived and all jobs are still disabled, the migration to the 3.x database is complete.

    If new items were archived, repeat from Step 2 in the previous row until the status email shows 0 items for the last cycle run.

  4. When the migration reports that 0 items were migrated, type 1 and press Enter.

    The migration tool stops running.

Re-enable Transaction Logging and Retain Jobs

  1. Re-enable Transaction Logging by reversing the changes that you made in Disable Transaction Logging.

  2. Re-enable the Jobs that you disabled during migration process.

Upgrading to 3.5.1.1 (SLES)

Table 2-3 Upgrade Retain to 3.5.1.1 (SLES

Dialog/Section

Details

Retain Server Terminal Prompt

  1. Working as the root user, at the terminal prompt, stop Apache and Tomcat.

    For example, on SLES 11 enter the following commands

    rcapache2 stop
rcretain-tomcat5 stop

  2. Navigate to the folder that you prepared in Get the 3.5.1.1 software.

  3. Enter the following command:

    ./RetainInstall.sh.

  4. Type 1 and press Enter to agree with the licensing agreement.

Choose (1-4):

  1. If you have completed the database migration as instructed in Migrating the SQL Database from 2.x to 3.x (Windows), type 3 and press Enter.

Choose (1-2):

  1. Confirm the completed database migration by typing 1 and pressing Enter.

Install Retain Server (y/n)?

You are prompted for the components that apply to this server.

  1. Type either Y or N, depending on whether the component indicated is installed on the server you are upgrading.

  2. Press Enter and repeat.

Choose (1-3):

  1. Confirm that you are upgrading and want to preserve the existing configurations by typing 1 and pressing Enter.

    Installation progress displays on the screen along with information about running the Retain components.

    When you are reminded to read the documentation and the system prompt appears, Retain has been successfully upgraded on this server.

System prompt

  1. At the terminal prompt, start Tomcat. (Apache should be running already.)

    For example, on SLES 11 enter the following command:

    rcretain-tomcat7 start

Start Retain 3.5.1.1 for the First Time

  1. In you management browser, access the Retain server’s web administrative console:

    http://ip_or_dns/RetainServer

Retain Database Schema

A message displays stating that the 3.x database schema enhancements require that the database be updated.

  1. Click the Enter Credentials button.

  2. Log in as the Retain administrator.

    A message in red text displays indicating that the database is being updated and the process should not be interrupted.

  3. When a green-text message indicates that the update is complete, Retain is ready for use.

  4. At the terminal prompt, restart Tomcat.

    For example, on SLES 11 enter the following command:

    rcretain-tomcat5 start

  5. Continue with Upgrading from 3.5.1.1 (or 3.5.1) to 4.5

2.2.2 2.6.2 to 3.5.1.1 on Windows

Preparing for the Migration and Upgrade (Windows)

Table 2-4 Preparing for Data Migration

Task

Details

Ensure an Internet Connection on the Retain server

  1. Verify that the Retain server is connected to the Internet, so that the installer can upgrade Java to the correct version.

    If your server isn’t connected to the Internet, you must download the required Java installation files. Do the following:

    1. On a workstation with an Internet connection, download the required version of the Java installer to an Internet-connected workstation by clicking here.

    2. Copy the downloaded .zip file to the following location on each server you are upgrading:

      C:\Program Files\Beginfinite\Retain\Java6

    3. When you run the Retain installer and the Install Java button displays, do not click the button. Just click Next.

Ensure SMTP Is Working in Retain

  1. The Migration Tool must be able to email migration status messages. Otherwise, it will stop and display an error message.

Get the 3.5.1.1 software

  1. Download the Retain 3.5.1.1 .zip file.

  2. Copy the file and unzip it on the following:

    • The Retain server that you are upgrading.

    • Every server that is running a Retain Worker.

    • The server from which you are running the Migration Tool if it’s not the Retain server.

Decide where to run the Migration Tool

  1. When possible, run the migration tool on the server where the SQL database is running.

  2. If you need to run the migration from a separate server, do the following:

    1. Copy the following file to the other server:

      C:\Program Files\beginfinite\retain\RetainServer\WEB-INF\cfg\ASConfig.cfg

    2. Note the file location on the other server so that you can specify it when you run the Migration Tool.

Ensure Adequate Disk Space

  1. SQL database migration requires enough empty disk space to allow for:

    • ~1 X current_database_size: For a backup copy of the existing 2.x database.

      Plus

    • ~1 X current_database_size: For the new 3.x database, which is about the same size as the 2.x database.

      Or

      Up to 10 X current_database_size (temporary, MySQL only): MySQL query constraints and settings can cause the migration process to temporarily consume up to 10 times the current disk space.

      See the next step.

  2. If you use a MySQL database, or you require additional empty disk space for the migration to run, you can add a tmpdir setting to the my.ini file that points to a volume where there is available disk space.

  3. If you use MS SQL or Oracle, make sure your DBA is aware of the need for temporary additional disk space.

Ensure Adequate RAM

  1. Make sure the database server has enough RAM (ideally 18 GB).

  2. Devote at least 1 GB RAM (preferably 8 GB) to the Migration Tool process, independent from the RAM used by the other processes running on the server.

Back up the SQL Database and the Retain Server

The database migration should run smoothly. However, best practice always dictates backing up systems before making major changes.

  1. Back up your SQL database and the Retain server immediately before starting the database migration.

    If you need assistance identifying where Retain’s components are stored, see Finding Retain’s Storage Paths.

Make sure the database index is prepared

  1. Make sure there is an index on the recip_id column in the t_recp_properties table.

    If this index does not exist, Recipient migrations take substantially longer.

    • For MySQL

      1. Log in to MySQL and run this query:

        show indexes from database-name.t_recp_properties \G

      2. If the recipients index is missing, create it with this query:

        CREATE INDEX idx_recip_id ON t_recp_properties (recip_id);

    • For MS SQL

      1. In SQL Server Management Studio, expand Databases > your Retain database > dbo.t_recp_properties > Indexes.

      2. If the recipients index is missing, create it with this query:

        GO
        CREATE NONCLUSTERED INDEX idx_recp_value
        ON t_recp_properties (recip_id)
        INCLUDE (value)

    • For Oracle

      Ask your Oracle DBA for assistance with determining the status of the recipients index.

Check for database fragmentation and rebuild if needed

NOTE:MySQL fragmentation issues are fixed during the Retain upgrade. If you use MySQL, you can skip to Disable Transaction Logging.

  1. If your Retain deployment uses an MS SQL or Oracle database, check for fragmentation issues in the following indexes:

    • attachment

    • Document

    • Email

    • t_msg_properties

    • t_recipients

    • t_recp_properties

    For MS SQL

    1. In SQL Server Management Studio, expand the indexes folder.

    2. Double click an index to display its fragmentation percentage.

    3. For indexes that require rebuilding, right click the index and choose the Rebuild option.

    For Oracle

    1. Ask your Oracle DBA for assistance with checking and rebuilding indexes.

Disable Transaction Logging

Because Transaction Logs consume a lot of disk space, leaving logging enabled during migration could cause the system to run out of space.

  1. Assuming that you are backing up your database before starting the migration, Micro Focus strongly recommends that you disable Transaction Logging after the backup finishes by doing the following:

    For MySQL

    1. Edit the /etc/my.cnf file.

    2. Insert a pound sign (#) at the beginning of the following line.

      log-bin=mysql-bin

      So that it reads

      #log-bin=mysql-bin

    3. Save the file.

    4. Make sure to restore the original setting after the migration completes.

    For MS SQL

    1. Access the Retain database properties and change the recovery model to Simple.

      For more information, see Set Database Recovery Model (SQL Server) on Microsoft.com.

    2. Make sure to change the model back after the migration completes.

    For Oracle

    1. Consult with your Oracle database administrator.

Disable Jobs

Micro Focus recommends disabling archive jobs during the migration.

Continuing to run Jobs during the migration process has been known to cause database racing conditions, which cause the migration tool to stop.

Although the tool can be restarted when this happens, it is best to avoid potential issues with an interrupted migration.

Migrating the SQL Database from 2.x to 3.x (Windows)

Table 2-5 Migrating the Database (Windows)

Dialog/Section

Details

  1. In the folder that you prepared in Get the 3.5.1.1 software, right click RetainInstall.exe and select Run as Administrator.

  2. Click Next > Next.

    Select the second option, I’m upgrading from Retain 2.x.

Run Migration Installation Program?

  1. Click Yes.

    The installer checks for the correct version of Java and its associated system variables and performs other preliminary actions, which it summarizes on the screen.

Run Migration [y/n]?:

  1. If your database is smaller than 150 GB, skip to the next row.

    If your database is larger than 150 GB, you need to increase the Java memory heap (assuming that you have sufficient memory installed for the other services, such as the Retain server, database server, etc.).

  2. Type n and press Enter.

  3. In the folder that you prepared in Get the 3.5.1.1 software, open the migrate3 folder.

  4. Right click the MigrateConfig.bat file and select Edit.

    IMPORTANT:Do not click Open or the batch file will run.

  5. Change the values for the following settings to allocate more RAM. Four GB (4096M) is the suggested minimum; eight GB (8192M) is optimal.

    1. Change Xms256M to Xms4096M (minimum) or Xms8192M (optimal)

    2. Change Xmx1024m to Xmx4096m (minimum) or Xmx8192M (optimal)

  6. Save the MigrateConfig.bat file and close the editor.

  7. In the migrate3 directory, right click BeginMigration.sh and select Open.

Run Migration [y/n]?:

  1. Type y and press Enter.

Press ENTER

  1. If you are running the Migration Tool on the Retain server, press Enter and continue with the next row.

    If you are not running the migration tool on the Retain server, you are prompted for the path to the ASConfig.cfg file.

    1. Type the path to the ASConfig.cfg that you copied to the server in Decide where to run the Migration Tool.

      For example, if you copied the file to the this server’s desktop, the path might be C:\Users\Administrator\Desktop\ASConfig.cfg.

    2. Press Enter.

Use GUI instead of Console [y]:

  1. The program displays more tips regarding the ASConfig.cfg file, then it prompts for three migration tool settings.

    • GUI instead of Console: Press Enter. Either choice is fine, but the GUI includes tabs, which make the information generated during the migration process much more usable.

    • Refresh stats Interval (15 seconds): Press Enter, or type a different interval and press Enter.

    • Exit automatically when migrated item count hits zero [n]: Do not change the default. Press Enter.

      WARNING:Although the migration tool can run for as many cycles as needed to migrate all archived items, the tool itself can only be run one time.

      Because some organizations choose to keep their archiving jobs running for the first migration cycle (not a best practice), it is common that running jobs archive additional items in the 2.x database after the cycle ends. If you stop the migration tool when items are still being archived in 2.x, the additional items can’t be migrated to 3.x and are effectively lost to Retain.

      If you must continue running jobs during the migration, you might consider stopping all jobs about one day before the migration concludes.In most cases you will then only need one additional cycle to confirm that everything has been migrated.

      You could also stop all jobs after the first cycle, and then run additional cycles until all items have been migrated.

      In all cases, do not choose the Exit Immediately option until all jobs have been stopped and the last migration cycle reports that no new items were archived.

      Otherwise, as already stated, items archived in the 2.x database but not migrated to 3.x are effectively lost.

Please verify all settings before choosing to proceed with the migration.

  1. The program displays the configuration settings for your review, then lists 6 options:

    • 1 Message Store settings: Type 1 and press Enter if you need to adjust any of the message-store database access settings.

    • 2 Configuration settings: Type 2 and press Enter if you need to adjust any of the configuration database access settings.

    • 3 Mailer settings: Type 3 and press Enter if you need to adjust any of the SMTP settings.

    • 4 Interface settings: Type 4 and press Enter if you want to change any of the UI settings that you specified earlier.

    • 5 Proceed with Migration: Type 5 and press Enter if you want to proceed with the migration.

    • 6 Exit: After you have started the migration tool, only type 6 when the most recent migration cycle showed no new items migrated.

      HINT:If the first migration cycle has not yet started, you can use this option to stop the migration tool and run the process later. The choices you have made are kept.

 

  1. After you type 5 and press Enter, the migration tool does the following

    • Upgrades the schema

    • Checks the database version

    • Disables deletion jobs

    • Checks the SMTP configuration

    When all checks pass, you can press Enter to continue.

GWAVA Retain Migration

  1. Progress displays in either the GUI or the Command terminal, depending on your GUI choice.

    If you chose the GUI, a Java app opens and reports progress in three tabs:

    • Statistics Tab: During the migration, the Statistics tab displays the number of messages processed and the names of tables being migrated. it also shows the time that has elapsed for each table migration.

    • Logs Tab: If errors are listed, do the following:

      1. Fix the errors.

      2. Run the job again by opening BeginMigration.sh.

        The migration picks up where it left off.

      If the system runs out of disk space: You must do the following:

      1. Restore the 2.x database backup.

      2. Reset the ASConfig.cfg file, as follows:

        1. Edit the C:\Program Files\beginfinite\retain\RetainServer\WEB-INF\cfg\ASConfig.cfg file.

        2. Change the <storageEngine> parameter from database_process to standard.

        3. Save the file.

      3. Fix the disk space problem.

      4. Run the migration again.

    • Errors Tab: If any errors occur during the migration, see the migration log in the Migrate3 directory for details.

    NOTE:Do not close the Java window because that stops the migration.

    IMPORTANT:Do not interrupt the migration process after it begins.

    Depending on the size of your archive, this process can require days, weeks, or even months to complete.

    However, if you have followed the instructions in the previous sections, your Retain services will continue to function normally and the process should run well to completion.

  2. When the migration finishes, Retain sends an email to notify that the first migration cycle completed.

Pass Completed dialog

  1. Disable all Retain Jobs (if you haven’t already done it).

  2. Click the Wait 5 minutes for another pass button.

    If you don’t click the button, another pass runs in an hour.

GWAVA Retain Migration

  1. Wait for the next migration cycle to complete.

  2. Check the status email.

  3. If no new items were archived and all jobs are still disabled, the migration to the 3.x database is complete.

    If new items were archived, repeat from Step 2 in the previous row until the status email shows 0 items for the last cycle run.

  4. Click the Exit Immediately button, then click Yes.

  5. Click the Migration Complete button, then click Yes.

  6. In the Command Prompt window, press any key to exit.

Re-enable Transaction Logging and Retain Jobs

  1. Re-enable Transaction Logging by reversing the changes that you made in Disable Transaction Logging.

  2. Re-enable the Jobs that you disabled for the database migration process.

Upgrading to 3.5.1.1 (Windows)

Table 2-6 Upgrade Retain to 3.5.1.1 (Windows)

Dialog/Section

Details

Retain Server Desktop

  1. On the Retain server, click Start > Administrative Tools > Services (or the equivalent on your Windows server).

  2. Stop the Apache Tomcat tomcat5 and Apache 2.2 services.

  3. In the folder that you prepared in Get the 3.5.1.1 software, right click RetainInstall.exe and select Run as Administrator.

Setup - Retain

  1. Click Next > Next.

Upgrading from a Previous Version?

  1. You just finished migrating the database, so select the third option I’m upgrading from Retain 2.x and data migration is completed and click Next.

Confirmation

  1. Select Yes I’m absolutely certain. Please proceed and click Next.

License Agreement

  1. Accept the license agreement and click Next.

Select Destination Location

  1. If your Retain installation is in a non-standard location, browse to the folder and click Next.

    Otherwise, accept the default location shown by clicking Next.

GWAVA Retain Migration

  1. Select the services you are upgrading on this machine.

  2. Click Next.

Overwrite or Upgrade

  1. Leave the Upgrade option selected and click Next.

Java Installation

  1. Click the Install Java button.

    A command prompt window opens, then Java downloads and installs.

    When the installation finishes the window closes.

  2. Click Next.

Tomcat Installation

  1. Click Install Tomcat.

    A command prompt window opens, then Tomcat downloads and installs.

    When the installation finishes the window closes.

  2. Click Next.

Choose a Web Server

  1. Select the Web server you have installed and configured, then click Next.

    NOTE:If you are using Apache 2.2 and get an error that the directory is incorrect, browse to the correct path, then click Next.

AJP Port

  1. Accept or modify the AJP port used on this network, then click Next.

Ready to Install

  1. Click Install.

    The Retain software upgrades to version 3.5.1.1.

Information

  1. Click Next.

General Information

  1. Information about accessing Retain displays. Click Next > Finish.

Enable Tomcat and Apache

  1. On the Retain server, click Start > Administrative Tools > Services (or the equivalent on your Windows server).

  2. Start the Apache Tomcat 7.0 tomcat7 and Apache 2.2 services.

Start Retain 3.5.1.1 for the First Time

  1. In you management browser, access the Retain server’s web admin console:

    http://ip_or_dns/RetainServer

Retain Database Schema

A message displays stating that the 3.x database schema enhancements require that the database be updated.

  1. Click the Enter Credentials button.

  2. Log in as the Retain administrator.

    A message in red text displays indicating that the database is being updated and the process should not be interrupted.

  3. When a green-text message displays indicating that the update is complete, Retain is ready for use.

  4. Access Start > Administrative Tools > Services and restart Tomcat 7.