Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. FIXICC H2 machine:
    1. RHEL 7 / RHEL 8
    2. OpenJDK 1.8 
    3. (Optional since FIXICC H2 23Q1 release) Consul agent in client mode
  2. FIXEdge Cpp/Java machine:
    1. (Optional since FIXICC H2 23Q1 release) Consul agent in client mode
  3. On the network:
    1. PostgreSQL Database or HSQL Database (since FIXICC H2 23Q1 release):
      1. 1 user with DDL privileges ( to run the database migration , can also be used to or run normal FIXICC H2 operation)
      2. (Optional) 1 user without DDL privileges ( to run normal FIXICC H2 operation)
    2. (Optional since FIXICC H2 23Q1 release) Consul cluster (- can be deployed on the same machines as FIXEdge Cpp/Java or FIXICC H2)
  4. Client workstations:
    1. Chrome browser

Pre-

...

configuration

Before you start working with the FIXICC H2, install and configure the FIX Engine and Consul application.

...

For non-production use, you can run the Consul in developer mode with the command: 

Code Block
consul agent -dev

...

For production use - please follow the link.

To configure the encrypted connection from FIXICC H2 to the Consul on the Consul side, please follow the link.

FIXICC H2 without Consul

Info

The ability to use FIXICC H2 without Consul is available since FIXICC H2 23Q1 release.

FIXICC H2 configuration

  • The fixicch2.consulEnabled property must be set to 'false' in the local.app.properties configuration file.

Example:

Code Block
languagejava
titlelocal.app.properties
###############################################################################
#                                  Other                                      #
###############################################################################
 
cuba.rest.anonymousEnabled=true
cuba.anonymousLogin=anonymous
 
cuba.dbmsType = postgres
cuba.dataSourceProvider = application
cuba.dataSource.username = cuba
cuba.dataSource.password = cuba
cuba.dataSource.dbName = fixicch2
cuba.dataSource.host = localhost
cuba.dataSource.port = 5432
 
fixicch2.fixServerType = all
 
fixicch2.prometheus.host = localhost
 
fixicch2.consulEnabled=false
  • The following actions must be performed to connect to FIXEdge Java or FIXEdge C++ and FIXEye-Agent:
    • Run FIXICC H2 and log in.
    • Navigate to the Configuration Show all servers in the left navigation menu. The Servers page will be opened.
    • Click the Add button. The Server editor page will be opened.
    • Enter Server Name, Type, IP, Admin Port and FIX Port for the Server and IP and Port for FIXEye Agent. Click the OK button.

    Image Added 

Info

Admin Port for FIXEdge Java server is set to '9010', and FIX Port is set to '8911' by default.

Admin Port for FIXEdge C++ server is set to '8903', and FIX Port is set to '8901' by default. 

Port for FIXEye Agent is usually set to '8882'.

FIXEdge Java configuration

The following properties must be defined in the fixedge.properties file:

Code Block
languagejava
titlefixedge.properties
service.discovery.enabled=false
 
server.useFixicch2ConfigManager=true
 
fixicch2.enable=true
 
# Fixicch2 REST API to load fix session and schedules configs and to subscribe on session and schedules changes
fixicch2.url=<fixicc_h2_url>

FIXEdge C++ configuration

The following properties must be defined in the FIXEdge.properties file:

Code Block
languagecpp
titleFIXEdge.properties
Components.Service.FIXICCH2 = configuration-service
Components.Service.FIXICCH2.Host = <host>
Components.Service.FIXICCH2.Port = 8080
Components.Service.FIXICCH2.ReconnectInterval = <some_interval>
 
Components.Component.Configuration = FIXICCH2

FIXEye Agent configuration

The Consul.Enabled property must be set to 'false' in the fixeye-agent.properties file:

Code Block
Consul.Enabled = false

FIXICC H2 settings

You should choose a directory on your workstation for FIXICC H2 files.

...

  1. Deploy FIXEye Agent (version 2.3.0 or higher) by following instruction.

LDAP authentication

To configure the FIXICC H2 authentication via LDAP you can follow the following instruction:

...