If an existing install of FileCatalyst Direct Server needs to be moved/migrated/changed to an install on a new machine and the existing settings need to be maintained. This guide will provide instructions on how to backup your settings and export them to a new machine.
This resolution is platform-agnostic, so you can change operating systems if required.
FileCatalyst Server v3.0 or later.
- Backup the old configuration files:
The following list of files will be required for the migration from the old machine to the new one. Move them into a folder outside of the install location for now.
These files and folder will be located in the root of the installation directory of the FileCatalyst Server:
- .fcdb folder: This folder is hidden on some operating systems and contains the database information.
- fcconf.conf: This file contains most of the settings that belong to the FileCatalyst Server and your license.
- ipfilters.xml: The contents of this file contain the IP access rules to the FileCatalyst Server.
- wrapper.conf (Linux only): This file is used to configure Java heap and other wrapper properties that impact the service. It is located in /opt/utechsoft/server/conf/ folder.
- users.xml: This file will only exist on deployments older than v3.0. It has been replaced by the .fcdb.
- authentication.xml: This file will only exist on deployments older than v3.0. It has been replaced by the .fcdb.
- If a third-party SSL certificate has been deployed into the FileCatalyst Server, the files associated with them need to be migrated as well. It is possible that these files may be located outside of the FileCatalyst Server installation directory. Open the fcconf.conf file in a text editor and search for the properties:
These two properties will point to the path where the SSL Certificate and .p12, .key, .pem or .pvk files are located.
- Install FileCatalyst Direct Server on the new hardware.
- Run the FileCatalyst Server in stand-alone mode to obtain the new request string. There are two methods of getting the request string:
- Start the FileCatalyst Server with a UI.
- Alternatively, the FileCatalyst Server can be started from the command line by using the following from the FileCatalyst Server as the working directory:
java -jar FileCatalystServer.jar
The software will output the request string to the console.
- Copy and paste this request string into an email and send it to Our Customer Operations department ([email protected]) to obtain a new key.
- Import settings to the new FileCatalyst Server:
- Shut down the current instance of the FileCatalyst Server, if it is open.
- Navigate to the FileCatalyst Server installation directory.
- From the backup folder in step 1, copy and overwrite the current files into the FileCatalyst Server installation directory:
- .fcdb folder
- wrapper.conf (Linux)
- If you are using UNC path mounts or other types of NAS, make sure that this machine has access to them and the user account that you are going to use to launch the FileCatalyst Server Service has sufficient permissions to Read, Write, and Delete. Check that all Firewall rules NAT redirections are properly set up to point to this machine.
- Edit the configuration files fcconf.conf(Windows only), wrapper.conf(Linux only) and have the following entry applied if it's not found "wrapper.java.command=./jre/bin/java"
This change will ensure to use of the inbuilt Java Runtime Environment (JRE) which is now prepackaged with all our FileCatalyst applications.
Windows : <path to>\FileCatalyst Server\fcconf.conf
- Edit the configuration file "fcconf.conf", Replace the existing license with the new license acquired in step 4. c
- Start the new FileCatalyst Server in stand-alone mode.
- Make sure that your user accounts, network information, ports and IP Masquerade information are properly set up.
- If you have used a third-party SSL certificate in the FileCatalyst Server, add them back in from the Security tab.