Rational Integration Tester supports FIX versions 4.0 through 4.4. The FIX transport is created when you set up a physical FIX Connection component in Architecture School. Creating the transport also creates a schema that can be viewed or modified in the Schema Library and applied to messages as a schema in the same way that you might apply a FIX dictionary (see FIX dictionaries).
The FIX protocol requires each application to maintain two sequence numbers per session: incoming and outgoing. The numbers are independent of each other, although sequence numbers are always found in Field 34 of the message (commonly referred to as "Tag 34"). The application increments the outgoing sequence number and sets Field 34 equal to that value in each outgoing message. For incoming messages, the application increments the stored incoming sequence number and verifies that it matches the value of Field 34 of the incoming message.
These effects are shown in the following table:
Value of "Reset sequence numbers..." | Storage type | Header |
---|---|---|
Selected | File or In memory | Sequence numbers are reset with each logon. |
Clear | File | Sequence numbers are maintained between multiple runs of the stub and multiple runs of Rational Integration Tester. |
Clear | In memory | Sequence numbers are maintained between multiple logons, but cleared if the stub is restarted. |
The FIX transport is created when you create a physical FIX Connection resource in Rational Integration Tester Architecture School.
In Architecture School, you can create a resource in two ways:
Each physical FIX Connection resource represents a FIX transport that can be selected and configured later on.