Thread: FIX API account questions

Hi,

We are a referring broker(Riflexo LTD) and have several questions regarding the usage of the FIX API.

Questions:

1) How can we login to the FIX demo server? We are trying to connect to the "fixdemo2.fxcorporate.com" provided in the example but a connection can not be established. We have message (Connection refused: no further information). What are the values for the SocketConnectHost and SocketConnectPort to make the connection?

2) Can we use a FXR-type of account to connect to a demo fix server, if so what should we use for target comp, sender comp (SenderCompID)

3)In case it's not possible to login w/ such an account, how can we get a FIX-enabled account.

4) We are mostly interested in NOT receiving MarketDataSnapshot(s), 'W' msg. Is that possible w/ your servers demo/production. We actually opted for FIX solely for that reason. If it's possible to disable the same message on Java Trading API, please advise so. We are likely to need to abandon out current Java-Trading API implementation to solely combat the issue.

5)In case we can't play around the MarketDataSnapshot message, we need a LAMM account in order to manage multiple accounts without bogging the traffic/bandwidth and wasting resources on those messages. Is that correct?

And last: if we go for LAMM:

6) Do the managed by a LAMM account clients lose their regular access (via FXCM trading station) to the trading?

Best Regards,

Originally Posted by riflexo

Hi,

We are a referring broker(Riflexo LTD) and have several questions regarding the usage of the FIX API.

Questions:

1) How can we login to the FIX demo server? We are trying to connect to the "fixdemo2.fxcorporate.com" provided in the example but a connection can not be established. We have message (Connection refused: no further information). What are the values for the SocketConnectHost and SocketConnectPort to make the connection?

2) Can we use a FXR-type of account to connect to a demo fix server, if so what should we use for target comp, sender comp (SenderCompID)

3)In case it's not possible to login w/ such an account, how can we get a FIX-enabled account.

4) We are mostly interested in NOT receiving MarketDataSnapshot(s), 'W' msg. Is that possible w/ your servers demo/production. We actually opted for FIX solely for that reason. If it's possible to disable the same message on Java Trading API, please advise so. We are likely to need to abandon out current Java-Trading API implementation to solely combat the issue.

5)In case we can't play around the MarketDataSnapshot message, we need a LAMM account in order to manage multiple accounts without bogging the traffic/bandwidth and wasting resources on those messages. Is that correct?

And last: if we go for LAMM:

6) Do the managed by a LAMM account clients lose their regular access (via FXCM trading station) to the trading?

Best Regards,

Talk to your sales rep about the credentials for your fix account. And regarding the "not receiving marketdatasnapshot", you can choose to receive marketdatasnapshots or you can choose not to receive marketdatasnapshots in FIX and Java API. If you were using the Java API why didn't you just not ask for marketdatasnapshots? or if you only need them once why don't you just ask for it once? what were you trying to do?

Below is the code, indeed it works for disabling the feed of the currency pairs w/o active trades. However, it is not session based but rather account based, i.e. it also disables them for any completely unaware user of Trading Station... and vice versa - adding them from the Trading Station client enables them for JavaTrading API.
I suppose there is only a single state kept per account (not session).

The explained behavior is erratic and very undesirable.
So, we were looking for a FIX based solution hoping it favors the (FIX) session and not the account overall.

Code:

    MarketDataRequest mdr = new MarketDataRequest();
    mdr.setSubscriptionRequestType(SubscriptionRequestTypeFactory.UNSUBSCRIBE);
    mdr.setFXCMTimingInterval(FXCMTimingIntervalFactory.TICK);
    mdr.setMDEntryTypeSet(MarketDataRequest.MDENTRYTYPESET_ALL);
    mdr.setMDReqID("zax");
    
    g.sendMessage(mdr);

Cheers

Originally Posted by riflexo

Below is the code, indeed it works for disabling the feed of the currency pairs w/o active trades. However, it is not session based but rather account based, i.e. it also disables them for any completely unaware user of Trading Station... and vice versa - adding them from the Trading Station client enables them for JavaTrading API.
I suppose there is only a single state kept per account (not session).

The explained behavior is erratic and very undesirable.
So, we were looking for a FIX based solution hoping it favors the (FIX) session and not the account overall.

Code:

    MarketDataRequest mdr = new MarketDataRequest();
    mdr.setSubscriptionRequestType(SubscriptionRequestTypeFactory.UNSUBSCRIBE);
    mdr.setFXCMTimingInterval(FXCMTimingIntervalFactory.TICK);
    mdr.setMDEntryTypeSet(MarketDataRequest.MDENTRYTYPESET_ALL);
    mdr.setMDReqID("zax");
    
    g.sendMessage(mdr);

Cheers

Oh ok. yes you are right. Subscribing for marketdatasnapshots in the Java API makes Trading Station subscribe too since the connection is account based. However, using FIX has the same effect so it is no different. If you want to trade one account using Java API or FIX and you want it to run independently of Trading Station you should create 2 accounts, one for each.