Try TT Now

Market Price Feed Environments

Market Price Feed (MPF) environments are networks setup so that client applications connect to a particular TT Gateway for order and fill data but to a separate TT Gateway for its price information. (For detailed information on MPF architecture and its usability, refer to the Market Price Feed Feature Guide on the Customer Portal.)

If you are in an MPF environment, you must know the flavor of the gateway on your MPF server. Then, when subscribing to contracts and spreads, you must point your fmds.cfg to the designated MPF server.

Example: You are in an environment with three CME Gateways: CME, CME-A, and CME-B. You introduce a new gateway to take advantage of the MPF functionality and you call it: CME-C.

In this example, CME, CME-A, and CME-B are used for order and fill data. And the new CME-C is the gateway flavor designated as the MPF server. When you use FMDS to subscribe to a CME contract or spread, you must point your fmds.cfg file to CME-C. You do this because FMDS is only interested in prices.

In an MPF Environment:

You used to subscribe to:But you MPF Server is now on :In the fmds.cfg, you type your Gateway and Product as:

CME.ES

CME-C

CME-C.ES

CME-A.ES

CME-C

CME-C.ES

CME-B.ES

CME-C

CME-C.ES

Non-MPF Environments

In a non-MPF environment, when you subscribe to an instrument in an environment with multiple gateway flavors (e.g., CME, CME-A, CME-B…etc.), you must include the flavor of the gateway to which you are subscribing in the fmds.cfg file.

In a non-MPF Environment:

You used to subscribe to:But you MPF Server is now on :In the fmds.cfg, you type your Gateway and Product as:

CME.ES

n/a

CME.ES

CME-A.ES

n/a

CME-A.ES

CME-B.ES

n/a

CME-B.ES