Use the instructions in the following sections to upgrade from Retain 23.2 or later to Retain 23.4 and later.
Table 2-1 Preparing for Retain 23.4 and Later
Task |
Details |
---|---|
Ensure that the Retain server is connected to the Internet |
|
Ensure that SMTP Is Working in Retain |
|
Get the 23.4 and later software |
|
Ensure Adequate RAM |
|
Back up the Database and the Retain Server |
The upgrade should run smoothly. However, best practice always dictates backing up systems before making major changes.
|
If you are upgrading Retain on a Windows server, go to Upgrading to 23.4 and Later (Windows)
Table 2-2 Upgrading to 23.4 on SLES
Installation Section |
Details |
---|---|
Stop Retain before Upgrading |
|
Run the Retain 23.4 and later Installation |
|
License Agreement |
|
Software and RAM Requirements |
The Linux install lists the 23.4 and later software and RAM requirements.
|
Retain Components Selection Page |
The install displays the Retain components that are already installed on the server.
|
Pre-requirements Status |
The install checks for OpenJDK 17 and an updated version of Tomcat 9. If they are not installed, it installs and configures them for Retain. NOTE:The Java and Tomcat verification/installation process can take a while, so be patient while the installation works in the background. The installation process extracts and installs Retain 23.4 and later. Next, it starts the system processes that Retain requires. Finally, a message reminds you to consult the documentation.
|
If you are upgrading Retain on a SLES server, go to Upgrading to 23.4 and Later (Windows)
Table 2-3 Upgrading to 23.4 on Windows
Dialog/Section |
Details |
---|---|
Stop Retain before Upgrading |
|
Run the Retain 23.4 and later Installation |
|
Welcome to the Retain Setup Wizard |
|
Software Requirements |
The install lists the 23.4 software and hardware requirements along with the software that it will install
|
License Agreement |
|
Select Destination Location |
|
Retain Components Selection Page |
The install displays the components that are already installed on the server.
|
Pre-requirements Status |
|
Information |
The install reminds you to consult the documentation.
|
General Information |
A message shows the Retain access URL.
|
Completing the Retain Setup Wizard |
|
After Retain 23.4 or later is updated, update the Indexing Engine to Solr 9. You can do this at any time after the upgrade, but if you have Manage Server rights, you are prompted to perform the Index Engine update.
In Admin Console, when it is prompted to update the indexing engine, click Ok.
NOTE:It can take some time for the Server Configuration page to load.
In Server Configuration > Index, click Configure in the Indexing Mode column.
IMPORTANT:When you configure Solr 9, all delete jobs are disabled until Solr 8 clean-up is completed.
You are prompted to select a Port and Index Path. The default Port is 1 more than the port used for Solr 9. For example, if the port for Solr 8 index engine is 8081, then on upgrading Retain, the default port for Solr 9 will be 8082. The index path is the new path for index files. If the index directory is using a symlink, another symlink needs to be created for the new index folder so that the new index files are stored in an appropriate storage location.
NOTE:
If you are running Retain on a Windows Server, Solr 9 restricts the use of Windows SMB shares on the UNC format, such as\\myhost\myshare\mypath. For the indexer storage path, you can use a drive and mount it later. As a workaround, map the storage path in UNC format to a symbolic link folder on the local drive:
On the server where Retain is running, run the following command in the Windows Command Prompt: mklink /D C:\myLink \\IP address\c\Retain\Index In the above command, C:\myLink corresponds to the linked folder on the local drive and \\IP address\c\Retain\Index corresponds to the storage path in UNC format.
Ensure that the Retain Tomcat service is running as a user who has access to the shared folder. If not, please update the service and restart Tomcat.
If you are running Retain on a Linux Server, using a different path than the default, you need to make sure the ownership is set to tomcat:www.
A disk check will run to make sure that there is enough space on your server to migrate the indexer. The free space needed for the migration is 3 times the size of the current index. The recommended free space is 3.5 times the current index size.
When the check passes, Solr 9 is configured and starts indexing. At this point, you can continue with the next steps to switch to Solr 9 or you can wait for Solr 9 to finish indexing.
IMPORTANT:Once Solr 9 is configured, index optimization and backup are disabled until Solr 8 clean-up is completed.
After Solr 9 is configured, click Switch to Solr 9 and restart the Tomcat service.
IMPORTANT:If you switch to Solr 9 when the re-indexing is in progress, the search results in Retain will not be accurate.
Ensure that Solr 9 works as expected. If not, select Re-index All Items and switch back to Solr 8.
Click Clean up Solr 8.
IMPORTANT:This deletes Solr 8 and all the Solr 8 data from the system. Before you perform Solr 8 clean up, ensure that the Solr 9 is working as expected.
Click Ok to confirm.