Knowledgebase: Pre-Sales
Install and Configure FileCatalyst Server BYOL on Amazon Marketplace
Posted by Elton Carneiro, Last modified by Aly Essa on 27 October 2016 03:25 PM

Launching FileCatalyst Server from the AWS Marketplace.

Visit the FileCatalyst Direct Server link: https://aws.amazon.com/marketplace/pp/B00EPNJGQC/

Click Continue to proceed to launch an instance. 

You have 2 options here. The one we are going to describe is the "1-Click Launch". The other one is the "Launch with EC2 Console" which takes you to the EC2 Console page where you can customize your instance. 

Using the 1-Click Launch

Review the settings on the left. The most important ones are the EC2 Instance Type and KeyPair. The KeyPair is what you will use to log into the instance once it is running. Make sure you have the KeyPair you have specified. If you do not have the KeyPair, you can choose the "Launch with EC2 Console" and you will provided an option to create a new KeyPair. 

The Security groups have been configured to work with FileCatalyst. If you need additional ports open, you can create a duplicate of what FileCatalyst has provided and add additional ports. 

When you are ready, you can click on the "Launch with 1-Click" button located on the right side near the top.

Accept and Launcg

You will be directed to

Thank you for subscribing.

Closing the pop up will take you to

Your Subscription

Wait for instance to launch. When your instance is ready, you will receive an email indicating so.

Subscription Ready

If your my subscription page still shows the image as pending, refresh the my subscriptions page. You should see the following:

Subscription Ready 

Click on the Manage in AWS Console link to go to the EC2 Console page. 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. 

Connect to your instance

Copy the ssh command and paste it in a UNIX terminal or open up SSH client (Windows) and log in using the private key specified during launch. Note: Here is a guide on how to use the PEM file when using PuTTy. http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html

Once logged into the machine, switch to root (sudo su). All commands needed for FileCatalyst Server on this instance need to be run as root. 
cd to /opt/utechsoft/server

Getting a license key

run ./fc_server_console.sh and the server will attempt to start up. at this point, a request string will be shown. 

Request String

Send the request string to your sales rep at FileCatalyst indicating what type of license you would like and how many concurrent connection 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. 

Applying the license key

Under /opt/utechsoft/server, edit fcconf.conf and set the license key you received after the = sign
## License key
FCServer.server.config.license=

save the file.

Enabling the remote administration client

From the /opt/utechsoft/server directory prompt, run: java -jar FileCatalystServer.jar -passwdadmin
This will prompt you for a new password for the remote admin. Enter a password.

Next, edit the fcconf.conf file and look for the following line:
FCServer.server.config.remote.admin.enabled=false.
change it to:
FCServer.server.config.remote.admin.enabled=true

Save the file. You have now enabled the remote admin with a password. The username is admin. You can change this in the fcconf.conf file or use the UI once you log in. 

Launching the FileCatalyst Server

To launch the server run: ./fc_server_console.sh - this will launch the server. You can now use the remote administration tool to administer the server. 

Here is a link that describes how to connect from the remote admin: http://support.filecatalyst.com/index.php?/Knowledgebase/Article/View/67/0/using-the-filecatalyst-remote-admin-to-connect-to-a-filecatalyst-server-running-on-headless-linux-command-line-mode-only-no-gui



Attachments