| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| max MQTT Connections & SCADA node |
« View previous topic :: View next topic » |
| Author |
Message
|
| Qadeer_824 |
 Posted: Sun May 02, 2010 9:37 pm Post subject: max MQTT Connections & SCADA node |
 |
|
Acolyte
Joined: 04 Oct 2007
Posts: 59
|
Hi,
As per the online documentation for MQTT connectoins, the maximum number of MQTT connections that can be handled by a Broker is 2000.
However the SCADA node limits the number of active connections to a configuration property on the SCADA node (max Threads) with a default value of 500. Ie. A maximum of 500 client connections per SCADA port number. While it is possible to increase this default value, but as SCADA internally uses database tables (BSCADA…) in the Message Brokers DB schema, this value is apparently tied up with the value of maxappls and maxagents on DB2 (the database for Message Broker).
My query here is:
(a) what is the maximum value that can be set for the max Threads without affecting the performance?
(b) How does increasing the value of maxappls affect the message broker.
(c) i am looking at setting the value to approx 3000. Does this look like a very huge value for maxappls/maxagents?
(d) Is anyone aware of the future of SCADA/Real-time on WMB 7.0, as these nodes have been removed.
(e) Just out of curiosity, were the SCADA/Real-time nodes removed due to the removal of configmgr/broker databases?
Your help is really appreciated.
Thanks,
Qadeer |
|
| Back to top |
|
 |
| andypiper |
| Posted: Thu Dec 09, 2010 7:17 am Post subject: |
|
|
Acolyte
Joined: 29 Oct 2001
Posts: 59
Location: London
|
| It's a bit of a late reply, but the future of the SCADAInput node should now be clear - this functionality has been replaced by the WebSphere MQ Telemetry support available as an add-on for WebSphere MQ 7.0.1.3 and newer. The new Telemetry channels are significantly better at scaling than the SCADAInput node and the performance reports available on the SupportPacs site show many more than 2000 client connections. There is no real need for tuning here. More advanced topologies, including "concentrators", are possible by using the MQ Telemetry Daemon for Devices which is part of the WebSphere MQ Telemetry advanced client option. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
