Making TREP and Bloomberg Platform work together

B-switchdiagWith Skyler B-switch, Thomson Reuters and Bloomberg platforms can work together seamlessly, quickly, simply and cost effectively.

Data locked into your existing platform? Need to hook up a legacy RFA application to Bloomberg terminal users? Want to publish from Bloomberg users to your TREP-RT applications? Or maybe you want to migrate completely from one platform to another?

B-switch adds an RFA interface to your Bloomberg Enterprise Platform. So all your TREP applications can see, subscribe and publish to it as if it were part of the TREP itself. And your Bloomberg API applications and terminals can see data on TREP too.

There are two flavours of B-switch:

B-switch-S: adds an ADS/P2PS style RFA interface for client applications to publish (via POST) and subscribe to data in and out of the Bloomberg Platform. Use this to hook up legacy applications, or share internal data between Eikon and Bloomberg desktop applications.

B-switch-H: subscribes to an existing TREP source (via an ADS/P2PS) and publishes the data into a Bloomberg Platform. Use B-switch-H to give Bloomberg API-based applications access to existing TREP sources, or to use Bloomberg Platform Contributions from an existing Marketlink or ATS.

How it works

B-switch is a software application, running in user mode on a Linux server of your choice. Through a simple 4-step installation and setup, you configure B-switch to appear as a TREP-RT/RMDS source, and to connect to the Bloomberg Enterprise Platform.

Thereafter any application using Bloomberg API (including Bloomberg Professional) to the Bloomberg Enterprise Platform or RFA (including Eikon) on your TREP-RT can share data seamlessly.

In order to take advantage of this capability, you will need to order the “Enterprise Publishing” capability for your Bloomberg Platform, and create services and schemas to suit the data you wish to publish.

If you are currently sharing data using a standard TREP/RMDS dictionary, then it is possible to create a Bloomberg service that mimics that format, reducing the need to consider new data models etc. On the other hand, if you have your own set of Field Ids for internal use, the Bloomberg schema can be created to match. We are happy to help you with this as we have an excellent relationship with Bloomberg to make the transition as smooth as possible.

What about persistence/resilience/backup?

B-switch acts only as a bridge – all data is routed through the Bloomberg Appliance and the appliance is treated as the “golden source”. If you want a resilient, persistent (and auditable) cache for your internal data, then take a look at Livecache – it’s the answer to all those requirements.

Of course, if you have any more complex requirements, we can cater for that too – simply contact us and we will be happy to help.