In this section:
| Table of Contents | ||
|---|---|---|
|
...
You can configure the following settings.
Settings Options
Either Acceptor settings path or Socket accept port is required. Logging level is optional.
| Scroll Table Layout | ||
|---|---|---|
|
| Accepter settings path | Specify the absolute path to the cfg properties file that defines how the FIX engine in the Virtualize server should accept connections from clients. You can review example acceptor cfg file below. For a detailed definition of the properties, see the following documentation: https://www.quickfixj.org/usermanual/1.5.3/usage/configuration.html Either Acceptor settings path this or Socket accept port is required. |
|---|---|
| Socket accept port | If specified, the FIX engine will accept connections on this port and the other acceptor property values would assume default values. In particular, the option would accept requests of any Either this or Acceptor settings path or Socket accept port is is required. |
| Reset persistent message store upon re-deploy | Tells Virtualize server whether to reset the message store when the asset is redeployed. This option applies only when using a persistent message store like a file message store. A persistent message store is configured when the acceptor settings path points to a cfg properties file and that file specifies a file message store (by uncommenting By default, the Virtualize server uses a memory message store (not persistent). With a memory message store, the message sequence number is automatically reset each time the virtual asset is re-deployed. Enter If set to Default is |
| Logging level | Specify the logging level. You can enter 0 (least verbose), 1, or 2 (most verbose). This is optional. |
Example Acceptor cfg File
...
| Recording? | Enables/disables recording. Enter If recording is enabled, responders are not used and Virtualize will connect to another FIX engine for the response, instead. |
|---|---|
| Proxy initiator settings path | Specify the absolute path to the cfg properties file that defines how Virtualize should initiate connections to the FIX engine. An example initiator cfg file is provided below. For a detailed definition of the properties, see the following documentation: https://www.quickfixj.org/usermanual/1.5.3/usage/configuration.html |
| TargetCompID | Specify the target comp ID that is used to identify the FIX client application. |
| Proxy response timeout | Specify the number of milliseconds that Virtualize should wait for request responses. The default is 30000. |
| Number of responses to wait for | Specify the number of responses that this request is expected to trigger—and trigger and that Virtualize should wait for. The default is is 1. |
| Record and return all responses | If the value specified in the Number of responses to wait for option is greater than 1, this option determines whether all responses should be returned by Virtualize. Enter y for yes. Enter n for no and only the last response received will be returned. The default is n. |
| Traffic file path | Specify the absolute path to the file that should record the traffic being passed between the actual client and the FIX engine. |
...