0% found this document useful (0 votes)
52 views

FXCubic Server Architecture Specifications

Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
52 views

FXCubic Server Architecture Specifications

Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

LIQUIDITY INTELLIGENCE

Server Architecture & Specifications

v.2024.07.18

1 s t F l o o r, 3 M o r e L o n d o n R i v e r s i d e , w w w.f xc u b i c . c o m
London SE1 2RE, United Kingdom +44 20 3727 2580
Server Specifications

Recommended Software Requirements


Hardware Specifications (Dependencies)

Dedicated server instead of a VM Microsoft .NET Core Runtime 8.0.6


(x64)
Windows Server 2016 or 2019
Microsoft .NET Core Runtime 8.0.6
CPU: New Gen. 8 core (16 logical cores), 3.5+ GHz (x86)

RAM: 24 GB MT4: Microsoft Visual C++


2015-2019 redistributable package
Storage: 1 TB SSD (x86)
(The bigger the better)

MT5: Microsoft Visual C++


2015-2019 redistributable package
(x64)

Google Chrome

Registered in England. Company No: 10816787 www.fxcubic.com


Plan 1 - Each service on separate servers: MT5 + FXCubic + FixServer

Installation of FixServer service is only required when the broker wants to create
MT5 FXCubic FixServer outgoing FIX API connectors in which they are the maker to other institutions.

Each service on separate servers


- In case MT5 Server goes down, FXCubic Main Server will continue working with MT5 Backup
since MT5 Backup Gateway points out the FXCubic Main. If exists, AccessServer parameter
under Gateway should be checked on a failover case, too.
(MT Backup should be able to reach FXC Main Server with External IP)
- In case FXCubic Main Server goes down, FXCubic Backup switch should be done manually
from MT FXC Gateway by changing the IP Address in Trading Server parameter.
- In case FixServer Main goes down, FixServer Backup Service should be run manually. If FXCubic
and MT are working on Main, then FixServer Backup’s configs should be pointing out MT Main
and FXCubic Main.

Remark: Having MetaTrader, FXCubic and FixServer on separate servers will definitely increase the
performance with high data transmission.

Registered in England. Company No: 10816787 www.fxcubic.com


Plan 1 - Each service on separate servers: MT5 + FXCubic + FixServer

MT5 Server Main MT5 Server Backup

MainTrade
Access Service MainTrade Service History Service Access Service History Backup Service
Backup Service
(started) (started) (started) (started) (started)
(started)

MainTrade Service History Service


(disabled) (disabled)

Port: 16XXX

Port: 16XXX
FXCubic Gateway FXCubic Gateway
(started) (disabled)

Port: 8085 Port: 8085

FixServer Service FXCubic Service Port: 8090 FXCubic Service FixServer Service
(started) Port: 8085 (started) (started) Port: 8085 (disabled)

FixServer Main Server FXCubic Main Server FXCubic Backup Server FixServer Backup Server
Trade Session Port
Quote Session Port

Port: 8090
Port: 8090

FIX API Client

FIX API Client’s Server GUI Client Devices


Plan 2 - Each service on same server : MT5 + FXCubic + FixServer

MT5 FXCubic FixServer

Each service on same server


- In case MT5-FXC Server goes down, FXCubic Backup switch will be done automatically since
Backup MT5’s FXC Gateway has Backup FXCubic’s IP Address in its Trading Server parameter as
“127.0.0.1:8085”. FXC Gateway works on MT History Server. If MT History Backup goes up,
then FXCubic Backup will start working, too.
- And FixServer Backup Service should be run manually.

Remark: Having MetaTrader, FXCubic and FixServer on the same servers might cause low
performance with high data transmission.

Registered in England. Company No: 10816787 www.fxcubic.com


Plan 2 - Each service on same server : MT5 + FXCubic + FixServer

MT5 Main Server

FIX API Client’s Server

Trade Session Port


FixServer Service Access Service MainTrade Service History Service
FIX API Client
(started) (started) (started) (started)
Quote Session Port

Port: 8085

Port: 8085 Port: 16XXX


Port: 8090
FXCubic Service FXCubic Gateway
(started) (started)

GUI Client Devices

MT5 Backup Server


Port: 8090

Port: 8085 MainTrade


FXCubic Service Backup Service
History Backup Service
Port: 8090 (started) (started)
(started)
Port: 8085

MT5 Access Service MT5 MainTrade Service MT5 History Service


(started) (disabled) (disabled)

Port: 16XXX
FixServer Service FXCubic Gateway
(started) (Disabled)
Plan 3 – Each service on separate servers: MT4 + FXCubic + FixServer

MT4 FXCubic FixServer

Each service on separate servers


- In case MT4 Server goes down, FXCubic Main Server will continue working with MT4 Backup
since MT4 Backup Plugin points out the FXCubic Main, too.
(MT Backup should be able to reach FXC Main Server with External IP)
- In case FXCubic Main Server goes down, FXCubic Backup switch should be done manually
from MT4’s FXC Plugin by changing the IP Address in ServiceHost parameter. This change will
require an MT Server Restart.
- In case FixServer Main goes down, FixServer Backup Service should be run manually. If FXCubic
and MT are working on Main, then FixServer Backup’s configs should be pointing out MT Main
and FXCubic Main.

Remark: Having MetaTrader, FXCubic and FixServer on separate servers will definitely increase the
performance with high data transmission.

Registered in England. Company No: 10816787 www.fxcubic.com


Plan 3 – Each service on separate servers: MT4 + FXCubic + FixServer

FIX API Client’s Server FixServer Main Server

Trade Session Port MT4 Main Server


FIX API Client FixServer Service
(started) MT4 Service Watchdog Service
Quote Session Port
(started) (disabled)

Port: 8085

FXCubic Main Server FXCubic Plugin


(loaded)
Port: 8090
Port: 8085
FXCubic Service
(started)
GUI Client Devices

Port: 8090
MT4 Backup Server

FXCubic Service
(started) Port: 8085
Port: 8090 MT4 Service Watchdog Service
FXCubic Backup Server (disabled) (started)

Port: 8085
FXCubic Plugin
(unloaded)

FixServer Service
(disabled)

FixServer Backup Server


Plan 4 - Each service on same server : MT4 + FXCubic + FixServer

MT4 FXCubic FixServer

Each service on same server


- In case MT4-FXCubic Server goes down, FXCubic Backup switch will be done automatically
since Backup MT4’s FXC Plugin has Backup FXC’s IP Address in its Service Host parameter.
FXCubic listens to MT Watchdog service. If MT Backup goes up, then FXC Backup will start
working.
- And FixServer Backup Service should be run manually.

Remark: Having MetaTrader, FXCubic and FixServer on the same server might cause low
performance with high data transmission.

Registered in England. Company No: 10816787 www.fxcubic.com


Plan 4 - Each service on same server : MT4 + FXCubic + FixServer

FIX API Client’s Server MT4 Main Server

Trade Session Port


FIX API Client FixServer Service
(started) MT4 Service Watchdog Service
Quote Session Port
(started) (disabled)

Port: 8085
FXCubic Plugin
Port: 8085 (loaded)
Port: 8090
FXCubic Service
(started)

GUI Client Devices

Port: 8090

Port: 8085
FXCubic Service
Ports: 8090 (started) MT4 Service Watchdog Service
(disabled) (started)
Port: 8085

FXCubic Plugin
(unloaded)

FixServer Service
(started)

MT4 Backup Server


Plan 5 – MT(s) and FXC services on separate servers : MT4 + MT5 + FXCubic + FixServer

MT4 MT5 FXCubic FixServer

MT(s) and FXC services on separate servers


- In case MT5-MT4 Server goes down, FXCubic Main Server will continue working with MT5-
MT4 Backup since MT4 Backup Plugin and MT5 Backup Gateway point out the FXCubic Main.
FixServer Main’s Trade Server config should be changed accordingly.
(MT Backup should be able to reach FXC Main Server with External IP)
- In case FXCubic Main Server goes down, FXCubic Backup switch should be done manually
from MTs’ FXC Gateway and Plugin by changing the IP Address in ServiceHost/Trading Server
parameter. FixServer Main’s API Server config should be changed accordingly.
- In case FixServer Main goes down, FixServer Backup Service should be run manually. If FXCubic
and MT are working on Main, then FixServer Backup configs should be pointing out MT Main
and FXCubic Main.

Remark: Having MetaTrader, FXCubic and FixServer on separate servers will definitely increase the
performance with high data transmission.

Registered in England. Company No: 10816787 www.fxcubic.com


Plan 5 – MT(s) and FXC services on separate servers : MT4 + MT5 + FXCubic + FixServer

MT5 Main Server MT5 Backup Server

Access Service MainTrade Service History Service MainTrade


Access Service History Backup Service
(started) (started) (started) Backup Service
(started) (started)
(started)

MainTrade Service History Service


(disabled) (disabled)
Port: 16XXX

FXCubic Gateway FXCubic Gateway


(started) (disabled) Port: 16XXX

MT4 Main Server MT4 Backup Server

Watchdog Service MT4 Service Watchdog Service MT4 Service


(disabled) (started) (started) (disabled)

FXCubic Plugin FXCubic Plugin


(loaded) (unloaded)

Port: 8085 Port: 8085

Port: 8090
FixServer Service FXCubic Service FXCubic Service FixServer Service
(started) Port: 8085 (started) (started) Port: 8085 (disabled)

FixServer Main Server FXCubic Main Server FXCubic Backup Server FixServer Backup Server

Quote Session Port Trade Session Port Port: 8090 Port: 8090

FIX API Client

FIX API Client’s Server GUI Client Devices


Port communications

In order to make everything work, connections via these ports should be


made.

MainTrade Server → History Server MT MainTrade Server should be whitelisted from MT History Server on port; 16385
(Gateway Server’s default, it may differs)

GUI Client Devices → FXCubic Web GUI Personal Computer should be whitelisted from FXCubic Server on port(s); 8090
8090 will be used to reach FXCubic GUI on browser. e.g.: 192.168.10.1:8090

MetaTrader Server should be whitelisted from FXCubic Server on port(s); 8085


MetaTrader → FXCubic
This port will be used by Plugin/Gateway.

FXCubic Main should be whitelisted from FXCubic Backup on port(s); 8090


FXCubic Main → FXCubic Backup
These ports will be used to get FXCubic Backup synchronized with FXCubic Main. FXCubic
Backup should be whitelisted from FXCubic Main on these ports, too.

FXCubic Main → LP(s) FXCubic’s IP address should be whitelisted from LP side. Please make sure that telnet is
successful from FXCubic Server to LP’s IP address.

FXCubic Backup → LP(s) FXCubic Backup Server’s IP address should be whitelisted from LP side, too. Please make
sure that telnet is successful from FXCubic Backup Server to LP’s IP address.

Registered in England. Company No: 10816787 www.fxcubic.com


Port communications

In order to make everything work, connections via these ports should be


made.

FixServer → FXCubic FixServer should be whitelisted from FXCubic on port(s); 8085


This port will be used to get FixServer connected to FXCubic.

FixServer → MT5 Access Server FixServer should be whitelisted from MT Access Server on port(s); 443 (access server’s
default for accepting connections)
This port will be used to get FixServer connected to MetaTrader.

FIX API Client → FixServer FixClient’s IP address should be whitelisted from FixServer Server on port(s); Trade Session
Port, Quote Session Port
These ports will be used to give liquidity and get trade orders. Ports are defined under
FixServer UI differently for each FixClient.

FXCubic → FXC License Server Your FXCubic software should be get reached to FXCubic License Server.
FXCubic License Server: licensing.fxcubic.net

FixServer → FXC License Server Your FixServer software should be get reached to FXCubic License Server.
FXCubic License Server: licensing.fxcubic.net

Registered in England. Company No: 10816787 www.fxcubic.com


Backup & Test & Demo

FXCubic Backup
- FXCubic Team does strongly recommend to have a FXCubic Backup server. FXCubic will work without any interruption on a failover
case.

- FXCubic Main and Backup are synchronized real-time.

- If; FXCubic Main Server sits on separate server and this server goes down, then IP Address on MT Plugin/Gateway should be
switched to Backup FXCubic’s IP.

- If; FXCubic Main Server sits on the same server with MT and this server goes down, then it will automatically switch to Backup.

FXCubic Test
- FXCubic is a dynamic software which is continuously under development with new features. So a dedicated test server will help
you to test the new features.
- You can create scenarios and optimize them in Test FXCubic, then implement the same logic on Live after you made sure that it is
the most profitable one.
- Test FXCubic’s Backup could be set up and the backup switching can be tested, too.

FXCubic Demo
- Using a Demo FXCubic could be an extra effort in terms of server and management. Instead, you can feed prices from your Live MT
into Demo MT and set demo accounts as Auto Execution for their trades.

Remark: FXCubic also recommends a time synchronization tool to be used on your servers such like NetTime.

Registered in England. Company No: 10816787 www.fxcubic.com


DISCLAIMER

• Installation of FixServer service is only required when the broker wants to create outgoing FIX API
connectors in which they are the maker to other institutions.
• FXCubic and FixServer softwares are completely sitting on the customer’s servers and networks.
• FXCubic cannot be held responsible for any security or network issues.

Any questions could be forwarded to FXCubic Support Team in working hours (UK Time).

Only emergency requests will be responded out of working hours.

Contact Us

Registered in England. Company No: 10816787 www.fxcubic.com

You might also like