WebX Client Activity

High server load can be caused by WebX client activity, including:

To determine whether WebX activity is causing a high load on the server:

  1. Run the Server Status Tool.
  2. Expand the system, then the WebX folder, then select the Links category.
  3. Use the Links category to determine whether there is an excessive amount of WebX activity or an inappropriate number of WebX clients:
    • Examine the number of WebX links. There should be 2 or 3 links per WebX client. If there appears to be an excessive number of WebX links, contact Schneider Electric for advice.
    • Examine the Long Time entry for each link. If a link has a Long Time entry that is greater than 1000 ms, the WebX clients are probably causing a high server load. Proceed to step 4.

    If there are an appropriate number of WebX links and they have the correct Long Time entries, refer back to Diagnose and Resolve the Server Load Problems.

  4. Reduce the load on the server that is caused by the WebX links by either:
    • Stopping external applications from accessing the system via the SOAP interface. These applications are the most common web-related cause of high load on the server.
    • Checking that users are not performing tasks that place an unnecessary demand on the system. For example, if a user requires information about Events within a specific time period, they should display a filtered Events List. An unfiltered Events List will place a large demand on the system.
    • Upgrading the server hardware so that it can manage more links to WebX clients.

Disclaimer

ClearSCADA 2017 R2