Knowledgebase : Cloud Solutions

Overview

The FileCatalyst Server supports writing to external file systems. Our application can read and write directly to these cloud-based storage vendors by adding them to the User account on the FileCatalyst Server. The following is a list of storage vendors we currently support:

  • Amazon S3
  • Azure Blob
  • OpenStack Swift
  • Google Cloud Storage
  • Backblaze B2
  • Wasabi
  • Dropbox (Labs)

We recognize that there are many vendors who support specific feature sets, however, we would like to advise our clients using any Cloud Storage to configure your tasks without using the following features:

  • Basic and Advanced Progressive Transfers (HotFolder)
  • Transfer File Delta (HotFolder)
  • Transfer Files using Incremental Modes (HotFolder and TransferAgent Express)
  • Auto-Resumes or Overwrites (All Clients)
  • Zipping (All Clients)
All the features mentioned above use the FTP command APPE (append) which means that there will be a file fragment that will have more blocks written to it. Using the features listed above could also leave orphaned files in your storage bucket which is not always visible or accessible by our software. These files are visible using the Native Storage Browser from the vendors and will need to be removed manually to prevent you from being charged with extra fees.

All of the limitations that are placed on External File Systems transfers using FileCatalyst Products are available Section 13: External File Systems page of our Server Documentation:

http://filecatalyst.software/download/filesFCDirect/current/documentation/server/Help.html#efs

Please note the link above requires a download password. You can obtain this by logging into the Support Portal and clicking on Get Download Credentials button in your profile. Alternatively, you can access the documentation from the Help menu from your Server Remote Administration application.


Resolution

Where possible please avoid the features listed above when configuring your transfer options and tasks. 

Overview

Internet Explorer has been the stock web browser that has been packaged in every Windows OS. As of November 30, 2020, Microsoft plans to end extended support for this browser. Following in the same footsteps we will also be terminating support for Internet Explorer browsers at this time as well.





You can read the full details of this update here: https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666

For our clients who are on Internet Explorer, we would highly recommend migrating your workflows to use Chrome, Firefox or Edge browsers.



Environment

Windows OS - Internet Explorer (all version)


FileCatalyst Workflow
FileCatalyst TransferAgent
FileCatalyst Server - Link/Upload/Download

Overview

Azure is Microsoft’s Cloud Platform that enables applications to be deployed across a high availability Internet-hosted environment. To deploy a FileCatalyst application, the proper ports must be opened and accessible to your Azure environment. This article will discuss the ports that need to be opened and how to open these ports using a scripted method.

As of the writing of this article, Azure only allows a total of 150 ports to be opened for any deployment. This is extremely important to note.

The default ports for FileCatalyst Direct are:

  • Port 21 for TCP.
    This is used as the communication channel. Port 21 is a default specified in the FileCatalyst Server and is not secure. You can change this as long as both FileCatalyst Server and Client Applications are using the same port.

  • Port 22 for TCP.
    This port is used for SSH connections.

  • Port 990 for TCP.
    This Port is secured over SSL and is also used as the communication channel. The default value of 990 can also be changed in the FileCatalyst Server Remote Admin Application.

  • Port range 8000-8999 for TCP and UDP.
    Some firewalls and NAT devices require setting up 2 separate rules and others allow you to specify TCP and UDP. These ports are used to transfer the Data to and from the FileCatalyst Server and is commonly referred to as the Data Channel. 
  • Port 12400 for TCP.
    This is the Remote Admin Port. This port is exclusive to the FileCatalyst Server Remote Admin Application.

The default ports for FileCatalyst Workflow/Webmail are:

  • Port 80 for TCP.
    HTTP inbound connections are accepted by the Tomcat Web Server on this port. 
  • Port 443 for TCP.
    HTTPS connections and secured communication to the Tomcat Web Server use this port. 

 

Environment

Microsoft Azure Cloud Computing

FileCatalyst Direct Suite v3.5 and later.

FileCatalyst Workflow v4.9.4 and later.

FileCatalyst Webmail v4.9.4 and later.

Windows and Linux Environments.

 

Resolution

  1. Plan of ports to open.
    Your local Windows System will need to allow data connection ports. Windows Firewall is accessible from Control Panel. Microsoft Azure has a limit of 150 open ports. For FileCatalyst, we will configure 70 ports for file transfers. Data Ports will need to be opened for both TCP and UDP.

  2. Create a folder on your local computer called c:\AzureScripts.

  3. PowerShell Prerequisites:
    1. Change your working directory to the AzureScripts location.
    2. Download and install the Windows PowerShell and Azure command-line interface tools from Azure PowerShell Web Installer. (http://go.microsoft.com/fwlink/p/?linkid=320376&clcid=0x409)
    3. Open Windows Azure PowerShell application. You may have a Windows PowerShell installed. Do not use PowerShell that is shipped with Windows as it does not have the Azure libraries. Run the following commands:

      Add-AzureAccount

      This will open a dialog for you to sign in to the Azure Portal.

      Get-AzurePublishSettingsFile

      When your browser opens, a credentials.publishsettings file will download to your default download directory.

  4. Opening ports on Microsoft Azure using PowerShell with Azure Libraries.
    At first setup, you will not be able to execute scripts in PowerShell scripts. In order to run PowerShell scripts, run the following command:

    Set-ExecutionPolicy RemoteSigned

  5. Open the ports using PowerShell:
    1. Create a folder on your local computer called C:\AzureScripts or change your working directory to it if the folder exists.
    2. Copy the publish profile settings file you downloaded in prerequisite 3c into this folder.
    3. Download and copy the AddFCPortsToAzureFirewall.ps1 and FCPorts.csv files from the supporting assets archive included in this document to the AzureScripts folder.
    4. Edit the AddFCPortsToAzureFirewall.ps1 using a text editor and enter the appropriate information under Get-AzureVM -ServiceName [YOUR_INSTANCE_NAME].
    5. Save the file once you have made your changes.
    6. Open Windows Azure PowerShell application. 
    7. Change the working directory to the AzureScripts folder.
    8. Run the AddFCPortsToAzureFirewall.ps1 file.
    9. This should add all the ports needed by FC to your virtual instance.

 

Overview

This guide will provide a quick walkthrough on launching your own FileCatalyst Server and licensing it on an Azure instance.

Environment

Ubuntu 16.04
FileCatalyst Server v3.7.2

Deployment Guide

Once you have entered the required information (username, password, network information and payment details) to set up an instance on the Azure Portal you will see that your instance will be built and available for use on the Azure Dashboard. Please use the following steps to complete the deployment of the FileCatalyst Server:

  1. SSH into the Linux using the username ubuntu and either the password or SSH Key.

  2. Sudo to the root user:

    sudo -i

  3. Change your working directory so that you are in the FileCatalyst Server installation path using:

     cd /opt/utechsoft/server 

  4. Once you are in, you will need to stop the FileCatalyst Server service if it is running. 

    service fcserver stop

  5. (Optional) The default admin password is: movefilesfast

    To change the Remote Administration password run the following command:

    java -jar FileCatalystServer.jar -passwdadmin

    The output should look like this:



  6. The next step is to install a license key on the FileCatalyst Server.

  7. Set execute permissions on the launch scripts. Make sure your current working directory is still /opt/utechsoft/server/. Run the following command to set the permissions:

    chmod u+x *.sh

  8. Run ./fc_server_console.sh and look for the Request String line: 



    Send the request string from your console output to your FileCatalyst Sales Representative. They will provide you with a key. If you do not have a FileCatalyst Sales Rep, you can email [email protected] with your request string.

  9. Now stop the FileCatalyst Server using the following command:

    ./fc_server_shutdown.sh

  10. Install the license key on the FileCatalyst Server. 

    Edit fcconf.conf, enter the licensing information after the equal sign.

    vi fcconf.conf

    ## License key
    FCServer.server.config.license=<Your License Key>

  11.  Save your changes and start the FileCatalyst Server service using this command:

    service fcserver start

  12. (Optional) Verify that the service launched properly using the following command service fcserver status. Your output should look like:



  13. You can now use the FileCatalyst Server Remote Admin client to Administer the Server. Contact your FileCatalyst Sales Rep for download access. 

  14. In order to perform transfers and to get listings, you will need to enable IP Masquerade on the FileCatalyst Server and set it to the Public IP. (Please see attachment at the bottom of this page)
    To enable this you can do the following:
    1. Open the Server Remote Admin Application.

    2. Select Advanced on the left-hand side.

    3. Check the box to Enable Masquerade Address.

    4. In the address field, enter the Public IP. This is not the IP of the machine running the FileCatalyst Server. If the network device acts as a gateway between your network and the public internet, you can find the public internet address quite easily by browsing from any machine to this site: http://whatismyip.com 
      Alternatively, you can check on your Azure Dashboard for the Public IP.

    5. Hit Apply


Note:

Quick Start Guide: How to add External File System Storage on  the FileCatalyst Server

Overview

Every instance that is deployed on Amazon EC2 must have Firewall and specific ports configured. By default, most of the ports that are needed are not open for TCP or UDP connections. The FileCatalyst Server, FileCatalyst Workflow, and FileCatalyst Webmail deployments all need to have their respective ports opened for connectivity and data transfer.

This article will walk you through a typical security group setup for an Amazon EC2 instance.

The default ports for FileCatalyst Direct are:

  • Port 21 for TCP.
    This is used as the communication channel. Port 21 is a default specified in the FileCatalyst Server and is not secure. You can change this as long as both FileCatalyst Server and Client Applications are using the same port.

  • Port 22 for TCP.
    This port is used for SSH connections.

  • Port 990 for TCP.
    This Port is secured over SSL and is also used as the communication channel. The default value of 990 can also be changed in the FileCatalyst Server Remote Admin Application.

  • Port range 8000-8999 for TCP and UDP.
    Some firewalls and NAT devices require setting up 2 separate rules and others allow you to specify TCP and UDP. These ports are used to transfer the Data to and from the FileCatalyst Server and is commonly referred to as the Data Channel. 
  • Port 12400 for TCP.
    This is the Remote Admin Port. This port is exclusive to the FileCatalyst Server Remote Admin Application.

  • Port 12480 for TCP.
    The internal Web Server uses this port to broadcast all communications. The Admin Applet, Link, and Servlet are hosted from this Web Server.

The default ports for FileCatalyst Workflow/Webmail are:

  • Port 80 for TCP.
    HTTP inbound connections are accepted by the Tomcat Web Server on this port. 
  • Port 443 for TCP.
    HTTPS connections and secured communication to the Tomcat Web Server use this port. 

 

Environment

FileCatalyst Direct Suite v3.5 and later.

FileCatalyst Workflow v4.9.5 and later.

FileCatalyst Webmail v4.9.4 and later.

Linux and Windows Environments.

 

Resolution

 

  1. Log into your AWS Console. Click on Security Groups on the left-hand side.



  2. Click on the Create Security Group button, see the attached illustration below.



  3. Specify the Security Group Name and Description.



  4. Hit Add Rule to add your first port. Here is an example of adding a single port 21 on TCP for a connection originating from anywhere.



  5. This is an example of how to add a range of ports. We have added the FileCatalyst Data Port range for both TCP and UDP.




  6. Once all your Firewall Rules have been added, hit the Create button.

  7. Using the Security Group Name, you can add this of Firewall Rules to your EC2 Instance.
Note:

Quick Start Guide: How to add External File System Storage on the FileCatalyst Server

Environment

Ubuntu 14.04 on AWS EC2.

FileCatalyst Direct Server v3.7.2 Build 6 and newer.


Deployment Guide

From the AWS Marketplace search for FileCatalyst and from the results select “FileCatalyst Direct Server Hourly Billing”.

  1. To create and launch an instance click on Continue to Subscribe. You will need to have an AWS Account to continue.

    Use the 1-Click Launch option to begin your deployment. It is fairly easy to setup and most of our recommended settings are displayed here for you to select and modify:



  2. If there is more than one version of the FileCatalyst Direct Server available you will be able to access it from the Version menu. You can view the Release Date of the software on the right of your selection:


    Please note that this will spin up FileCatalyst in an Ubuntu OS. We are going to use v3.7.2 build 6 for this document.

  3. When using the 1-Click Launch option, AWS selects a Region for you, however, if you would like to change the location of your EC2 instance you can modify the selection by using the drop-down list:



  4. Our software has a specific set of requirements for installation and deployment. We have provided a list of compatible instances that you can use to deploy your FileCatalyst Server which is compatible with this AMI. The EC2 instance specifications will be displayed once you make a selection:


    The instance size determines how much bandwidth the OS is allocated by AWS and in turn, the license limit applied to the FileCatalyst Server. Here is a table that shows you the FileCatalyst License bandwidth limit

    Instance Size Bandwidth License
    Large 500Mbps
    XLarge 750Mbps
    2XLarge 1Gbps
    4XLarge 2Gbps
    10XLarge 5Gbps
    16XLarge 10Gbps

    Note: The maximum speed achieved depends on a number of factors, disk speed, networking options etc. Contact support for additional assistance when trying to achieve high speeds.
  5. Networking options are preset in this installation. You can either use the preset values under the VPC Settings tab or create your own VPC and Subnet(s). Please make sure your VPC has connectivity from the outside.



    Please refer to AWS VPC Guide for more information. These settings can be modified after you launch the instance.

  6. Inbound and Outbound Firewall Rules will need to be added so that you can have traffic and data flow in and out of your deployment. We have already created some firewall rules for you based on our default configurations. We recommend that you start here, this will allow you to get up and running fast and as with any settings in the AWS platform they can be changed at a later date. Please select “Create new based on seller settings”:



  7. Create a key pair through your EC2 Console to access the Ubuntu OS through PuTTY. Please click on the link to proceed on the deployment page:


    After your browser is refreshed you will be able to view your newly created Key Pair:


    Check your browsers download location for the PEM file that was downloaded.

  8. To launch your instance you will need to accept the charges, terms and the EULA:


  9. From our EC2 Console connect to the instance using PuTTY (If on Windows) or using any SSH client. Right click on your instance and hit connect. 

    Use this guide if on Windows on Connecting to Your Linux Instance from Windows Using PuTTY

  10. On your first connection, the FileCatalyst Server will already be installed, licensed and running. You will need to enable the Masquerade feature in the FileCatalyst Server so that external clients can connect to the deployment using the Public IP.
    In the PuTTY terminal look inside /home/ubuntu/ for a README.txt. This file will contain instructions and credentials which you can use to connect to the FileCatalyst Server.

    You can access the Download Portal or choose FileCatalyst Server Admin for your OS:

    MacOSX v3.7.2 build 6 package installer
    Windows v3.7.2 build 6 executable installer 
    Linux v3.7.2 build 6 zip package
    Contact [email protected] for download credentials. Please make sure the build is v3.7.2 Build 6 when downloading the Server Admin.



  11. Open your FileCatalyst Server Remote Admin and click on the Advanced tab. In the first row, you will see the Network tab, click on it.
    Locate the IP Settings section and Enable Masquerade Address. Enter your Public IPv4 address in the Masquerade Address field and hit Apply.



    This step will allow the FileCatalyst Server to broadcast the Public IP of the machine rather than the Internal IP.
Note:

Quick Start Guide: How to add External File System Storage on  the FileCatalyst Server

Overview

This guide will provide a quick walkthrough on launching your own FileCatalyst Server Per Hour Billing instance.

Environment

Ubuntu 16.04
FileCatalyst Server v3.7.2

Deployment Guide

Once you have setup the FileCatalyst Direct Server Per Hour Billing from the Azure Marketplace you can use the following steps to get your deployment online:

  1. Using the link above in the Azure Marketplace, click on Get It Now to begin your subscription. You will be required login to your Azure account.



  2. Once you are logged in you can commence the deployment process by clicking create:



  3. In the basic configuration tab, you will need to specify connection details and a connecting username. For this article, we have used ubuntu as the username and specified a password. You can choose the options that fit your needs. Hit Ok to continue to the next tab.



  4. In the next step, you will configure the type of instance you would like to use. You will need to choose the best VM option depending on the amount of data (number of files and total size), number of simultaneous connections, compression settings and other applications that are running on the machine. You can reference our System Requirements and configure an instance you need.

  5. Once you have configured any additional options and accepted the terms and agreements your instance will be created on the Azure Dashboard. Click Connect on your instance to get SSH connection details. 



  6. Connect a Terminal or PuTTY session to your Azure Deployment and sudo to the root user:

    sudo -i
  7. Change your working directory so that you are in the FileCatalyst Server installation path using:

     cd /opt/utechsoft/server 

  8. Set execute permissions on the launch scripts. Make sure your current working directory is still /opt/utechsoft/server/. Run the following command to set the permissions:

    chmod u+x *.sh
  9. Once you are in, you will need to stop the FileCatalyst Server service if it is running. 

    service fcserver stop

  10. (Optional) The default admin password is: movefilesfast

    To change the Remote Administration password run the following command:

    java -jar FileCatalystServer.jar -passwdadmin

    The output should look like this:



  11. Start the FileCatalyst Server service using this command:

    service fcserver start

  12. The FileCatalyst Server is now running in headless mode. You can administer the Server remotely using the FileCatalyst Server Remote Admin tool. 
    You can access the Download Portal or choose FileCatalyst Server Admin for your OS:

    MacOSX v3.7.2 package installer
    Windows v3.7.2 executable installer 
    Linux v3.7.2 zip package

    Contact [email protected] for download credentials. 


  13. Open your FileCatalyst Server Remote Admin and click on the Advanced tab. In the first row, you will see the Network tab, click on it. 
    Locate the IP Settings section and Enable Masquerade Address. Enter your Public IPv4 address in the Masquerade Address field and hit Apply.



    This step will allow the FileCatalyst Server to broadcast the Public IP of the machine rather than the Internal IP. You can obtain the Public IP of your deployment from the Azure Dashboard.
Note:

Quick Start Guide: How to add External File System Storage on  the FileCatalyst Server
Overview

To cancel your FileCatalyst Spaces subscription you will need access to your deployment as the Super Admin. If you have forgotten your username or password please submit a ticket to [email protected] with your account name, subscription ID and company billing address so that we can verify your account. To proceed with the cancellation process use the steps below.

Resolution

  1. Log into your FileCatalyst Spaces deployment as the Super Admin.

  2. From the top menu bar navigate to the Modify Configuration page.

  3. Under the System Configuration section select the Manage your subscription link. 

  4. From the tab list select Subscription Details.

  5. At the bottom of the page, you will see the Cancel Subscription button.


Overview

After the FileCatalyst Server has been installed you may want to use an object storage mount as a primary or alternative storage device. The FileCatalyst Server currently supports Amazon S3 Buckets, Azure Blob Storage, OpenStack Swift3, Backblaze, Google or SMB/CIFS storage mounts.

You can use this article to add the object storage to your FileCatalyst Server deployment.


Environment

FileCatalyst Server v3.7 and newer.

Resolution

There are two methods to add Amazon S3 Buckets, Azure Blob Storage, OpenStack Swift3 or SMB/CIFS mount points on the FileCatalyst Server. You will need to enable the Advanced view to see the File Systems tab.

  1. Adding object storage mounts as External File Systems.

    Using this method will only allow you to use one instance of each object storage available (Amazon S3 Buckets, Azure Blob Storage, OpenStack Swift3 or SMB/CIFS).

    For example, you will now be able to mount 2 two Amazon S3 Buckets. If you already have one Amazon S3 Bucket the option will disappear when trying to add another one.

    If you have a requirement to use multiple object storage points of the same type please see the URL Composition Method.

    • In the FileCatalyst Server Remote Admin navigate to File System tab on the left and click +New.
    • From the drop-down list select the type of object storage you would like to add.



    • Enter your File System Access Key, Secret Key and Endpoint path. Hit the Test button to connect to the object storage.



    • You will now be able to configure the object storage as the Users Home Directory, Virtual File or as a Virtual Folder.

  2. URL Composition Method

    The alternative method is to configure the object storage using the URL Composition method. This allows you to use more than one object storage type. You can use the URL Syntax and add it as a Users Home Directory, Virtual Folder or Virtual File.

    Syntax:

    • Amazon S3:
      • Scheme: s3
      • Default Endpoint: s3.amazonaws.com
      • Full Syntax: s3://<access key>:<secret key>@s3.amazonaws.com/<bucket>/<path>

    • Azure Blob Storage:
      • Scheme: msab
      • Default Endpoint: core.windows.net
      • Full Syntax: msab://<account name>:<account key>@core.windows.net/<container>/<path>

    • OpenSwift Stack3
      • Scheme: swift3
      • Default Endpoint: blank
      • Full Syntax: swift3://<account name>:<account key>@<endpoint>:<port>/<container>/<path>

    • SMB/CIFS
      • Scheme:smb
      • Default Endpoint: blank
      • Full Syntax: smb://<username>:<password>@<host or IP>/<share>/<path>

    • Goolge Cloud Storage 
      • Scheme: gcs
      • Default Endpoint: api.backblaze.com
      • Full Syntax: gcs://<json credentials filename>:<enter any value for password>@googleapis.com/<container>/<path>

    • Backblaze 
      • Scheme: b2
      • Default Endpoint: googleapis.com
      • Full Syntax: b2://<access key>:<secret key>@api.backblaze.com/<bucket>/<path>

For special notes, limitations and other configurations please see our External File Systems Document.

Overview

The FileCatalyst Suite of products can leverage cloud resources supplied by Amazon AWS. Using EC2 Instances, users are able to create and deploy our software on many different versions of Windows and Linux Operating Systems. You will need to consult Amazon AWS for their Cloud Services Pricing.

The products in the FileCatalyst Direct Suite can be downloaded directly from our Download Page. To access the page, you will need credentials which can be obtained from your FileCatalyst Sales Representative or the FileCatalyst Support Team. The FileCatalyst Direct Download Page can be accessed through this link: http://filecatalyst.software/fc-direct-download.html

The following guide will walk you through the basic setup of an AWS EC2 Instance, the configuration of security and network groups and the deployment of FileCatalyst Direct.

Environment

FileCatalyst Direct Suite v3.6 and later.

Amazon AWS EC2 Instances.

Resolution

Use the following steps to ensure that you have full connectivity in and out of your EC2 Instance. The following steps may redirect you to other guides, please complete them in the order they appear in this section.  

Some of the links below will require credentials to access the respective material. If you do not have these credentials please contact your FileCatalyst Sales Representative or the FileCatalyst Support Team.

  1. Choosing the right EC2 Instance and Operating System 

    Based on the System Requirements (http://filecatalyst.com/resources/system-requirements/), you can choose the EC2 Instance that fits the needs of your deployment.  When prompted to select the architecture type please select "64-bit (x86)". Using the "64-bit (Arm)" option will not launch the Server properly.
  2. Security Groups and Network Configuration

    You can use the following guide on FileCatalyst Amazon EC2 Port Configuration and Security Groups Guide: http://support.filecatalyst.com/index.php?/Knowledgebase/Article/View/263/0/firewall-and-port-configuration-for-amazon-ec2-instances-using-security-groups

    It is very important that the network is properly configured so that you do not encounter any issues that are firewall related when transferring data in or out of Amazon. 

  3. Installation Instructions 

    Once you have downloaded the respective application you would like to deploy to your EC2 Instance, you can use one of the following Quickstart Guides to install your FileCatalyst Application:

Notes:


There are other common articles that will be useful in customizing your deployment. You can access them using the links below:

In the External File Systems document, there is a list of limitations when using Cloud Storage (S3 buckets) which are imposed by Amazon. You can view them here: http://filecatalyst.software/download/filesFCDirect/current/documentation/server/efs.html#implementationNotes

 

Overview

This guide will provide a quick walkthrough on launching your own FileCatalyst Server and licensing it on an Amazon EC2 instance.

Environment

Amazon Linux Amazon Linux - 64-bit Amazon Machine Image
FileCatalyst Server v3.8

Deployment Guide

Launching FileCatalyst Server from the AWS Marketplace.

  • Select the version of the FileCatalyst Server you would like to use. We recommend using the option with the latest Release Date:

  • Choose the Region that you would like to use from the drop-down list.



  • Skip ahead one section and select the VPC Settings you would like to use.

  • When initially deploying the FileCatalyst Server, we strongly recommend that you use the preconfigured Security Group called "Create new based on seller settings". You will be able to modify these settings on your EC2 dashboard later.

  • To connect to the machine you will need a KeyPair. If there is an existing KeyPair you would like to use select it from the drop-down list.

  • Review the rest of your settings and Machine connection information on the "Launch this software" page and click on Launch at the bottom. 



Connecting to your FileCatalyst Server

  • From your EC2 dashboard, you will be able to see the instances that you have currently active. When the instance has completed set up (Status checks 2/2), select it and click on the "Connect" button at the top. This will show you a pop up on how to connect to your instance using PuTTY.


Amazon has provided documentation to assist with your connection to the Ubuntu deployment here: https://docs.aws.amazon.com/console/ec2/instances/connect/docs

Getting a license key

  • Connect to the FileCatalyst Server using PuTTY or a Terminal. Switch to the elevated root user using:

    sudo su

  • Change your working directory so that you are in the FileCatalyst Server installation path by executing:

    cd /opt/utechsoft/server

  • Once you are in the folder, you will need to stop the FileCatalyst Server service if it is running.

    service fcserver stop

    Your expected output should be:



  • Set execute permissions on the launch scripts in the installation folder. Make sure your current working directory is still /opt/utechsoft/server/. Run the following command to set the permissions:

    chmod u+x *.sh

  • The next step is to install a license key on the FileCatalyst Server. Run ./fc_server_console.sh and the FileCatalyst Server will attempt to start up. At this point, a request string will be shown:



    Send the request string to your Sales Rep at FileCatalyst indicating what type of license you would like and how many concurrent connections you need. They will send you a key with the appropriate features enabled. Please copy and paste the Request String. Taking a screen capture of the request string may delay you getting a License key. 

    If you do not have the contact for a Sales Rep please send the Request String to [email protected]

Applying the license key

  • Make sure your FileCatalyst Server is off before you proceed. You can run ps -ef | grep java in the terminal and make sure no instance is running. If you do see that there is an instance running please stop the application.

  • Under /opt/utechsoft/server directory, edit fcconf.conf in a text editor. Paste your license key you received after the = sign:

    ## License key

    FCServer.server.config.license=<Enter Key Here>

  • Save the file.

Recommended: Change the Remote Admin Password

  • To change the Remote Administration password run the following command from /opt/utechsoft/server:

    java -jar FileCatalystServer.jar -passwdadmin

    The output should look like:


Launching the FileCatalyst Server

 

Enable Masquerade Address


The FileCatalyst Server itself now needs to know that it's working through a NAT device. To enable this:

  • Open the Server Remote Admin Application.
  • Select Advanced on the left-hand side.
  • Check the box to Enable Masquerade Address.
  • In the address field, enter the Public IP. This is not the IP of the machine running the FileCatalyst Server. If the network device acts as a gateway between your network and the public internet, you can find the public internet address quite easily by browsing from any machine to this site: http://whatismyip.com 
    Alternatively, you can obtain your Public IP (IPv4) from your EC2 instance management console. Do not use your DNS.
  • Hit Apply.



Note:

Quick Start Guide: How to add External File System Storage on the FileCatalyst Server