OPEN Market Data Services
ICONTACT US NOW on +81 90-8180-0212 Tokyo Japan
RECENT PROJECTS
SASS to RMDS NIP converter
SASS Publishers Network data is converted to OMM and re-published to the ADH cache via the NIP network. Downstream consumer can subscribe to original SASS 2 or 3 via an ADS with a regular RFA/SFC API based application without the need of a leacy RTIC componenent.
During the proejct migration period, the converter is configured to consume data from the NIP network, convert it to MFeed, and publish the MFeed data back to SASS Publishing Network for legacy SASS subscribers.
Legacy subscribers can still exist and receive the published data even after the SASS publisher has migrated to a NIP publisher. The RTIC is removed thereafter from the system once all the legacy SASS subscribers are
moved to consume data from the ADS with a newly developed application.
The final step is the migration of all legacy SASS publisher to NIP OMM publishers completing the final phase of project.
Application permission in DACS
If application permission was never turned on On from day one and now few years passed, you have several hundred users using a multide of a different application. Knowing what these applications are and which one should a user be permissioned to use can be a dounting task.
Some legacy application did not even sent a unique & defined application id during the DACS login process resulting in the API to send a default value of "256". (Def_Ssl_App) .Dacs tools showed hundred of users being connected, but only a few being correctly identified with the correct application name. Others were either incorrectly mapped or showed just (Def_Ssl_app) i.e. application 256.
In this condition it would be impossible to manage application permissioning. Not if it is not possible to identify what is what and used from who.
Our developed tools were are able to audit users and and usage and produce guidances to identify applications sending the incorrect app id's. Further more our tools were able to automatically assign the application permission to several hundred user at the push of a button without the complication of reading from a paper list and set them on one by one on the DACS UI interface.
An on site consutant knowledgeble of most reuters API's lisoned with the clients developers in guiding them to make appropiate changes that assured that the correct pre-assigned application id was sent along during connection with DACS and other RMDS/TREP infrastructure components.