Skip to main content

Ember Journal

The Ember Journal, sometimes called the Ember transaction log, is a high-performance write-ahead storage system for trading messages that flow into the Ember Order Management System (OMS).

The documentation for the Ember Journal includes the following resources:

  • Ember Journal Deep Dive: Provides an in-depth exploration of the Ember Journal, offering comprehensive insights into its architecture and functionality.
  • Ember Journal Presentation (PPT download): This presentation offers a detailed overview of the Ember Journal.
  • The Journal section in the Configuration Reference document: This section provides guidance on how to configure and customize the Ember Journal to suit specific requirements.
  • Synchronous and asynchronous Journal replication: Information about journal replication in high-availability (HA) setups can be found in the Ember HA documentation.
  • A set of tools for working with the Journal:
    • journal-upgrade - A one-time migration procedure to upgrade the Journal format version.
    • journal-downgrade - An option to restore the Journal format to a pre-upgrade format version.
    • journal-recover - A tool for repairing the Ember Journal in the event of corruption.
    • journal-sequence-fix - A tool for repairing the Ember journal in the event of Journal corruption caused by failed media or disk IO.
    • latency-tool - A tool for real-time monitoring of latency between sent and received FIX messages.
    • counters - Provides a simple CLI interface for viewing Ember performance counters.
    • ember-console-app - A tool that can be used to submit, replace, and cancel orders, as well as halt/resume trading.
    • journal-compress & journal-decompress - Can be used to archive Ember Journal while Ember is running.
    • journal-import - Allows importing the Journal from a backup created in a data warehouse.
    • journal-to-json - Converts Ember Journal from binary to JSON format and back.
    • journal-transform - Can be used to edit the Execution Server journal on a customer site in various special situations.
    • mangle - Can be used to avoid storing clear-text passwords in your configuration files.
    • oms-debugger - Part of the Execution Server diagnostic tools. Designed to troubleshoot order transitions recorded in the system journal by replaying journal messages and examining the state of orders at specific breakpoints.
    • order-debugger - Part of Execution Server diagnostic tools. Designed to troubleshoot order transitions recorded in the system journal by replaying journal messages and examining the state of orders at specific breakpoints.