The CommuniGate Pro Server dynamically creates, runs, and removes Real-Time Nodes.
A Node is an internal CommuniGate Pro Server object that can receive Signal Requests and produce Responses for those Requests. A Node can also send Requests and process Responses.
Various CommuniGate Pro components and modules use Nodes to implement Signaling functions:
You can use the WebAdmin Interface to configure the Nodes component. Open the Real-Time pages in the Settings realm, then open the Nodes page:
Log: Use this setting to specify the type of information the Local Nodes component should put in the Server Log. Usually you should use the Failure (unrecoverable failures only), Major (failures and major events), or Problems (failures, major events, and non-fatal errors) levels. When you experience problems with the Local Nodes component, you may want to set the Log Level setting to Low-Level or All Info: in this case the Node processing internals will be recorded in the System Log. When the problem is solved, set the Log Level setting to its regular value, otherwise your System Log files will grow in size very quickly. The Local Nodes component records in the System Log are marked with the NODE tag.
Processors: The Local Nodes component uses several simultaneous processors (threads) to process Nodes. One processor can handle several Nodes tasks. If you use many Nodes implementing time-consuming operations (complex Real-Time Applications, etc.) you should allow the component to use more processors.
Object Limit: This setting specifies how many Nodes the component can handle at the same time. If this limit is exceeded, attempts to create new Nodes result in an error.
Event Limit: This setting specifies the critical number of unprocessed events (sent to all active Nodes). If this number is exceeded, the component is overloaded (the component Processors cannot handle events as they appear), and attempts to create new Nodes result in an error.