question

Upvotes
Accepted
20 6 5 9

UPA - loading appendix_a

When attempting to load the appendix_a file via Java UPA, the following error occurs when invoking DataDictionary.loadFieldDictionary("path to appendix_a file"):

Unable to load Appendix A field dictionary. Will attempt to download from provider.
Text: Illegal Rwf Type '!
!' (Line=36).

We've validated that both the file and absolute file path are correct. So,

1) I assume that we must load the appendix_a file

2) Assuming (1) is true, is DataDictionary.loadFieldDictionary the correct object and method to use?

The example UPA Consumer.java file only loads the field dictionary and enum type dictionary with no reference to the appendix_a file

elektronelektron-sdkrrtjavaeta-apielektron-transport-api
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
Accepted
9.5k 10 5 7

appendix_a is a dictionary for Marketfeed data which UPA does not support. UPA supports OMM data and the dictionary for it is RDMFieldDictionary. That's why UPA cannot load appendix_a and shows the error. You can find the dictionary for OMM data in <UPAJ package>\etc.

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
24.5k 86 10 22

Hi Paul,

The RMDFieldDictionary file is the replacement for the appendix_a file - so if the app is already loading the RDMFieldDictionary file then you should not be loading the appendix_a file.

appendix_a was used with the legacy SSL (and other legacy) connection types. For the current RSSL type connections the RDMFieldDictionary is required.

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.