Versions Compared

Old Version 1

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version Current

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2024.2

In this section:

Table of Contents
maxLevel2

...

Initiator settings path

Specify the absolute path to the cfg properties file that defines how SOAtest should initiate connections to the FIX engine.

Required.

An example cfg file is provided below this table. For a detailed definition of the properties, see the following documentation:

https://www.quickfixj.org/usermanual/1.5.3/usage/configuration.html

Logon wait timeThe number of milliseconds that SOAtest should wait for the response of the Logon request. The default is 2000.
Response wait timeThe number of milliseconds that SOAtest should wait for the response of other (non-Logon) requests. The default is 10000.
Number of responses to wait forThe number of responses that this request is expected to trigger and that SOAtest should wait for. The default is 1.
Return all responses?If the value of the Number of responses to wait for option is greater than 1, this option determines whether all responses should be returned by SOAtest. Enter y for return all responses. Enter n to return only the last response received. The default is n.
Logging levelThe logging level. You can enter 0 (least verbose), 1, or 2 (most verbose). The default is 0.

Anchor
Example
Example
Example Initiator cfg File

Code Block
languagetext
[default]
#FileStorePath=/tmp/fix/virt/initiator
#FileLogPath=/tmp/fix/logs
ConnectionType=initiator
StartTime=00:00:00
EndTime=00:00:00
HeartBtInt=30
ReconnectInterval=60
SenderCompID=CLIENT
TargetCompID=VIRT
UseDataDictionary=Y
#ValidateIncomingMessage=N
#RejectInvalidMessage=N
SocketConnectHost=localhost
ResetOnLogon=Y


[session]
BeginString=FIX.4.4
SocketConnectPort=9889
DataDictionary=FIX44.xml
Info
titleManaging the Message Store

With a memory message store, the message sequence number is automatically reset each time the test is invoked. With a file message store, the message sequence persists. To reset the message sequence, you would have to manually delete the directory specified by FileStorePath or have the reset triggered by another configuration (such ResetOnLogon).
A memory message store is used with the default initiator cfg file settings. If you prefer to use a file message store, uncomment FileStorePath in the initiator cfg file.

Connection Management Configuration Options

You can enable Keep connection alive or Close connection after test execution.

Execution Notes

  • Logon/Logout: Every time that a FIX Messaging Client is invoked, it will always send a Logon request before sending the specified request, then send a Logout request when the connection is closed.
  • Response not received: If the FIX Messaging Client fails to receive a response, it is most likely for one of the following reasons:
    • The message sequence number is out of sync with the AUT: In this case, one fix is to ensure the sequence is reset to start from the beginning on both the FIX Messaging Client and on the AUT.
    • The FIX client actually receives a response, but it is invalid according to the FIX data dictionary: If the response is indeed legitimate, you can prevent the FIX Messaging Client from rejecting the response by setting the following in the initiator cfg file:
      ValidateIncomingMessage=N
      RejectInvalidMessage=N

Third-Party Content

This extension includes items that have been sourced from third parties as outlined below. 

...