upgrade RFA7.2.1.L1 to RFA8.1 tibmsg to OMM

david.yano

The current configuration that the developer has is:

<node name="Connections">

<map/>

<node name="quantis-us-dev">

<map>

<entry key="connectionType" value="SSL"/>

<entry key="serverType" value="sapi"/>

<entry key="serverList" value="ads1-qa.ny.rbcds.com
ads2-qa.ny.rbcds.com"/>

<entry key="portNumber" value="8101"/>

<entry key="userName"
value="_quantis"/>

<entry key="downloadDataDict" value="true"/>

<entry key="downloadFullMarketFeedDataDict"
value="true"/>

<entry key="logEnabled" value="true"/>

<entry key="dacs_CbeEnabled"
value="false"/>

<entry key="dacs_SbePubEnabled" value="false"/>

<entry key="dacs_SbeSubEnabled" value="false"/>

</map>

</node>

I would like to know how to switch to OMM, what
configuration should be used. And please provide some sample codes and
configuration that I can try out before making code changes.

Please let me know if you need further details.

wasin.w V3

Hi @david.yano

Basically, you can
migrate the application from the TibMsg-MD Interface to the OMM connection via
the following tasks

1. re-write the application to use the RFA Java OMM interface (the
   OMM interface is not compatible with the MarketData and TibMsg interfaces)
2. create new RFA Java
   configuration connection node for the RSSL connection (or re-configure)
3. Configure the ADS server
   to enable the RSSL connection
4. If you are using Java
   1.6 or below, you need to upgrade to Java 1.7 or 1.8 as well

RFA Java Configurations

You need to re-configure (or create
new) RFA configuration connection node to use the RSSL connection instead. Please
check the section 3.2.1 RSSL Connection of the RFAJ_ConfigLoggingGuide.pdf
document in the RFA Java package for more detail.

Please see a brief comparison between the SSL and RSSL
configurations based on your SSL configurations below:

<node name="Connections">
    <map/>
        <node name="quantis-us-dev">
        <map>
            <entry key="connectionType" value="SSL"/>
            <entry key="serverType" value="sapi"/>
            <entry key="serverList" value="ads1-qa.ny.rbcds.com ads2-qa.ny.rbcds.com"/>
            <entry key="portNumber" value="8101"/>
            <entry key="userName" value="_quantis"/>
            <entry key="downloadDataDict" value="true"/>
            <entry key="downloadFullMarketFeedDataDict" value="true"/>
            <entry key="logEnabled" value="true"/>
            <entry key="dacs_CbeEnabled" value="false"/>
            <entry key="dacs_SbePubEnabled" value="false"/>
            <entry key="dacs_SbeSubEnabled" value="false"/>
        </map>
</node>

RSSL:

<node name="Connections">
    <map/>
        <node name="quantis-us-dev">
        <map>
            <entry key="connectionType" value="RSSL"/>
            <entry key="serverList" value="ads1-qa.ny.rbcds.com ads2-qa.ny.rbcds.com"/>
            <entry key="portNumber" value="{RSSL Port}"/>
    </map>
</node>

The above configurations
show that:

• The RSSL connection
  requires the “connectionType” as “RSSL”
• The “portNumber” must
  points to the ADS RSSL Port (default port is 14002)
• All dictionary
  configurations are removed,now they are
  programmatically in the code (send Dictionary request message to ADS or
  populate from local files)
• The “username” parameter
  is removed, now it is programmatically set in the code (via a login message)

Resources and Examples:

There are the following
OMM application migration resources, example code and guidance for developers:

1. The API migration guide
   document is available at the <RFA
   Package>\Docs\portal\api_migration.htm file in the RFA Java package
2. The RFA Java Tutorial that provides a step by step,
   video tutorial and source code to create the RFA Java OMM consumer application
   for you
3. The RFA Java Quick Start tutorial
4. I suggest you check the
   RFA Java StarterConsumer example which provides sample code that subscribes
   data to the ADS server with the OMM interface for developers. The
   StarterConsumer exmaple is available at <RFA Java
   package>\Examples\com\reuters\rfa\example\omm\cons folder. You can
   compare it with the MDSubDemo (<RFA Java
   package>\Legacy\Examples\com\reuters\rfa\legacyexample\session\mdsub) to
   see different between the OMM and MD interfaces application

Please be informed that
the RFA API is a feature-completed API (non-strategic). You may consider the
Elektron Message API – Java edition (EMA Java API) which is a part of the strategic Elektron SDK family.

EMA Java

The Elektron SDK Family (C++ and Java Editions) is a suite of modern and
open APIs that aim to simplify development through a strong focus on ease of
use and standardized access to a broad set of Thomson Reuters and proprietary
content and services.

The
Elektron SDK stack contains a set of capabilities ranging from low level
‘Transport’ interfaces to very high level content aware stateful interfaces. The
SDK consists of two following APIs

1. Eletrkon Transport API (ETA): Formerly known as UPA, or
   Ultra Performance API, this API provides access at the transport layer for
   Thomson Reuters Elektron Feeds and Thomson Reuters Enterprise Platform (TREP).
   This API provides the highest level of performance, scalability and
   tune-ability.
2. Elektron Message API (EMA): The Elektron Message API is a data-neutral,
   multi-threaded, ease-of-use API providing access to OMM and RWF data. As part
   of the Elektron Software Development Kit, or Elektron SDK, the Elektron Message
   API allows applications to consume and provide OMM data at the message level of
   the API stack.

Please note that the EMA API is built on top of ETA API.
Both of them connect and consume data from TREP/Elektron via RSSL connection.

The Elektron SDK Family (C++ and Java editions) already
supports MiFID II.

You can find more detail
regarding the EMA Java from the following resources

• Elektron SDK Family site (https://developers.thomsonreuters.com/elektron)
• Elektron SDK – Java site (https://developers.thomsonreuters.com/elektron/elektron-sdk-java)
• Developer Webinar:
  Introduction to Enterprise App Creation With Open-Source Elektron Message API (https://www.youtube.com/watch?v=2pyhYmgHxlU)
• Developer Webinar Recording:
  Why migrate from RFA to EMA API? (https://www.youtube.com/watch?v=CJihZV4m0rw)
• Elektron Message API Java
  Quick Start (https://developers.thomsonreuters.com/elektron/elektron-sdk-java/quick-start)