OpenDACS en MUREX 3.1 Equity

Hola Refinitiv Developer Community,

Os escribo porque estamos haciendo pruebas del api de OpenDACS para un entorno de Murex (Murex 3.1 Equity) y estamos obteniendo algunas evidencias que nos extrañan.

Por ejemplo, en el siguiente mensaje para la consulta del instrumento SAN.MC refleja un deny y los mensajes de rechazo son los que aparecen en la siguiente captura:

No comprendemos por qué el mensaje de DACS son varios para un único instrumento e incluye el siguiente rechazo:

‘User req to IDN for Prod – WWEIKON’.
‘User req to IDN for Prod – SDFBEDATA’.
‘User req to IDN for Prod – WWIRETMM’.

¿Por qué estos mensajes cuando:

El usuario de aplicación no tiene ninguno de estos Códigos.
El instrumento SAN.MC se distribuye y permisiona a través del código MCE.

Gracias de antemano.

Un cordial saludo,

Antonio

Find more posts tagged with

trep

elektron

DACS

refinitiv-realtime

open-dacs

Accepted answers

veerapath.rungruengrayubkul

Hi @Antonio Santander

For content based entitlements, a particular data item will have a set of codes called Permissionable Entities (PEs) associated with it. In DACS, Permissionable Entity (PE) codes are mapped to various products, exchanges and vendors so that they can be used to determine permission.

The PE of the SAN.MC RIC currently is 2989 which can be mapped to various products and exchange. You can find mapped products and exchanges from

- Product Code Look up

- Item requirement menu on DACS UI

By default, user only needs permission for one of the product and one of the exchange in the list. This means that you can just grant only an available product for the user.

All comments

pimchaya.wongrukun01

Hello @Antonio Santander

Some instruments require permission of several products. As you have seen in the messages for SAN.MC instrument which requires the permission of product named WWEIKON, SDFBEDATA, WWIRETMM etc. This depends on the feed (provider) who publishes the instruments’ data and permission.

Each user profile in DACS contains the list of allowed and denied products. Hence, you should contact DACS admin who can help you to allow the products required for SAN.MC instrument in the application user profile.

Antonio Santander

Hi @Pimchaya.Wongrukun,

First of all, thanks for your answer.

We have been reviewing your comment and unfortunately it does not meet what we are looking for because our question is related with how the OpenDACS API Works. In addition to this and to clarify, we are the DACS Admin.

Any additional contribution will be welcomed.

Thanks and regards,

Antonio

pimchaya.wongrukun01

Hello @Antonio Santander

You can refer to An Introduction to the DACS Entitlement System for OpenDACS Developers to understand more about DACS and openDACS.

Based on the error messages, Content based entitlement (CBE) check is performed. The overview steps to perform CBE check using OpenDACS are below:

Log in to DACS then a handle is returned. The handle is the reference to the user.
Perform CBE check by sending the list of permission entitlement(PE; a number) of the instrument(e.g. SAN.MC) with the handle got from the login result to DACS. A PE can be Product-PE(as in your case) or Exchange-PE. As far as I know, a PE can map to one or multiple Products and a Product can map to one or multiple PEs.
DACS checks the user profile against the given list of PEs. Then, it returns the result if the user is allowed or denied accessing this instrument. If the user is denied, you will get the error text with the required Products or Exchanges the user does not have permission.

According to step 2, the list of PEs of the instrument is in a Refresh message published by the feed. OpenDACS does not have function to get this list. The application can get this list by subscribing the instrument(e.g. SAN.MC) and retrieve the list of PEs in the refresh message (the first data message). For the complete workflow and example source code to perform CBE check using OpenDACs, please refer to Tutorial 5 - Integrating DacsClient with StarterConsumer . If you have any difficulties to access this page, please contact rdc.administrator@thomsonreuters.com

However, if your application connects to ADS which enables DACS feature. ADS will perform this (all steps above) so you just login to ADS and get the data or the Access Denied error. Your application does not need to use OpenDACS.

Hope this help. If not, please clarify what is your problem or requirement.

Antonio Santander

Hi again @Pimchaya.Wongrukun,

Thanks a lot for your answer.

Just to point out a couple of things:

1. We understand what you mention in your steps; however, some Products-PE cannot be permissioned for an application and/or for an end user DACS login in terms of Refinitiv Compliance Rules. That's why, we cannot actívate, for instance the WWIRETMM to an end-user (natural person).

2. As we stated in our first entry, we do not understand why the CBE message includes Products-PE which are not permissioned in any of our servers, neither for an enterprise application dacs logins, nor for an end-user logins.

Any additional contribution will be welcomed.

Thanks and regards,

Antonio

pimchaya.wongrukun01

Hello @Antonio Santander

Thank you for the given info.

What component that the application shown in the image above connects to?

Dacs sink deamon to connect to DACS

2. ADS(TREP component). Default ports are 14002 and 8101.

3. The other. Please specify.

veerapath.rungruengrayubkul

Hi @Antonio Santander

The PE of the SAN.MC RIC currently is 2989 which can be mapped to various products and exchange. You can find mapped products and exchanges from

- Product Code Look up

- Item requirement menu on DACS UI

By default, user only needs permission for one of the product and one of the exchange in the list. This means that you can just grant only an available product for the user.

EXPLORE OUR SITES