-
November 11th, 2014, 10:20 AM
#1
changing Listening TCP port
hello,
i have a lightstreamer installed on my server and the default Listening TCP port is 8080.
also i have IIS that listen to port 80.
is there a way to configure the lightstreamer to listen also on port 80?
-
November 12th, 2014, 09:33 AM
#2
Hi,
it is possible to change the default settings by modifying the configuration file "lightstreamer_conf.xml", that you can find in <LS_HOME>/conf directory (where LS_HOME is the path where you installed the Lightstreamer server). In order to change the default listening TCP port, you must replace the original settings in the <port> element under the "HTTP/HTTPS SERVER CONFIGURATION" block at the beginning of the file.
If your requirement is to have both Lightstreamer and IIS listening on port 80, you should consider to deploy them into different hosts, because TCP does not allow to bind more than one process on the same port.
Alternatively, you could also consider to plug two different network interfaces in the same host with two different IP addresses, allowing you to bind each process on its own listening interface on the same port 80. To do that, you have to properly configure the <listening_interface> element in the configuration file with the IP address of the network interface you assign to Lightstreamer server instance.
Could you please give us more details about your scenario in order to identify the deployment strategy that fits your requirement best?
Regards,
Gianluca
Last edited by gianluca.finocchiaro; November 12th, 2014 at 10:21 AM.
-
November 12th, 2014, 10:53 AM
#3
thanks for reply
are the two different network interfaces must be public ip for each interface or private ip for each interface with the same public ip?
Last edited by engcoder; November 12th, 2014 at 11:01 AM.
-
November 13th, 2014, 09:00 AM
#4
Hi,
in a simple network scenario where a single host must be accessible to the Internet, the configuration we propose allows a Lightstreamer server instance to accept incoming connection over a specific network interface bound on a public address and listening on port 80: in this way you are free to bind the IIS process on the other network interface, still on port 80.
Let me know if it is enough for your requirements.
Regards,
Gianluca
Last edited by gianluca.finocchiaro; November 13th, 2014 at 09:48 AM.
Similar Threads
-
By rvkvino in forum Client SDKs
Replies: 4
Last Post: September 24th, 2013, 09:28 AM
-
By emehmet in forum Adapter SDKs
Replies: 6
Last Post: August 30th, 2012, 10:54 PM
-
By mohamida in forum Client SDKs
Replies: 1
Last Post: June 14th, 2010, 09:23 AM
-
By simonef in forum Client SDKs
Replies: 1
Last Post: June 10th, 2008, 01:47 PM
-
By Mone in forum Client SDKs
Replies: 0
Last Post: November 9th, 2006, 04:12 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 04:00 PM.
Bookmarks