There are times when changes are required to machines and systems which will have an impact on Radix DM.  When designing a migration plan tailored to your circumstances it is essential to know which machines on your network are being altered and how they relate to Radix DM.  These can be classified as changes to one or more of the following components:

the Radix DM Server;

Radix DM Client machines;

the SQL Server containing the Radix DM database

other data source machines;

installed Radix DM applications (the Radix DM Crawler and the Radix DM Indexer);

the Document Store where the files saved in Radix DM are stored;

All operations should be performed by a system administrator who also has full Radix DM Administration privileges.  The best time to make these changes is after hours when users are not accessing documents or servers.

Locations

Radix DM uses the concept of Locations to store paths for internal settings.  These must be checked to ensure that any folders that are referenced are updated as required. To do this, start Radix DM Administration, then go to Global Settings->Locations and modify each path in every location if the existing folder values will be changed during the migration. 

Changes to the Radix DM Server

The Radix DM Server is the primary machine where a site's Radix DM is first installed.  This computer typically has all the installation files for the client version of Radix DM (at \\SharedComputerName\RadixShareName\RadixDM\Installations) as well as the shared configuration file (\\SharedComputerName\RadixShareName\RadixDM\Config\RadixDM.config). If this machine is being changed a number of steps must be taken to ensure that that Radix DM functions normally:

1) Radix DM uses Active Directory to provide access to users based on their login name.  If these login names change then user logins must also be changed in Radix DM Administration.  To do this, start Radix DM Administration, then choose Security->Users and modify the value in User Name for each user. 

 2) A configuration file called RadixDMClient.config (which refers to the shared location where the Radix DM server has been set up) must be modified to point to the new Radix DM server machine.  A copy of this file exists at \\SharedComputerName\RadixShareName\RadixDM\Installations and in each subfolder thereof.

 Every one of these identical files will contain the path to the shared configuration file in the line:

<add key="ConfigurationFile" value="\\SharedComputerName\RadixShareName\RadixDM\Config\RadixDM.config"/>

This SharedComputerName\RadixShareName value should be changed to the new machine name path for every file.  A copy of this changed file must also be pushed to each user's profile folder.

3) All folder permissions and other security considerations configured for the SharedComputerName\RadixShareName folder must be replicated on the new server.

Changes to the Radix DM Client

If the Radix DM Client machine changes then it may be necessary to reinstall the Radix DM Client from the shared Radix DM installation folder at \\SharedComputerName\RadixShareName\RadixDM\Installations\RadixDMClient2.0.XX where XX is the version number of the most recent of all versions available.  This is only required if the local Radix DM installation on a specific machine is affected.

Changes to the Radix DM SQL Server Instance

Any database on which Radix DM is installed should be set up with Mixed Mode authentication. Ensure that TCP/IP is enabled and that firewalls allow access for all users to the new instance.

Locate the database instance that Radix DM is installed on. This database is listed in the shared configuration file at \\SharedComputerName\RadixShareName\RadixDM\Config\RadixDM.config in the line:

<add name="RadixDM" connectionString="Server=SQLSERVERNAME; Database=RadixDMV2; ...;"/>.

This database must be backed up and restored on the new SQL Server instance and this configuration file altered so that it references the new SQL instance. It is imperative that the database be backed up and restored in a window when no users are using the database, once the database has been backed up no further documents should be saved into Radix DM until the migration is complete.

Examine the connection string used to connect to the database in the configuration file. If a User Name/password is used, ensure that this user has been set up on the new Instance with the same password previously used.  If Integrated Authentication is used then set up the same group permissions as before and grant similar access to that group.

It is also important to verify that the database is configured so that the property Auto Close is turned to OFF. This option may already be disabled on the new database.

Remote Database Fields

Every remote database that Radix DM uses to provide information for database fields must be checked to ensure that the data source remains valid.  To do this, start Radix DM Administration, then go to Libraries->Remote Databases.  For each Remote Database, alter the connection strings if required and test the connection to ensure that the data source is still valid.

Moving the Document Store for Library Groups

Every library group must be checked to ensure that the paths for files are still valid.  To do this, start Radix DM Administration, then go to Libraries->Library Groups and change the Base Path value to the new documents' location by clicking the Change… button.  This operation will not move the files from the old location to the new location; this step must be taken separately.

Ensure that Windows permission has been set up for the new folder locations, replicating access levels currently set up for all users.

In addition, all the text indexes that have been created for this library will need to be recreated. Information about how to do this is available in the following section.

Installed Radix DM Applications (Radix DM Crawler and Radix DM Indexer)

There are two programs that function as part of Radix DM which may also be affected by a change in machine configuration.  The computers on which the Radix DM Crawler and the Radix DM Indexer are set up can be identified through the Admin Health Check.  To do this, right click on the Radix DM Grabber and select the option Admin Health Check and examine the sections labelled Radix DM Crawler and Radix DM Indexer respectively.

Radix DM Crawler

This program can be run from any machine which has the Radix DM Client installed.  The Radix DM Crawler runs as a scheduled task, generally once per day at a time after hours when disk access is lower, e.g. 11 pm.  This scheduled task should be configured to run as:

C:\Program Files\Radix Software\Radix DM Client\RadixDMCrawler.exe /A

Radix DM Indexer

This program is installed and managed as a separate application.  If the machine on which this program is installed is changing then the program should be reinstalled, following the instructions provided at the Radix DM Support site.

In addition, if the Index files created by the Radix DM Indexer are located on a machine that is changing as a result of the migration or the library groups base paths have been changed then these Indexes will need to be deleted and recreated as they will no longer be valid.  To determine the folder containing these index files, start Radix DM Administration, then choose Global Settings->Locations and for each location, check the value in Text Index Base Path.  After the index files have been deleted restart the Radix DM Indexer Service from the Radix DM Indexer Manager program (if not already running) to begin recreating the files.

Testing

To test that Radix DM has been migrated successfully, use components of the program to verify that functionality meets expectations.  The program should start normally for multiple users who have the Radix DM Client installed.  For each library group, ensure that documents can be saved and that all fields are assigned values as part of this process.  Files in all library groups should be able to viewed and opened and saved as expected.  Verify that external data sources connect to data sources and provide correct data.