In the simplest case, the Handler needs a reference for a connectivity configuration to get initialized. However, there were other parameters which affect miscellaneous aspects of Handler's behavior. These parameters are collected into the single OnixS::ICE::iMpact::MarketData::HandlerSettings
class. An instance of this class must be delivered to the Handler at the construction stage.
OnixS::ICE::iMpact::MarketData::HandlerSettings::logLevel
parameter of the OnixS::ICE::iMpact::MarketData::HandlerSettings
class instructs the Handler whether it should log its events and which of events should be put into the log. By default, to provide maximum performance, logging is not performed by the Handler. However, in some cases logging becomes a useful feature. For example, log data can be used by the support team to analyse and resolve miscellaneous issues occurred during the execution of the Handler.
Since recently, the Handler uses new unified licensing services which allow storing multiple licenses for a single and multiple products in the single place. By default, the Handler looks for license at the current directory of the application which executes the Handler. However, sometimes there's a need to store license in a different place, especially when a company uses multiple Onix Solutions products. For this reason, OnixS::ICE::iMpact::MarketData::HandlerSettings
exposes OnixS::ICE::iMpact::MarketData::HandlerSettings::licenseDirectory
parameter which allows to specify directory in which Handler should look for the license.
Following example demonstrates how to construct Handler with custom options: