RDC Support Question for CAT API 1.5.1.E1 using OMM WS.

Hi,

We are a customer of yours by the name of Charles Stanley, we have an issue when using the demo page on our TRIS/TREP server for troubleshooting.

When using demo/demopage/example_worldindices.html as a test page with Ajax the dacs username and position is passed using the example code below:

document.cookie ="AAAToken=cstris01" +

";path=/" +

";domain=domain.com";

RIS.nameType = 4;

RIS.applicationId = "227";

RIS.applicationName = "CAT";

RIS.position = "127.0.0.1";

We have now moved from Ajax using http:// to OMM WS using ws://.

Since moving to OMM WS the CAT API doesn’t pass the dacs username.

Please can you provide a workaround or fix.

Find more posts tagged with

trep

infrastructure

elektron

refinitiv-realtime

Accepted answers

wasin.w

Hello @Ashley.Pearson @abdus.hamid

I found the workaround by setting the following EWA’s RIS object properties:

Set RIS.nameType = 3
Set RIS.userName = DACS username

The RIS.nameType lets application specifies type of login request.

When nameType = 4, the ADS gets the DACS username from the document’s.cookie AAAToken.
When nameType = 3, the EWA 1.5 MVC/Widget components sends the DACS username as a Token to ADS. The application can set it via RIS.userName statement.

Based on my test, I cannot send a DACS username via HTTP document’s.cookie but it works fine with Token (nametype = 3).

Example Code of example_worldindice.html:

<div id="worldindices" style="padding: 20px; background-color: #FFFFFF;"></div>
   <script type="text/javascript">
   //document.cookie = "AAAToken=wasin" + ";path=/" + ";domain=domain.com"; //Comment document.cookie

RIS.nameType = 3; //Must be 3
   RIS.applicationId = "<Your application id>";
   RIS.applicationName = "<Your application name>";
   RIS.position = "<Your position>";
RIS.userName = "<Your DACS username>";

   var size = {
      width: 900,
      height: 800
   };

   var propertyModelTest = new Backbone.Model({…

Please note that the Web Browsers that support the WebSocket connection are Chrome, Firefox, IE10 and IE11. The IE7, IE8 and IE9 support the Ajax connection only.

All comments

wasin.w

Hello @abdus.hamid

First of all, please note that the CAT API version 1.5 and CAT Widget Framework are already end of life and no longer supported. The CAT API (now renamed as "EWA API") is a legacy product. I suggest you move to the strategic Elektron WebSocket API. The Elektron WebSocket API is a server side API that lets consumer connect and consume Elektron real time streaming data from local TREP (version 3.2.1 and above) and Elektron Real Time in Cloud (Elektron Data in Amazon Cloud) via a standard WebSocket connection. The benefit over CAT/EWA API are following:

It is a server side API, no client-side API (like RIS.js) required.
It uses Standard WebSocket and JSON message technologies, so any platforms and programming languages that support WebSocket/JSON can use Elektron WebSocket API. Unlike CAT API that supports only web browser and JavaScript.

Please find more detail in Elektron WebSocket API Quick Start and Tutorials pages.

The latest version of CAT API is EWA API 1.7.0 E6 which supports EWA Streaming API and EWA MVC only. You can set DACS credential with EWA 1.7.0 MVC RIS.position and TrisUI.initConnectionParameters functions with nameType = 3 (Token).

RIS.position = "IP Address/net"; 
TrisUI.initConnectionParameters("ADS URL", <domain>, <reconnectMaxTry>, <reconnectInterval>, <DACS ID>, <nameType>);

example:

RIS.position = "127.0.0.1/net"; 
TrisUI.initConnectionParameters("ws://172.20.33.11:15000", null, 5, 1000, "username", 3);

Note: Only EWA 1.7.0 that supports nameType and name parameters in TrisUI.initConnectionParameters() function.

Ashley.Pearson

@wasin.w

Hi Wasin,

Is there an equivalent of CAT example_worldindices.html in EWA? If not how can this be created?

Thanks,

Ashley.

wasin.w

Hello @Ashley.Pearson @abdus.hamid

I found the workaround by setting the following EWA’s RIS object properties:

Set RIS.nameType = 3
Set RIS.userName = DACS username

The RIS.nameType lets application specifies type of login request.

When nameType = 4, the ADS gets the DACS username from the document’s.cookie AAAToken.
When nameType = 3, the EWA 1.5 MVC/Widget components sends the DACS username as a Token to ADS. The application can set it via RIS.userName statement.

Based on my test, I cannot send a DACS username via HTTP document’s.cookie but it works fine with Token (nametype = 3).

Example Code of example_worldindice.html:

<div id="worldindices" style="padding: 20px; background-color: #FFFFFF;"></div>
   <script type="text/javascript">
   //document.cookie = "AAAToken=wasin" + ";path=/" + ";domain=domain.com"; //Comment document.cookie

RIS.nameType = 3; //Must be 3
   RIS.applicationId = "<Your application id>";
   RIS.applicationName = "<Your application name>";
   RIS.position = "<Your position>";
RIS.userName = "<Your DACS username>";

   var size = {
      width: 900,
      height: 800
   };

   var propertyModelTest = new Backbone.Model({…

Please note that the Web Browsers that support the WebSocket connection are Chrome, Firefox, IE10 and IE11. The IE7, IE8 and IE9 support the Ajax connection only.

abdus.hamid

HI Wasin,

Can you confirm whether this config change will have to be applied onto our TREP server and is it likely to help with our ADS crashing at least 2 or 3 times a day?

Also are you aware of when the version of ADS version 3.4.1 is likely to be released. W have been told that there is a tentative date of 31st March can you confirm how accurate that is likely to be.

Regards

Abdus Hamid

EXPLORE OUR SITES