question

Upvote
Accepted
75 1 1 6

EmaConfig.xml - Path for RDMFieldDictionary and enumtype.def

From Client:

Also with regards to the EmaConfig.xml file (and files it references, such as RDMFieldDictionary and enumtype.def), how do other clients go about handling relative paths for these files?

The locations of configuration files like these differ for us between testing and production environments. Typically we handle this by loading files as classpath resources, but that the file names specified in EmaConfig.xml must be relative physical paths.

We can re-write the file paths at run-time before calling the Refinitiv API, but wanted to make sure there isn't a better solution first.

ema-apijavaconfiguration
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvote
Accepted
17.5k 35 12 12

Hello @michael.theimer01

I checked both EMA Document and the API itself. The EMA API supports loading the entire EmaConfig.xml file from the classpath resources only, but not for the Dictionary files. The location dictionary files location now support relative physical paths string.

If the client needs this feature in the future release of the SDK, the client can submit an enhancement request to the product team via the https://my.refinitiv.com/content/mytr/en/feedback.html page.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
17.5k 35 12 12

Hello @michael.theimer01

The client can set <DictionaryType value="DictionaryType::ChannelDictionary"/> to let the API request and download Dictionary information from the infrastructure (ADS, RTO) for the application.

Please see more detail about the DictionaryType configuration from the Enterprise Message API (EMA) - Configuration Overview article.

Example:

<Consumer>
    <Name value="Consumer_1"/>
    <Channel value="Channel_1"/>
    <Dictionary value="Dictionary_1"/>
    <XmlTraceToStdout value="0"/>
</Consumer>
...
<Dictionary>
    <Name value="Dictionary_1"/>
    <!-- dictionaryType is optional: defaulted to ChannelDictionary" -->
    <!-- possible values: ChannelDictionary, FileDictionary -->
    <!-- if dictionaryType is set to ChannelDictionary, file names are ignored -->
    <DictionaryType value="DictionaryType::ChannelDictionary"/>
</Dictionary>


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
75 1 1 6

Thank you wasin.w for your answer, but client want to use RCC Contribution Channel and RCC don't have the option to download the dictionary. So the only option is a path I guess. Please correct me if I'm wrong.
Best Regards, Michael

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
75 1 1 6

Hi API Support Team, can you please confirm that RCC don't have the download option. Thank You.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
56.3k 145 45 65

@michael.theimer01

I checked the source directory of the DDS_TRCE provided by RCC.

<refreshMsg domainType="RSSL_DMT_SOURCE" streamId="2" containerType="RSSL_DT_MAP" flags="0x68 (RSSL_RFMF_HAS_MSG_KEY|RSSL_RFMF_SOLICITED|RSSL_RFMF_REFRESH_COMPLETE)" groupId="0" dataState="RSSL_DATA_OK" streamState="RSSL_STREAM_OPEN" code="RSSL_SC_NONE" text=""  dataSize="195">
    <key  flags="0x8 (RSSL_MKF_HAS_FILTER)"  filter="11"/>
    <dataBody>
        <map flags="0x0" countHint="0" keyPrimitiveType="RSSL_DT_UINT" containerType="RSSL_DT_FILTER_LIST" >
            <mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="10" >
                <filterList containerType="RSSL_DT_ELEMENT_LIST" countHint="0" flags="0x0">
                    <filterEntry id="1" action="RSSL_FTEA_SET_ENTRY" flags="0x0" containerType="RSSL_DT_ELEMENT_LIST">
                        <elementList flags="0x8 (RSSL_ELF_HAS_STANDARD_DATA)">
                            <elementEntry name="Name" dataType="RSSL_DT_ASCII_STRING" data="DDS_TRCE"/>
                            <elementEntry name="Vendor" dataType="RSSL_DT_ASCII_STRING" data="Refinitiv"/>
                            <elementEntry name="Capabilities" dataType="RSSL_DT_ARRAY">
                                <array itemLength="0" primitiveType="RSSL_DT_UINT">
                                    <arrayEntry data="127"/>
                                    <arrayEntry data="6"/>
                                </array>
                            </elementEntry>
                            <elementEntry name="QoS" dataType="RSSL_DT_ARRAY">
                                <array itemLength="0" primitiveType="RSSL_DT_QOS">
                                    <arrayEntry qosDynamic="0" qosRate="1" qosTimeliness="1"/>
                                </array>
                            </elementEntry>
                            <elementEntry name="SupportsOutOfBandSnapshots" dataType="RSSL_DT_UINT" data="0"/>
                        </elementList>
                    </filterEntry>
                   
            </mapEntry>
        </map>
    </dataBody>
</refreshMsg>

It doesn't contain 5 (RSSL_DMT_DICTIONARY) in its Capabilities and it doesn't provide the DictionariesProvided element entry.

1666241708118.png

Compared to the Real-Time service (ELEKTRON_DD), it provides both the RSSL_DMT_DICTIONARY (5) capability and the DictionariesProvided element entry.

            <mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="10002" >
                <filterList containerType="RSSL_DT_ELEMENT_LIST" countHint="0" flags="0x0">
                    <filterEntry id="1" action="RSSL_FTEA_SET_ENTRY" flags="0x0" containerType="RSSL_DT_ELEMENT_LIST">
                        <elementList flags="0x8 (RSSL_ELF_HAS_STANDARD_DATA)">
                            <elementEntry name="Name" dataType="RSSL_DT_ASCII_STRING" data="ELEKTRON_DD"/>
                            <elementEntry name="SupportsQoSRange" dataType="RSSL_DT_UINT" data="0"/>
                            <elementEntry name="QoS" dataType="RSSL_DT_ARRAY">
                                <array itemLength="0" primitiveType="RSSL_DT_QOS">
                                    <arrayEntry qosDynamic="0" qosRate="2" qosTimeliness="1"/>
                                </array>
                            </elementEntry>
                            <elementEntry name="Capabilities" dataType="RSSL_DT_ARRAY">
                                <array itemLength="1" primitiveType="RSSL_DT_UINT">
                                    <arrayEntry data="5"/>
                                    <arrayEntry data="6"/>
                                    <arrayEntry data="7"/>
                                   ...
                                </array>
                            </elementEntry>
                            <elementEntry name="DictionariesProvided" dataType="RSSL_DT_ARRAY">
                                <array itemLength="0" primitiveType="RSSL_DT_ASCII_STRING">
                                    <arrayEntry data="RWFFld"/>
                                    <arrayEntry data="RWFEnum"/>
                                </array>
                            </elementEntry>
                            <elementEntry name="DictionariesUsed" dataType="RSSL_DT_ARRAY">
                                <array itemLength="0" primitiveType="RSSL_DT_ASCII_STRING">
                                    <arrayEntry data="RWFFld"/>
                                    <arrayEntry data="RWFEnum"/>
                                </array>
                            </elementEntry>

According to this information, the DDS_TRCE service doesn't support dictionary requests.

However, to confirm the behavior in the product, please contact the Refinitiv Contributions Channel support team directly via MyRefinitv.


1666241708118.png (33.4 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.