TT User Setup

7.17.42.1

Released: Dec 11, 2014 File Size: 0
Package Contents:
No notes available.

Important Notes

If you are currently using TT Update to manage TT Client applications and you have not already added TTUpdateEnabled=1 to the TTUserSetupServer.ini file on the TT User Setup servers, you must do so prior to upgrading. Failing to add this parameter will disable TT Update for all TT client applications.

Why Should I Upgrade?

Note: When upgrading to this version from a 7.4.x version, refer to the TT User Setup 7.17.10 Release Notes for information about the features introduced in TT User Setup 7.17.10, important upgrade considerations, installation notes, enhancements, and fixes.

This release supports Trading Technologies' initiative to become the Vendor of Record for CME Market Data in the MultiBroker environment. As part of this initiative, Broker Administrators can use the User Settings tab to manage "Grandfathered" settings for both internal and buy-side users, and "Netting Participant" settings for their own internal users. Buy-side administrators can set whether their users are covered under a netting agreement from the Set CME Netting Agreement section within the TT User Setup web client. Users that access CME market data and are not validated netting participants will be limited to a single concurrent login in MultiBroker.

The Grandfathered and Netting settings are also available in Non-MultiBroker, but are optional, and intended to be used as needed for each company's tracking purposes. The settings can be reported from the CME Product Group Permissions report, as well as from the Product Group Permissions window in both MultiBroker and Non-MultiBroker environments.

Additionally, as part of the CME Billing Requirements, in MultiBroker ONLY, X_TRADER® and X_RISK users that subscribe to CME market data will be presented with a link to the CME Market Data Subscriber Agreement. All users must sign this agreement by January 1, 2015 to continue to be able to access CME Market Data. This requirement applies to both SIM and Live users.

Additional information about CME Market Data billing and administration can be found in this FAQ and in the TT User Setup Help. For more information about market data reporting in MultiBroker, please contact your TAM.


This release supports the following new features added in 7.17.40:
  • Price Reasonability at Pre-Open and other Non-matching states: In addition to the current account-based price reasonability setting that is not enforced during non-matching states like pre-open, TT User Setup administrators can now choose to enable price reasonability during pre-open (non-matching) states. During non-matching states, the price check uses the indicative open price as the market price, otherwise, the price check uses the first available price from the last/close or settle, in that order. If none of these prices exist, then the algorithm assumes there is no market data at all, and allows or rejects the order based on the Reject orders when there is no market data setting. Price reasonability during Pre-open/Non-matching requires Gateways 7.17.65 or later. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Rejecting orders when there is no market data: When using account-based price reasonability, administrators can choose to reject orders when there is "no market data" (regardless of whether or not the market is in a matching or nonmatching state). This setting also requires Gateways 7.17.65 or later. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Synthetic Order Type Restrictions: Administrators can now enable or disable Iceberg, Time, Volume, Stops and Machine Gun orders, per user, from within TT User Setup. In the MultiBroker environment, Broker administrators set these permissions for buy-side users. These new synthetic order restrictions require Synthetic SE Server 7.17.45 or later. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Preventing Market Orders per Gateway: Administrators can now enable or disable the ability to submit market orders on a per User/Gateway basis, or continue to allow or prevent market order submission on a per user basis. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Two-factor authentication via SMS: In addition to the two-factor authentication via Email introduced in 7.17.30, administrators can now require users to use SMS-based two-factor authentication when logging onto their X_TRADER®, X_RISK, and TT User Setup applications. Two-factor authentication via SMS requires TT User Setup 7.17.40 or higher, and X_TRADER® and X_RISK 7.17.40 or higher (7.17.50 or higher is recommended). When SMS two-factor authentication is enabled for the system, users with Two factor authentication checked must also have an SMS Number configured on their User Settings tab. SMS service will be provided by a third-party. Customers' wanting to enable SMS two-factor authentication must contact their TAM to set up an SMS account. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.
    Note: When the system is set to use two-factor authentication via SMS, all TT User Setup clients that will be used to edit user or system 2-factor authentication features must also be upgraded to 7.17.40

This release also:
  • Allows the Days an application can be trusted setting to be set to 0, which means the user must use two-factor every login.
    Note: If you set the Days an application can be trusted to 0, any TT User Setup clients will be used to access the System Settings window should also be upgraded to 7.17.40.
  • Updates the ICE Product Groups to match changes made at the ICE exchange. Refer to the What's New in TT User Setup? section of the TT User Setup Help for a list of new, merged, and changed ICE product groups.
  • Adds a 'Status' column to the CME product group report to indicate whether a user is active or inactive.
  • Supports BVMF exchange requirements by requiring users that connect to BVMF Gateway Logins to reset their passwords every 45 days.
  • Fixes an issue where product group permissions were incorrectly disabled when upgrading from 7.4.x. (7.17.42)

System Requirements

Note: When upgrading to this version from a 7.4.x version, refer to the TT User Setup 7.17.10 Release Notes for information about the features introduced in TT User Setup 7.17.10, important upgrade considerations, installation notes, enhancements, and fixes.

This release supports Trading Technologies' initiative to become the Vendor of Record for CME Market Data in the MultiBroker environment. As part of this initiative, Broker Administrators can use the User Settings tab to manage "Grandfathered" settings for both internal and buy-side users, and "Netting Participant" settings for their own internal users. Buy-side administrators can set whether their users are covered under a netting agreement from the Set CME Netting Agreement section within the TT User Setup web client. Users that access CME market data and are not validated netting participants will be limited to a single concurrent login in MultiBroker.

The Grandfathered and Netting settings are also available in Non-MultiBroker, but are optional, and intended to be used as needed for each company's tracking purposes. The settings can be reported from the CME Product Group Permissions report, as well as from the Product Group Permissions window in both MultiBroker and Non-MultiBroker environments.

Additionally, as part of the CME Billing Requirements, in MultiBroker ONLY, X_TRADER® and X_RISK users that subscribe to CME market data will be presented with a link to the CME Market Data Subscriber Agreement. All users must sign this agreement by January 1, 2015 to continue to be able to access CME Market Data. This requirement applies to both SIM and Live users.

Additional information about CME Market Data billing and administration can be found in this FAQ and in the TT User Setup Help. For more information about market data reporting in MultiBroker, please contact your TAM.


This release supports the following new features added in 7.17.40:
  • Price Reasonability at Pre-Open and other Non-matching states: In addition to the current account-based price reasonability setting that is not enforced during non-matching states like pre-open, TT User Setup administrators can now choose to enable price reasonability during pre-open (non-matching) states. During non-matching states, the price check uses the indicative open price as the market price, otherwise, the price check uses the first available price from the last/close or settle, in that order. If none of these prices exist, then the algorithm assumes there is no market data at all, and allows or rejects the order based on the Reject orders when there is no market data setting. Price reasonability during Pre-open/Non-matching requires Gateways 7.17.65 or later. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Rejecting orders when there is no market data: When using account-based price reasonability, administrators can choose to reject orders when there is "no market data" (regardless of whether or not the market is in a matching or nonmatching state). This setting also requires Gateways 7.17.65 or later. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Synthetic Order Type Restrictions: Administrators can now enable or disable Iceberg, Time, Volume, Stops and Machine Gun orders, per user, from within TT User Setup. In the MultiBroker environment, Broker administrators set these permissions for buy-side users. These new synthetic order restrictions require Synthetic SE Server 7.17.45 or later. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Preventing Market Orders per Gateway: Administrators can now enable or disable the ability to submit market orders on a per User/Gateway basis, or continue to allow or prevent market order submission on a per user basis. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.

  • Two-factor authentication via SMS: In addition to the two-factor authentication via Email introduced in 7.17.30, administrators can now require users to use SMS-based two-factor authentication when logging onto their X_TRADER®, X_RISK, and TT User Setup applications. Two-factor authentication via SMS requires TT User Setup 7.17.40 or higher, and X_TRADER® and X_RISK 7.17.40 or higher (7.17.50 or higher is recommended). When SMS two-factor authentication is enabled for the system, users with Two factor authentication checked must also have an SMS Number configured on their User Settings tab. SMS service will be provided by a third-party. Customers' wanting to enable SMS two-factor authentication must contact their TAM to set up an SMS account. For more information refer to the What's New in TT User Setup? section of the TT User Setup Help.
    Note: When the system is set to use two-factor authentication via SMS, all TT User Setup clients that will be used to edit user or system 2-factor authentication features must also be upgraded to 7.17.40

This release also:
  • Allows the Days an application can be trusted setting to be set to 0, which means the user must use two-factor every login.
    Note: If you set the Days an application can be trusted to 0, any TT User Setup clients will be used to access the System Settings window should also be upgraded to 7.17.40.
  • Updates the ICE Product Groups to match changes made at the ICE exchange. Refer to the What's New in TT User Setup? section of the TT User Setup Help for a list of new, merged, and changed ICE product groups.
  • Adds a 'Status' column to the CME product group report to indicate whether a user is active or inactive.
  • Supports BVMF exchange requirements by requiring users that connect to BVMF Gateway Logins to reset their passwords every 45 days.
  • Fixes an issue where product group permissions were incorrectly disabled when upgrading from 7.4.x. (7.17.42)

Installation Notes

When TT Update is not installed on the TT User Setup client workstation, you must manually install a supported TT User Setup client. When TT Update is installed on the TT User Setup client workstation, TT Update will automatically update the TT User Setup client to match the TT User Setup server. The TT User Setup 7.17.42 server is ONLY compatible with TT User Setup 7.17.0.520, 7.17.10, 7.17.12, 7.17.13, 7.17.20, 7.17.21, 7.17.22, 7.17.23, 7.17.24. 7.17.30, 7.17.31, 7.17.40, 7.17.41, and 7.17.42 clients. The TT User Setup 7.17.42 client is not compatible with pre-7.17.42 TT User Setup servers.

To use the latest features, you should use the latest version of the client and server. Additionally, when the system is set to use two-factor authentication via SMS, all TT User Setup clients that will be used to edit user or system 2-factor authentication features must also be upgraded to 7.17.40. Clients that fail to upgrade will receive error messages or shut down when editing SMS related settings.

For more information about TT Update, refer to the TT Update Help. For more information about installing TT User Setup, refer to the TT User Setup System Administration Online Help.

Enhancements

  1. Gateway Logins
    1. Added a new field Market Orders to the Users and their Gateway Login Attributes window that allows administrators to allow market orders for this User/Gateway Login, to prevent market orders for this User/Gateway Login, or to continue to allow or prevent market order submission based on the user-level Market Orders setting. (Ref 229264)

    2. Per BVMF exchange requirements, users that connect to BVMF Gateway Logins must reset their passwords every 45 days, and none of the last six passwords may be reused. TT User Setup now enforces this requirement. (Ref 229450)

  2. Login
    1. In addition to the two-factor authentication via Email introduced in 7.17.30, administrators can now require users to use SMS-based two-factor authentication when logging onto their X_TRADER®, X_RISK, and TT User Setup applications. Two-factor authentication via SMS requires TT User Setup 7.17.40 or higher, and X_TRADER® and X_RISK 7.17.40 or higher (7.17.50 or higher is recommended). When SMS two-factor authentication is enabled for the system, users with Two factor authentication checked must also have an SMS Number configured on their User Settings tab. (Ref 229261)

  3. Product Setup
    1. Updated the ICE Product Groups to match changes made at the ICE exchange. (Ref 229470)

  4. Reports
    1. Added a 'Status' column to the CME product group report that lists whether a user is active or inactive. (Ref 229260)

  5. Risk Limits
    1. In addition to the current account-based price reasonability setting that is not enforced during non-matching states like pre-open, TT User Setup administrators can now choose to enable price reasonability during pre-open (non-matching) states. This option is available from the account-based product limits window; the default is to not enforce the check during not matching states. If the option is enabled, during non-matching states, the price check uses the indicative open price as the market price, otherwise, the price check uses the first available price from the last/close or settle, in that order. If none of these prices exist, then the algorithm assumes there is no market data at all, and allows or rejects the order based on the Reject orders when there is no market data setting.

      Additionally, when using account-based price reasonability, administrators can choose to reject orders when there is "no market data" (regardless of whether or not the market is in a matching or nonmatching state). This option is also available from the account-based product limits window; the default is to allow orders when there is no market data. (Ref 229262)

    2. Administrators can now enable or disable Iceberg, Time, Volume, Stops and Machine Gun orders, per user, from the User's Trade Permissions tab. In the MultiBroker environment, Broker administrators set these permissions for buy-side users. (Ref 229263)

    3. Added a feature in MultiBroker that recommends an available Member when the selected Member is already in use by another company. (Ref 229265)

  6. Server
    1. Updated the ICE product groups to match the currently available product groups.
      • The following product group permissions have been renamed. If the previous product group was allowed, the renamed product group will be allowed as well.
        • CA Futures is renamed to ICE Futures Canada
        • CCFE is renamed to ICE Physical Environment
        • OTC Gas is renamed to ICE S2F Gas
        • OTC Oil is renamed to ICE S2F Oil
        • OTC Power is renamed to ICE S2F Power
        • UK Futures is renamed to ICE Futures Europe Commodities
        • US Futures is renamed to ICE Futures U.S.
      • Fin Index Data is merged into the existing ICE Futures U.S. If either of the product groups was previously allowed, the merged product group will be allowed as well.
      • Heat Rate Spread is merged into the existing ICE S2F Gas. If either of the product groups was previously allowed, the merged product group will be allowed as well.
      • The following product groups have been added and will be disabled by default for existing buy-side users in the MultiBroker environment, and enabled by default for all other existing users (in both MultiBroker and non-MultiBroker environments):
        • ICE Futures Europe Financials
        • ICE Endex
      (Ref 229399)

    2. Added a feature that automatically propagates Direct trader gateway login password updates without requiring any component restarts. (Ref 229582)

    3. Administrators can now mark a user as Grandfathered and/or covered under a netting agreement for the billable CME Product Groups. In non-MultiBroker, the new settings are located on the user's User Settings tab and can be set by group or system administrators. In MultiBroker, Broker Administrators can configure grandfathered settings for their internal users as well as buy-side users that connect to them, and they can set their own internal users as being covered under a netting agreement (from the user's User Settings tab). Buy-side administrators set whether their users are covered under a netting agreement from the TT User Setup web client.

      In MultiBroker these setting have billing implications, but in Non-MultiBroker the fields are optional and are intended to be used as needed for each companies tracking purposes. The new fields also appear in the CME Product Group Permissions report. (Ref 229794)

    4. As part of the CME Billing Requirements, in MultiBroker ONLY, X_TRADER® and X_RISK users that subscribe to CME market data will be presented with a link to the CME Market Data Subscriber Agreement. All users must sign this agreement by January 1, 2015 to continue to be able to access CME Market Data. This requirement applies to both SIM and Live users. (Ref 229799)

    5. Updated the CME Product Group Permissions report with columns for the the new Grandfathered, Netting, Netting program participant settings, as well as a User Created Data and User Last Login Date columns. (Ref 229842)

  7. Users
    1. When creating new users, Product Group Permissions will be set to "Blocked" by default. New users will not have access to market data until specifically allowed. (Ref 229521)

Fixes

  1. General
    1. Fixed an issue where the "Most Recent X_TRADER® version" report listed the TT SIM version instead of the X_TRADER® version. (Ref 227945)

  2. Server
    1. Fixed an issue where product group permissions were incorrectly disabled when upgrading from 7.4.x. (Ref 230222)

  3. Users
    1. Fixed an issue where TT User Setup administrators with Live login allowed and TT SIM Login both unchecked could not log into TT User Setup. (Ref 223497, 219842)

Known Issues

    1. FIX Adapter Clients with Live login allowed and TT SIM login allowed both unchecked cannot log into FIX Adapter servers. Future versions will not require either of these checkboxes to log into FIX Adapters. The workaround is to check one of these checkboxes for FIX Adapter Clients. (Ref 222720)

    2. When the system is set to use two-factor authentication via SMS, all TT User Setup clients that will be used to edit user or system 2-factor authentication features must also be upgraded to 7.17.40. Clients that fail to upgrade will receive error messages or shut down when editing SMS related settings. (Ref 229625)

  1. Reports
    1. Logging onto X_TRADER® increments the TT API entry in the TT Product Version/User Usage report by two. TT API should not be listed at all unless the client specifically logged into TT API. (Ref 220131)

    2. The "Most recent X_TRADER® Version" report appears to list multiple entries for the same user and IP address. However, the duplicate entry is actually the X_STUDY® version and can be disregarded. (Ref 227295)