See: Description
Then to actually connect and start receiving messages you do the following:
MyOddsFeedListener listener = new MyOddsFeedListener();
MySDKGlobalEventsListener globalEventsListener = new MySDKGlobalEventsListener();
OddsFeedConfiguration config = OddsFeed.getOddsFeedConfigurationBuilder()
.setAccessToken("your-integration-token-here")
.selectIntegration()
.build();
OddsFeed oddsFeed = new OddsFeed(globalEventsListener, config);
OddsFeedSessionBuilder sessionBuilder = oddsFeed.getSessionBuilder();
sessionBuilder.setListener(listener).setMessageInterest(MessageInterest.AllMessages).build();
oddsFeed.open();
See OddsFeed, OddsFeedSessionBuilder, SDKGlobalEventsListener and OddsFeedListener for details.
That should be about it!
If you want to get available sport events, active tournaments, or all sports you can get the SportsInfoManager from the main OddsFeed instance:
SportsInfoManager sportsInfoManager = oddsFeed.getSportsInfoManager();
// Get all sports, translated in the desired locales
for (Sport sport : sportsInfoManager.getSports()) {
}
// Get all soccer active tournaments, the returned data will be translated in the desired locales
for (SportEvent tournament : sportsInfoManager.getActiveTournaments("soccer")) {
}
// Get all competitions scheduled for today
for (SportEvent sportEvent : sportsInfoManager.getCompetitionsFor(new Date())) {
}
// Get all live competitions
for (SportEvent sportEvent : sportsInfoManager.getLiveCompetitions()) {
}
Another more scalable way of listening to events is to have two different sessions one for high-priority messages and another for low-priority-messages. This means that the low priority messages will not prevent high-priority messages from getting processed (ex., BetSettlement is considered low-priority, OddsChange is considered high-priority). To create two different sessions for the high and low-priority messages you do the following:
MyOddsFeedListener listener = new MyOddsFeedListener();
MySDKGlobalEventsListener globalEventsListener = new MySDKGlobalEventsListener();
OddsFeedConfiguration config = OddsFeed.getOddsFeedConfigurationBuilder()
.setAccessToken("your-integration-token-here")
.selectIntegration()
.build();
OddsFeed oddsFeed = new OddsFeed(globalEventsListener, config);
OddsFeedSessionBuilder sessionBuilder = oddsFeed.getSessionBuilder();
sessionBuilder.setListener(listener).setMessageInterest(MessageInterest.HiPrioMessagesOnly).build();
sessionBuilder.setListener(listener).setMessageInterest(MessageInterest.LoPrioMessagesOnly).build();
oddsFeed.open();
Note that the same listener is used for both channels, but when creating the two different sessions,
different MessageInterest levels are provided. In this case, you will get two different threads doing the
processing of the different types of messages.
sessionBuilder.setListener(listener).setMessageInterest(MessageInterest.LiveMessagesOnly).build();
This kind of session will receive all messages except OddsChange
happening before the game starts (you will start receiving
OddsChange some minutes before the game starts)
and BetSettlement
resulting from confirmed results (you will still receive BetSettlments when the game ends,
but only after 15minutes or even later after the game confirms the match results).
If some malfunction of the system is detected(Sportradar subsystem stops working, alive interval violations,...), the SDK will dispatch a ProducerDown event, when this happens it is advised that you disable all the markets related to this producer.
When the SDK detects that the malfunction is corrected it will automatically reconnect and request the most recent odds information and any other missed messages(a recovery request will be executed), after the recovery is completed the ProducerUp event is dispatched, after the producer is up again you can safely re-enable all the markets.
If your system crashes or if you take down/restart your system you need to provide the timestamp of the last processed message per producer, so the SDK performs the recovery for the missed messages(the max time from the last processed message can not be more than 3 days). You can do this trough the ProducerManager available on the OddsFeed instance. If the last processed message timestamp is not provided, the SDK will perform a full recovery, beware: with a full recovery you do not recover any lost BetSettlement messages!
// as an example, we set the last message received timestamp to 2 days ago for the producer with the id 1(LiveOdds)
Calendar cal = Calendar.getInstance();
cal.add(Calendar.DATE, -2);
ProducerManager producerManager = oddsFeed.getProducerManager();
producerManager.setProducerLastMessageTimestamp(1, cal.getTime().getTime());
// session creation,...
oddsFeed.open(); // finally we open the feed
Copyright © 2016–2023. All rights reserved.