| Table of Contents |
|---|
Overview
The settings in this section describe only FIXEdge parameters. These parameters don't belong to FIX sessions parameters or FIX Engine parameters.
These settings of the FIXEdge are defined into 'FIXEdge.properties' configuration file.
...
This section describes properties in FIXEdge.properties file which are responsible for TCP protection.
...
For more information please read the article How to configure TCP protection in FIXEdge.
Transport Adaptors common parameters
...
The parameter is an enumeration of transport adapters' directory names separated by ','
Default value is:
...
the path of the folder where the application's executive file is located
| Info |
|---|
This parameter is applicable since FIXEdge C++ version 6.14.0 |
Control Centre parameters
ControlCentre.XMLSockMonitor.Port
XML Sock monitoring port to accept requests from the special tool FEAdminConsole.
Example: ControlCentre.XMLSockMonitor.Port = 8902
ControlCentre.Lock.File.Name
File that prevents from starting multiple FIXEdge instances at the same directory.
Example: ControlCentre.Lock.File.Name = FIXEdge1/log/_fixedge.lock
...
Optional. Defines if the new schedule management functionality should be available in FIXICC or not.
...
Once value is reached and exceeded FIXEdge generates OnNotificationEvent to notify about exceeding the available memory.
...
Described functionality is implemented in FIXEdge Windows version only.
Logging for lifecycle FIXEdge events
Since FIXEdge version 6.7.0 the following lifecycle events are supported:
| Name | Description |
|---|---|
| AppStarting | Application is being to be started and log system is initialized |
| AppStarted | Properties are loaded and sessions are runned |
| AppReady | All components of application was started |
| AppFailed | Application is crashed |
| AppSigTermDetected | Signal SIGINT or SITERM is detected |
| AppShutdown | Application is being to shut down (stop sessions / destroy objects) |
| AppComplete | All work is done, stopped as planned |
...
| Info |
|---|
Events can be forwared to ArcSight See How to configure forwarding FIXEdge lifecycle events to ArcSight for more information |
Log.Events.LogCategory
Mandatory. Default category for all events
...
| Warning |
|---|
if the parameter is not defined, the event logs will not be generated |
| Info |
|---|
See Format of event entries for transfer to ArcSight for more information |
Log.Events.Event.<NameOfEvent>.LogCategory
Optional. Log category for a single event
Default value: value of Log.Events.LogCategory parameter
Log.Events.Event.<NameOfEvent>.LogLevel
...
Valid values: TRACE, DEBUG, INFO, ERROR, FATAL
Default value: value of Log.Events.LogCategory parameter