Components of FileFlex Enterprise Platform

FileFlex enterprise platform consists of 3 main components.

1. The FileFlex enterprise server
2. The FileFlex data connector agent
3. The FileFlex end-user application

Introduction

FileFlex enterprise server can be deployed as a cluster with a minimum requirement of 4 virtual machines. This allows companies with a high volume of users accessing the system to plan and deploy a highly available FileFlex solution. 

Scope

The scope of this document is to make the enterprise server component of the platform highly available. 

Planning & Requirements

The deployment of the cluster requires some preparation work. Listed below are some of the key requirements; actual provisioning of these required items will happen in sequence during the cluster deployment. 

Note on Installation Steps

Once you have the domain names planned you can go ahead with the next installation steps.

We will follow a logical sequence of steps but based on Cloud Service Providers (CSPs) like Azure, AWS Google Cloud etc. the Steps Sequence will have additional steps in their relevant sections.

1. Provision IPs
2. Provision VMs
3. Setup DNS

Installing High Availability cluster on AWS

Login to AWS Portal at https://console.aws.amazon.com/

STEP: Verify and Enable DNS Attributes

1. Login to https://console.aws.amazon.com/vpc/
2. Navigate to "Your VPCs" from the left menu
3. You may use your existing VPC or provision a separate one for the purpose
4. Verify that DNS resolution and DNS hostnames attributes of the virtual private cloud (VPC) must be enabled as explained here

STEP: Create IPs

Create 4 (FOUR) separate Elastic IPs ("Network & Security" -> "Elastic IPs" -> "Allocate Elastic IP address")

STEP: Create Security Group

Navigate to "Security Groups" -> "Create security group"

1. Allow the following "Custom TCP" ports for "inbound rules": 4007, 4010, 4011, 9443, 443, 22, 80, 61616, 27017, 7443 from "Anywhere"
2. Allow the "All TCP" Type to "Anywhere" for outbound and associate it with your VPC:
3. Save with "Create security group"

STEP: Spool up VM instances

Create a VM from the latest image ("AMIs" -> "Images"). 

Find the FileFlex image

If you followed STEP 6.1 to link AWS id in FileFlex Enterprise Partner Portal then you will find the FileFlex image by selecting Private Images in the filter

In order to start the process, select the image and click "Launch"

Deploy the VM

Choose an instance type with at least 4GiB of Memory with 2 cores this is the baseline:

Choose the number of instances

Type in 4 to provision the number of instances we need.

Click all the way to the Configure Security Group

Assign security group

Navigate to the "6. Configure Security Group" tab, 

1. Click on "Select an existing security group" from "Assign a security group" and
2. Click on the security group you've previously created to select it
3. Click "Review and Launch" to proceed with the review
4. Verify that everything is as it should be, and click the blue "Launch" button at the bottom right.

Create a key pair to access server instances

You will be presented with the key pair specification dialogue next

1. If you already have a key pair, you can select it from the list. If you do not, you will need to create one to be able to access your instance. Choose "Create a new key pair" from the first dropdown, and enter a name for the keypair.
2. Click on the blue "Launch Instances" button at the bottom right of the dialogue to proceed.

Click the blue "View Instances" button at the bottom right. You will see a list of your running instance, including the newly spooled up instance

STEP: Assign Elastic IPs to Instances

1. Go to "Network & Security" -> "Elastic IPs"
2. Select each of the elastic IPs you've already allocated and associate them with the running instances. NOTE: you will do this four times, one IP per instance

STEP: Copy the private IPs

1. Now go back to the running instances
2. Select the "Instance ID" of each of the machines (one by one)
3. Copy and note somewhere the Private IP addresses:

STEP: Create Hosted Zones

Route 53 is Amazon's DNS service that will be used to route traffic internally.

1. Go to Route53 -> "Hosted Zones" (https://console.aws.amazon.com/route53/v2/hostedzones)
2. Select " Create hosted zone" on the right side of the page to create a reverse DNS zone
   a. For the "Domain name" add the corresponding XXX.in-addr.arpa record, depending on your configuration. we used 31.172.in-addr.arpa
   b. Select "Private hosted zone" for "Type"
   c. Select your Region and VPC ID from "VPCs to associate with the hosted zone". Confirm with "Create hosted zone"

STEP: Create PTR Record (reverse zones) Per Instance

From the "Hosted zone details" select "Create record":

From the "Quick create record" window add a record for each of the nodes by using the private IPs which were copied above.

Fill the details as follows:
1. The reverse IP for "Record name"
2. PTR as "Record type"
3. The actual hostname for the "Value"

4. Click create record

5. Add a PTR record for each of the machines (total of 4)

In the end, the hosted zone should look similar to the following:

Here we created one PTR record per machine

STEP: Create Forward Zones per Instance

1. Go back to "Route53" -> "Hosted zones" in order to create a forward zone
   a. Use the main domain you will use for "Domain name"
   b. Again, use "Private hosted zone" as type
   c. Select the appropriate "Region" and "VPC ID"
   Confirm with "Create hosted zone"
2. Select "Create record" for each of the 4 machines
   a. Add the subdomain for "Record name"
   b. Select "A" as "Record type"
   c. Enter the internal IP for "Value"
3. Add an A record for each of the machines (total of 4). In the end, the hosted zone should look similar to:

STEP: Setup External Domain DNS

Depending on where you are hosting you existing domain, it is time to configure A records pointing to external IPs assigned to the Instances.

1. Add an A record for each Instance
2. Use One IP as configured above making sure you are using the right IP of each instance

For example the A records for our sample domain setup looks like this on Network Solutions DNS manager:

STEP: Start installing Primary FileFlex Server

Connect with ssh to each of the machines and run the setup process. 

Login using the default password (you will be prompted to change this later in the setup)

Username: sadmin

Password: Q!w2e3r4

As soon as you log in to the VM you will be presented with the following screen.

STEP 1 Choose the language of choice 

STEP 2 Choose "Primary or single machine"

STEP 3  Choose a password for sadmin account

STEP 4  SKIP this step

STEP 5 Enter the Primary domain that will be used to access the FileFlex server by end-users

STEP 6 WAIT!!!!!! this will take some time.....

PRIMARY Server is ready to be configured. Click Reboot

STEP: Start installing Secondary FileFlex Server

SSH into the Secondary Machines in sequence to start adding them to the cluster i.e. VM#2 then #3 and then #4 

Login using the default password (you will be prompted to change this later in the setup)

Username: sadmin

Password: Q!w2e3r4

You will see the same initial screen on the first access

STEP 1 Choose language of choice

STEP 2 Choose Secondary machine in a cluster option

STEP 3  Choose a password for sadmin 

STEP 4  SKIP this step

STEP 5 Enter the proper Secondary domain for the designated machine here

STEP 6 Now the VM is ready to be added to the Cluster, its time to open your web browser to access the Primary Machine

NOTE: IF this happens and the timer expires after 30 minutes then run the following command

sudo /opt/ffs/setup.sh

STEP: Start configuring the FileFlex Server Cluster

STEP 1 Now you can access this machine using the hostname you have configured for the primary server at: 

EXAMPLE: https://fileflex.orionwebware.net:9443 

STEP 2 Login using the sadmin username and password that you used for the primary machine.

STEP 3 Prompt to enter the FileFlex deployment ID and FileFlex deployment keys and click Verify 

STEP 4  Choose "Configure a high-availability cluster" option and click next

STEP 5 Setup your Global Admin credentials for Policy and Users management console

STEP 6 Almost ready to start adding machines.

STEP 7 Click OK to start

The setup will take few minutes to configure the Primary Server

STEP 8 When prompted enter the hostname of the machine awaiting addition to the cluster and sadmin password for that machine 

NOTE: Primary Server will setup trust with secondary servers and automatically assign their roles in the cluster.

NOTE: the screen will update on the secondary machine as follows

STEP 9 And the Primary server keeps the setup going awaiting the next secondary servers

STEP 10 Follow the ok and Yes prompts

STEP 11 Once the setup completes. Some services may be stopped. Simply select them and click start icon to start them.

STEP 12 Finalize the setup in the control panel

1. Setup mail server used to send notifications etc.
2. Setup SSL Certificate (HELP on SSL Certificate Automated Installation)