Porting VB adapter to Lighstreamer 6.03

Dear all,
i am porting an old .NET Visual Basic adapter (that worked for years and was ported from Lighstreamer 4 to 5 without problems) to Lighstreamer 6.03. The adapter was made in 2010, based on the PROXY_HELLOWORLD demo, and also the name of the adapter has been kept the same, so I have copied the new version 6 folder PROXY_HELLOWORLD in the \adapters folder. In Visual Studio, I replaced the project reference from "DonNetAdapter_N2" to the new "DotNetAdapter.dll" of 6.03.
The project has compiled OK with Visual Studio 2015, Lightstreamer starts and waits for the adapter (waiting for a connection on port 6662/6661..) and goes on when the adapter starts (arriving to: "listening to *:8080"). In my adapter, the Init method gets called by Lighstreamer and also SetListener is called. Lighstreamer and adapter seem connected as usual.

The problem is that, when I open the usual Index.html page that worked with the old version, data are not updated. I can see that my Subscribe function is NOT called as it should, when I open the html page.
If I terminate the adapter, then Lightstreamer gets closed also, meaning that the connection between the two was still alive.
Any suggestions? Thank you! Paolo

Hi Paolo,

It is indeed a strange behavior.
The server's log file (logs/lightstreamer.log) shows something strange? Could you see the create_session client request? It seems correct?
Could you send the log file to us (to support@lightstreamer.com) for a check?

Regards,
Giuseppe

Quote:

---

Originally Posted by giuseppe.corti

Hi Paolo,

It is indeed a strange behavior.
The server's log file (logs/lightstreamer.log) shows something strange? Could you see the create_session client request? It seems correct?
Could you send the log file to us (to support@lightstreamer.com) for a check?

Regards,
Giuseppe

---

The log does not show anything strange.. I enclose it. I think that the problem is in the browser side. Lighstreamer sends the page and Internet Explorer shows it (from localhost:8080) but no data arrives. I will check if the sample page that I am using is correct, because I am working in a test environment and not in the production one.

Thank you, Paolo

Quote:

---

Originally Posted by ANYELEC

The log does not show anything strange.. I enclose it. I think that the problem is in the browser side. Lighstreamer sends the page and Internet Explorer shows it (from localhost:8080) but no data arrives. I will check if the sample page that I am using is correct, because I am working in a test environment and not in the production one.

Thank you, Paolo

---

Addition:
The final error you see in the log was when I stopped the adapter, I think this is normal.

Hi Paolo,

In the log there is no evidence of the create_request request incoming from the client.
This means, unless you changed the log level for LightstreamerLogger.requests logger, that the client attempts to open the session towards a different endpoint than localhost:8080.

I confirm that you should check the client page code and in particular:

Code:

---

var client = new LightstreamerClient(null,"PROXY_HELLOWORLD");

---

Regards,
Giuseppe

Quote:

---

Originally Posted by giuseppe.corti

Hi Paolo,

In the log there is no evidence of the create_request request incoming from the client.
This means, unless you changed the log level for LightstreamerLogger.requests logger, that the client attempts to open the session towards a different endpoint than localhost:8080.

I confirm that you should check the client page code and in particular:

Code:

---

var client = new LightstreamerClient(null,"PROXY_HELLOWORLD");

---

Regards,
Giuseppe

---

Thank you Giuseppe.

There is no such line in my index.html file (I enclose a simplified version: it was taken from the old installation).
I think that calls have changed with the new version.
By the way: the old version refers to "lscommons.js" and "lspushpage.js": I think they should be files in the Lighstreamer\pages folder, but they are not there.
Maybe you have a new skeleton for the html file, but I could not find it in your site.

Thanks for your help!

Paolo

Hi Paolo,

You can find the new version of the HelloWorld client example on GitHub: https://github.com/Lightstreamer/Lig...ent-javascript.
It relies on the new JavaScript Client library that implies changes in both the JS code and in the HTML definition of the cells.
However I expect that should not be a dramatic work to update your page.

Alternatively, it should be sufficient restore in the /pages folder of the new server the exact structure of the old page, with all the .js and .css files linked in the code.

Regards,
Giuseppe

Dear Giuseppe,

unfortunately I cannot understand why my application does not work after many trials, and I ask if you can try it for me.
In my attachment you may find my files.
LSadapter.exe is my adapter, that needs some files to work: please make the folder c:\LSadapter and copy LSadapter.INI in it. The executable also requires DotNetAdapter.dll and .pdb and lod4net.dll in the same folder as the executable. I do not send them because they were taken from the standard Lighstreamer installation.
The adapters folder contains my lightstreamer\adapters folder and the pages folder contains my test page in the lightstreamer\pages folder. This is a new version of the page, made from your last demo. I already sent you the old version of the page, that worked for years but not with Lightstreamer 6.0.3

Thank you very much for your help!!

Paolo

I wrote lod4net.dll, obviously it is log4net.dll...

Hi Paolo,

I confirm that I was able to run succesfuly your page with my local 6.0.3 installation.
The only step performed, in addition to those listed in your post, is to copy the file of the JavaScript library, lightstreamer.js, in the same folder as the indexN.html (lightstreamer\pages).
Then from my browser open: http://localhost:8080/indexN.html

Regards,
Giuseppe

Thank you Giuseppe, NOW IT WORKS!
Switching to 6.0.3, we would not like to adapt our existing Internet pages with the new sintax, it is preferable to leave the ones that worked with the previous version of Lighstreamer. I see that the Javascript code in the pages uses: LScommons.js, LSpushpage.js and misc.js. Should I copy these files to the same folder as the HTML pages? These files are not present in the distribution of Lighstreamer 6.0.3, should I take them from an older distribution?

Thank you! Paolo

Hi Paolo,

I can confirm that the files: LScommons.js, LSpushpage.js, and misc.js are not distributed since the new JavaScript Client library does not need them anymore (only the lightstreamer.js is needed).
And so you should pick them up from your original project.

Please also note that the proper folder where to copy the files depends upon how the script inclusion is declared in your HTML; referring to your original page:

HTML Code:

---

  <script language="JavaScript" src="LS/lscommons.js"></script>
  <script language="JavaScript" src="LS/lspushpage.js"></script>
 
  <script src="../commons/custom/misc.js" type="text/javascript"></script>

---

The files lscommons and lspushpage are expected in a subfolder LS while the misc file in the relative path "../commons/custom/".

Regards,
Giuseppe

Quote:

---

Originally Posted by giuseppe.corti

Hi Paolo,

I can confirm that the files: LScommons.js, LSpushpage.js, and misc.js are not distributed since the new JavaScript Client library does not need them anymore (only the lightstreamer.js is needed).
And so you should pick them up from your original project.

Please also note that the proper folder where to copy the files depends upon how the script inclusion is declared in your HTML; referring to your original page:

HTML Code:

---

  <script language="JavaScript" src="LS/lscommons.js"></script>
  <script language="JavaScript" src="LS/lspushpage.js"></script>
 
  <script src="../commons/custom/misc.js" type="text/javascript"></script>

---

The files lscommons and lspushpage are expected in a subfolder LS while the misc file in the relative path "../commons/custom/".

Regards,
Giuseppe

---

Dear Giuseppe,

I was abroad several days but now I started again to work on LightStreamer. My colleagues found the js files from old installations (misc.js was in the 4.1 and the others in 5.1.1) and copied them to the right folders.
Now something is received, but I get a new error that you may see in the included image. It looks like a date/time goes in the field that describes a variable; the error comes out continuously as soon as new data arrive. I am using the same test data that you tried (and still work correctly, I checked again) in the test page (indexN) made with the new javascripts.
Any suggestions, still trying to implement 6.0.3 without modifying web pages?

Thank you!

Paolo

Hi Paolo,

Yes, the error is quite strange it seems that the updated value of a field, a date/time I suppose, ends up in a position that is interpreted as an Item name.

As a rule of thumb newer Lightstreamer servers usually support older clients; this allows our customers to go live in production with the new server version and old clients, and then upgrade the clients at their convenience.
So, I expect that your old clients should work fine with the 6.0.3 server without any changes.
Please could you check if the client page used with the new server is exactly the same that the old one? Checking the server log file could you confirm that the application data of the updates are exactly the same between server 5 and server 6?

Regards,
Giuseppe

Quote:

---

Originally Posted by giuseppe.corti

Hi Paolo,

Yes, the error is quite strange it seems that the updated value of a field, a date/time I suppose, ends up in a position that is interpreted as an Item name.

As a rule of thumb newer Lightstreamer servers usually support older clients; this allows our customers to go live in production with the new server version and old clients, and then upgrade the clients at their convenience.
So, I expect that your old clients should work fine with the 6.0.3 server without any changes.
Please could you check if the client page used with the new server is exactly the same that the old one? Checking the server log file could you confirm that the application data of the updates are exactly the same between server 5 and server 6?

Regards,
Giuseppe

---

Dear Giuseppe,

the Lightstreamer installation is a new 6.0.3, with the only modifications needed to run it (i.e. the Java runtime folder in the LS.BAT file). In the \pages folder I copied the old index.html file (that you have) and the three .js files in the subfolders. I noticed that, in the old working installation, the ..\commons\custom\misc.js file was not present, so I also tried to take it away, but nothing changed. I enclose the log, where the last error is not significant because it occurred when I stopped the data adapter. With the same installation and data adapter, the other test page with the new format (indexN.html) works perfectly.
Thank you for your suggestions...

Paolo

Hi Paolo,

Unfortunately in the log file attached there is no evidence of any client session, and this is itself already strange.
Please could you re-run your page after changing this logger settings (lightstreamer_log_conf.xml):

Code:

---

        <logger name="LightstreamerLogger.requests" level="INFO"/>
        <logger name="LightstreamerLogger.subscriptions" level="DEBUG">
        <logger name="LightstreamerLogger.pump" level="DEBUG"/>

---

Regards,
Giuseppe

Quote:

---

Originally Posted by giuseppe.corti

Hi Paolo,

Unfortunately in the log file attached there is no evidence of any client session, and this is itself already strange.
Please could you re-run your page after changing this logger settings (lightstreamer_log_conf.xml):

Code:

---

        <logger name="LightstreamerLogger.requests" level="INFO"/>
        <logger name="LightstreamerLogger.subscriptions" level="DEBUG">
        <logger name="LightstreamerLogger.pump" level="DEBUG"/>

---

Regards,
Giuseppe

---

Dear Giuseppe,

I changed the log settings and repeated the test. You may see that the NEW (IndexN.html) page works, all the lines were recorded while I had that page open. Then I closed the page (Unsubscribe event logged) and entered the page written with the OLD code. While I am getting errors in the browser, there is no activity on the Lighstreamer side: there are no lines after the first unsubscribe. I think that there are compatibility problems in the page or in the js files called from it.
I enclose my simplified \pages folder. To save space, I deleted the two copies of Lightstreamer.js, one was in \pages\ and one was in \pages\Cambi. From the browser I open the page localhost:8080/Cambi/IndexR.html.

Thank you for your help, luckily the problem is not urgent!

Paolo

Hi Paolo,

I think that the issue is due to the fact that in LS folder some Lightstreamer library files are missing.
The old version required severals lib files: http://www.lightstreamer.com/repo/di...ient_html/lib/

Regards,
Giuseppe

Quote:

---

Originally Posted by giuseppe.corti

Hi Paolo,

I think that the issue is due to the fact that in LS folder some Lightstreamer library files are missing.
The old version required severals lib files: http://www.lightstreamer.com/repo/di...ient_html/lib/

Regards,
Giuseppe

---

Dear Giuseppe,
I am Always at the same point. Now, just to be sure, I copied all the .js files in all folders: the same folder of the page, the LS subfolder and the ..\commons\custom subfolder. The files are:
lightstreamer.js
lscommons.js
lsengine.js
lspushpage.js
misc.js.
Nothing changes, I Always have the same error.
I asked my customer to send me the complete \pages folder that now works in production with LS version 5.2, and put it in my test machine with LS 6.0.3. I do not get any error, but values are not updated. I noticed that the file lighstreamer.js is not present in the production machine, I think this was not used in old versions.
I am starting to think that we will have to modify the web pages on our server with the new syntax, what do you think?

Thank you again! Paolo

Hi Paolo,

I confirm that the upgrade to the new client library would be the best solution, however, is still valid the fact that the old version should work just fine, without any modification, with a 6.0.x server.

That said, some considerations on your recent efforts:

- in the LS subfolder you should add all the files of the client lib, not only the .js ones, and especially .html also.
- Yes, I confirm that lightstreamer.js is the file of the new library (since Lightstreamer JavaScript client library 6) in client lib 5 (and earlier) that file is not needed.
- In the version copied from production, you should check especially the misc.js file pointed by the page, and within that file, code lines like these:

Code:

---

      lsEngine.connection.setLSHost("http://localhost");        // (set the hostname when deploying on WEB SERVER)
      lsEngine.connection.setLSPort("8080");                        // (set the port when deploying on WEB SERVER)
      lsEngine.connection.setAdapterName("DEMO");        // the name of the Adapter Set

---

that allow you to target the right server.

Regards,
Giuseppe

Quote:

---

Originally Posted by giuseppe.corti

Hi Paolo,

I confirm that the upgrade to the new client library would be the best solution, however, is still valid the fact that the old version should work just fine, without any modification, with a 6.0.x server.

That said, some considerations on your recent efforts:

- in the LS subfolder you should add all the files of the client lib, not only the .js ones, and especially .html also.
- Yes, I confirm that lightstreamer.js is the file of the new library (since Lightstreamer JavaScript client library 6) in client lib 5 (and earlier) that file is not needed.
- In the version copied from production, you should check especially the misc.js file pointed by the page, and within that file, code lines like these:

Code:

---

      lsEngine.connection.setLSHost("http://localhost");        // (set the hostname when deploying on WEB SERVER)
      lsEngine.connection.setLSPort("8080");                        // (set the port when deploying on WEB SERVER)
      lsEngine.connection.setAdapterName("DEMO");        // the name of the Adapter Set

---

that allow you to target the right server.

Regards,
Giuseppe

---

Thank you Giuseppe, now also the old page, identical to the one in production, is working. I think there was a missing file also in the "pages" folder that I got from production. I wish to thank you especially for your patience!
Best regards, Paolo