Lesson 2.3 - Essential Platform Components¶
Dealers do not need to memorize every server detail. They need a practical map of the components that affect daily operation.
Learning Objectives¶
- Explain the role of each major component.
- Identify typical symptoms.
- Locate the correct evidence source.
- Identify the correct owner without changing production settings.
| Component | Dealer needs to know | Common symptom | Evidence to collect |
|---|---|---|---|
| MT4 / MT5 | Main trading platform for accounts, orders and positions | Login issue, order delay, position mismatch | Account, order ID, timestamp, platform status |
| Manager | Daily investigation and account/order review interface | Need to verify account, order, balance or position | Screenshot, journal/log entry, order details |
| Administrator | Configuration and permission control area | Symbol, group, margin or permission concern | Current setting, approved setting, change record |
| Bridge | Transfers orders between the platform and execution venues | Queue build-up, timeout, reject, route delay | Queue, route, latency, reject/timeout metrics |
| Bridge Trade Log | Real-time order-flow view inside the bridge | Large-volume order, short holding time, repeated reject or route anomaly | Order time, symbol, volume, route/match result, order ID |
| Quote Source | Reference quote and quote-quality source | Suspected off-market price, stale quote, wider spread or depth issue | Quote timestamp, response time, spread and depth data |
| Quote System | Price distribution to platform | Stale quote, abnormal spread, missing tick | Bid/ask, spread, quote time, quote contribution |
| Risk Tool | Exposure and risk-control monitoring | Risk alert, temporary control, account condition | Exposure, risk-status usage, alert record, approval |
| Reporting/history | Reports and reconciliation records | Report mismatch or missing trade history | Report range, timezone, account/order records |
How Much Detail Is Enough?¶
A Dealer should be able to explain:
- What the component does.
- What live symptoms point to it.
- Which dashboard, report or log can support the observation.
- Who owns the next action.
A Dealer does not need to independently maintain server architecture or change production configuration.
Practical Training¶
Scenario
The Bridge Trade Log shows several large orders while latency rises on one quote source and XAUUSD spread widens.
What to check
Order time, product, volume, routing or matching result, platform-rule reject reason, quote-source session status and Bridge queue.
Common mistake
Reviewing only one order and missing the repeated pattern within the same time window.
Correct handling
Review order flow, quote-source status and Bridge indicators together. Record confirmed facts and escalate if the combined evidence shows a material execution or quote-quality concern.
Summary¶
A Dealer does not need to memorize the full system architecture. The Dealer should understand each component's role, typical symptoms, evidence source and the owner responsible for the next action.
Completion Criteria¶
- Can explain the key risk or operational objective of this lesson
- Can identify the required systems, data, or evidence to review
- Can describe the correct escalation or handling process
- Can apply the lesson correctly in a supervised scenario