Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

FIX Engine

To control the FIX connections with the FIXICC H2, you should install and configure the FIX engine application.

For detailed instructions on the installation and configuration FIXEdge Java please follow this link.

Also, you should set the additional configurations for FIXEdge Java:

NameExample value

Default Value

Description
rest.service.nameREST-AdminAPIemptyThe name of REST service, if it is empty or disabled, REST service will not be available and registered in Service Discovery
rest.service.port9010emptyThe number of REST port, if it is empty or disabled, REST service will not be available and registered in Service Discovery
rest.ssl.cert.path/ssl/cert.pememptyThe path to the SSL certificate, should not be empty to create REST service and register it in Discovery
rest.ssl.key.path/ssl/key.pememptyThe path to the SSL key, should not be empty to create REST service and register it in Discovery
server.nameServerAemptyThe name of the server, if it is not empty, the server will be registered in Discovery by this name. Otherwise, it will not be registered.
protocol.nameFIXemptyThe name of the protocol, used for server registration in Consul
service.discovery.healthcheck.interval10

10

Health check interval (Service Discovery)
service.discovery.attempt.period10000

0

Service Discovery attempt period, milliseconds
fixicch2.urlhttp://10.68.21.181:8080emptyFixicch2 REST API to load fix session configs and to subscribe on session changes
fixicch2.url.prefixhttp

http

Fixicch2 URL prefix if Service Discovery is used to define IP and port
fixicch2.service.discovery.connection.timeout60000

60000

Timeout for attempts to connect to Service Discovery, mc
fixicch2.service.discovery.status.update.timeout10

10

Max time to wait for Service Discovery Fixicc H2 health status update, min
server.useFixicch2ConfigManagertrue

False

Allows to choose the sessionConfigManager and scheduleConfigManager (original or fixicch2)
fixicch2.serviceFIXICC H2

FIXICC-H2

The name of the FIXICC H2 service is used when the fixicch2.url is not set. If it is empty or disabled then the default value (FIXICC-H2) will be used for the connection
fixicch2.reconnect.pause2000

2000

Pause to reconnect to FIXICC H2 URL in case of errors, mc
fixicch2.insecure.connection.enabledtruefalse

If set to true this option disables validation of the TLS certificate provided by FIXICC H2. This allows using self-signed certificates on FIXICC H2 without adding them to a trusted store. This option is primarily useful for QA and development environments. In production environments, it is recommended to turn this option off and use a certificate signed by a trusted authority

consul.hostlocalhostlocalhostThe hostname or IP address of the Consul Agent
server.checkHostlocalhostlocalhostThe hostname of the FIXEdge Java to be used by the health check
The FIXEdge properties file example
# Name of REST service, if it is empty or disabled, REST service will not be available and registered in Service Discovery
rest.service.name=REST-AdminAPI
# Name of REST port, if it is empty or disabled, REST service will not be available and registered in Service Discovery
rest.service.port=9010
# Path to SSL certificate, should not be empty to create REST service and register it in Discovery
rest.ssl.cert.path=/ssl/cert.pem
# Path to SSL key, should not be empty to create REST service and register it in Discovery
rest.ssl.key.path=/ssl/key.pem
# Name of server, if it is not empty, server will be registered in Discovery by this name. Otherwise, it will not be registered.
server.name=ServerA
# Name of protocol, used for server registration in Service Discovery
protocol.name=FIX
# Health check interval (Service Discovery)
service.discovery.healthcheck.interval=10
# Service Discovery attempt period, milliseconds
service.discovery.attempt.period=10000
# Fixicch2 REST API to load fix session and schedules configs and to subscribe on session and schedules changes
fixicch2.url=http://10.68.21.181:8080
# Fixicch2 URL prefix if Service Discovery is used to define IP and port
fixicch2.url.prefix=http
# Timeout for attempts to connect to Service Discovery, mc
fixicch2.service.discovery.connection.timeout=60000
# Max time to wait Service Discovery Fixicc H2 health status update, min
fixicch2.service.discovery.status.update.timeout=10
# To use original sessionConfigManager and scheduleConfigManager beans set 'false' or comment it
# To use fixxicch2 session and schedule config managers set 'true'
server.useFixicch2ConfigManager=true
# Fixicch2 service name is used when the fixicch2.url is not set
fixicch2.service = FIXICC H2
# Pause to reconnect to FIXICC H2 URL in case of errors, mc
fixicch2.reconnect.pause=2000
# Allows to configure the secure connection from FIXEdge Java to FIXICC H2
fixicch2.insecure.connection.enabled=false
#The hostname or IP address of the Consul Agent
consul.host=localhost
#The hostname of the FIXEdge Java to be used by the health check
server.checkHost=localhost


After the FIXEdge Java configuration is completed and FIXEdge Java is started, the Consul application will add "REST-AdminAPI" and "FIX" services for the "ServerA" server to the service list.


You can see the example in the figure below:


Figure. The list of the configured services.

To run Consul UI, open browser page with address: localhost:8500.

The FIXICC H2 can have access to the configured services.

  • No labels