{"id":7161,"date":"2025-08-28T22:36:25","date_gmt":"2025-08-29T03:36:25","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&#038;p=7161"},"modified":"2025-09-05T13:32:07","modified_gmt":"2025-09-05T18:32:07","slug":"creating-a-tt-fix-drop-copy-session","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/tt-fix\/tt-fix-drop-copy-out\/overview-tt-fix-drop-copy-out\/creating-a-tt-fix-drop-copy-session\/","title":{"rendered":"Creating a TT FIX Drop Copy session"},"content":{"rendered":"\n<p>FIX client drop copy applications connect to TT FIX services through a FIX Drop Copy session. <\/p>\n\n<p>Use the <strong>FIX sessions<\/strong> window to add FIX sessions to your company and configure them for third-party\n\tFIX client access. <\/p>\n\n<!--\n\tDrop Copy OUT\n\t-->\n\n\n<section>\n\t<p>To add and configure a FIX Drop Copy session:<\/p>\n\t<ol>\n\t\t<li>\n\t\t\tClick <strong>More<\/strong> | <strong>FIX Sessions<\/strong> in the left navigation pane.\n\t\t<\/li>\n\t\t<li>\n\t\t\tAt the top of the FIX Sessions window, click <strong>+New Session<\/strong>.\n\t\t\t<p><img decoding=\"async\" class=\"img-responsive\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/08\/deb-ttus-fix-session-dc-out-1.png\" alt=\"Add-PIC\"><\/p>\n\t\t<\/li>\n\t\t<li>\n\t\t\tFor <strong>FIX Type<\/strong>, select <strong>FIX Drop Copy<\/strong>.\n\t\t<\/li>\n\t\t<li>Configure the following settings:\n\t\t\t<ul>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>FIX Session Name<\/strong> \u2014 Sets the display name of the FIX server.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Remote Comp Id<\/strong> \u2014 Sets the FIX client ID. This FIX client ID value is sent in\n\t\t\t\t\tFIX Tag 49 (SenderCompID) by a FIX client connecting to the FIX server. The ID is populated in FIX\n\t\t\t\t\tTag 56 (TargetCompID) for all messages sent by the FIX Server to the FIX client.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Target Sub Id<\/strong> \u2014 Sets the receiver ID. This value is sent in FIX Tag 57\n\t\t\t\t\t(TargetSubId) of the FIX client Logon (A) message.\n\t\t\t\t\t<p><\/p>\n\t\t\t\t\t<!--\n\t\t\t\t\t\t<strong>Note<\/strong>: If a value is specified for this setting, the combination of the <strong>Remote Comp Id<\/strong> and <strong>Target Sub Id<\/strong> settings must be unique among all FIX sessions.\n\t\t\t\t\t-->\n\t\t\t\t\t<strong>Notes<\/strong>:\n\t\t\t\t\t<p><\/p>\n\t\t\t\t\tIf a value is specified for this setting:\n\t\t\t\t\t<ul>\n\t\t\t\t\t\t<li>The combination of the <strong>Remote Comp Id<\/strong> and <strong>Target Sub Id<\/strong>\n\t\t\t\t\t\t\tsettings must be unique among all FIX sessions.<\/li>\n\t\t\t\t\t\t<li>The FIX client connecting to this FIX session must supply the same value in tag 57.<\/li>\n\t\t\t\t\t<\/ul>\n\t\t\t\t\t<p><\/p>\n\t\t\t\t\tAlso, if FIX clients send Tag 57, which is optional, in the Logon (A) message, the value must be\n\t\t\t\t\tsupplied in this setting.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Session Password<\/strong> \u2014 The password associated with this FIX session and used to\n\t\t\t\t\tauthenticate FIX Servers. FIX Session passwords do not expire and are not subject to any TT account\n\t\t\t\t\tpassword restrictions. It must be passed in Tag 96 (RawData) in the Logon (A) message.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Notification email<\/strong> \u2014 Sets the email address company administrators can use to\n\t\t\t\t\treceive notifications from TT for emergency maintenance, operational or product release information\n\t\t\t\t\tthat could impact the FIX session.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Country<\/strong> \u2014 The country in which the FIX server machine is located.\n\t\t\t\t\t<p>Based on the country selected, you may also need to provide a State\/Province and Zip Code.<\/p>\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Send Staged \/ Synthetic Child order \/ fill messages<\/strong> \u2014 Sets whether to send\n\t\t\t\t\torder and fill messages to the FIX client for child order of staged or synthetic parent orders.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Send and receive Order ID values in short form<\/strong> \u2014 Sets whether to send\n\t\t\t\t\tshortened order IDs in tag 37 (OrderId) in order routing and execution report messages.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Compliance Feed<\/strong> \u2014 When enabled, the Drop Copy session will deliver New Order\n\t\t\t\t\tSingle (D), Cancel\/Replace (G), New Order Multileg (AB), Multileg Cancel\/Replace (AC) and Cancel (F)\n\t\t\t\t\tmessages, plus the related Pending Request (150 = A, E or 6) Execution Report (8) messages. These\n\t\t\t\t\tcompliance messages include high precision timestamps suitable for MIFID II reporting as to when\n\t\t\t\t\tTT\u2019s order routing software received the request and when it sent the request to the exchange.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Force sending of Head fills before Leg fills<\/strong> \u2014 Sets whether to always send\n\t\t\t\t\tHead fills (442=3) before sending the individual leg fills (442=2). This setting is supported only\n\t\t\t\t\tfor FIX 4.4 sessions.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Send FillsGrp as Individual Execution Reports<\/strong> \u2014 Sets whether to send an\n\t\t\t\t\tindividual Execution Report (8) message for each entry in the FillsGrp and LegFillsGrp repeating\n\t\t\t\t\tgroups instead of in a group in a single Execution Report (8) message.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Send TT Internal Account ID and User ID on Execution Reports And Cancel Reject\n\t\t\t\t\t\tMessages<\/strong> \u2014 Sets whether to send the TT internal IDs for tag 1 (Account) and tag\n\t\t\t\t\t129 (DeliverToSubId) in tags 18101 (AccountID) and 18102 (UserID), respectively, for Execution\n\t\t\t\t\tReport (8) and Order Cancel\/Replace Request (9) messages.\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Filter AOTC Executions &amp; Add Compliance Messages for AOTC-triggered actions at the\n\t\t\t\t\t\tExchange<\/strong> \u2014 Sets whether to filter Avoid Orders That Cross (AOTC) and Compliance\n\t\t\t\t\tmessages. When enabled, FIX Drop Copy will:\n\t\t\t\t\t<ol>\n\t\t\t\t\t\t<li>Generate compliance messages for AOTC fills \/ changes that occur against orders resting at\n\t\t\t\t\t\t\tthe exchange.<\/li>\n\t\t\t\t\t\t<li>Simultaneously drop any internal fill messages for that action.<\/li>\n\t\t\t\t\t\t<li>Drop the internal transfer fills\/cancels for the aggressing order.<\/li>\n\t\t\t\t\t<\/ol>\n\t\t\t\t<\/li>\n\t\t\t\t<!-- waiting for DEB-62511\n\t\t\t\t\t<li>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<strong>Send and receive Order ID values in short form<\/strong> &mdash; Sets whether to send shortened IDs for orders instead of the standard 36-character TT order IDs in tag 37 (OrderID). When enabled, TT will send and receive order IDs in short form (26 chars) in tags 37 and 16113, and also copy the original full-size order ID (36 chars) to tag 16116 (OrderIDGUID). By default, TT sends 36-character GUID in the order ID fields. The short form is created by converting the GUID from hexadecimal to a base-32 representation.\n\t\t\t\t\t\t<\/p>\n\t\t\t\t\t\t<p>For example:<\/p>\n\t\t\t\t\t\t<p>\n\t\t\t\t\t\t<strong>Tag 37 (original):<\/strong> 37=d9e95c8f-93b1-4559-8174-c47e8ba1b95d\n\t\t\t\t\t\t<br>\n\t\t\t\t\t\t<strong>Tag 37 (short form):<\/strong> 37=3HUVZD4TWFCVTALUYR7IXINZLU\n\t\t\t\t\t\t<\/p>\n\t\t\t\t\t<\/li>\n\t\t\t\t\t-->\n\t\t\t\t<li>\n\t\t\t\t\t<strong>Send Exchange Fill Updates as Trade Correction Execution Reports<\/strong> \u2014 Sets\n\t\t\t\t\twhether to send exchange fill updates as Execution Report (8) messages instead of Trade Capture\n\t\t\t\t\tReport (AE) messages for the following markets:\n\t\t\t\t\t<ul>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tHKEX\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tOSE\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tSGX\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tTOCOM\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tNDAQ_EU\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tNFI\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t<\/ul>\n\t\t\t\t<\/li>\n\t\t\t\t<li>\n\t\t\t\t\t<strong>(Session Reset)<\/strong>: \u2014 Schedule for resetting the FIX Server connection.\n\t\t\t\t\t<p>To set the reset time:<\/p>\n\t\t\t\t\t<ol>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tClick a day to enable the <strong>Reset Time (UTC)<\/strong> fields.\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\tSet the desired session reset time in UTC time.\n\t\t\t\t\t\t<\/li>\n\t\t\t\t\t<\/ol>\n\t\t\t\t<\/li>\n\t\t\t<\/ul>\n\t\t<\/li>\n\t\t<li>\n\t\t\tIn the <strong>Status<\/strong> section, choose whether to make the session active. The session is inactive\n\t\t\tby default.\n\t\t<\/li>\n\t\t<li>\n\t\t\tIn the <strong>Account Settings<\/strong> section, enable the <b>Assign All Accounts<\/b> setting to ensure\n\t\t\tthat all available accounts for the entire company are assigned to the FIX Drop Copy\n\t\t\tsession. This includes accounts shared with your company. Dynamically, new accounts will be assigned to the\n\t\t\tsession as they&#8217;re available and deleted accounts will be removed. When this checkbox is unchecked, each\n\t\t\taccount has to be mapped individually to the FIX Drop Copy session. This setting is enabled by default.\n\t\t<\/li>\n\t\t<li hidden>Click <strong>+Add<\/strong> in the <strong>Company Relationships<\/strong> section to share FIX\n\t\t\tsessions with other companies (e.g., to brokers). <p> This allows the FIX Session to be configured for\n\t\t\t\ttrading (assigned accounts, connections, etc.) by the shared company.<\/p><\/li>\n\t\t<li>\n\t\t\tClick <strong>Save Changes<\/strong>.\n\t\t<\/li>\n\t\t<li>\n\t\t\t<a href=\"\/tt-fix\/Managing_FIX_Sessions.html\">Configure the connection\n\t\t\t\tto the FIX session<\/a> via TCP or Secured TCP (SSL).\n\t\t<\/li>\n\t<\/ol>\n\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>FIX client drop copy applications connect to TT FIX services through a FIX Drop Copy session. Use the FIX sess [&hellip;]<\/p>\n","protected":false},"author":2,"template":"","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[475],"class_list":["post-7161","doc","type-doc","status-publish","hentry","docs-category-overview-tt-fix-drop-copy-out"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7161","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc"}],"about":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/types\/doc"}],"author":[{"embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":0,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7161\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7161"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}