High server load can be caused by Original WebX client activity, including:
- An excessive amount of activity on Original WebX clients.
- An excessive number of links to Original WebX clients.
- Large numbers of requests from external applications via the Simple Object Access Protocol (SOAP) interface.
To determine whether Original WebX activity is causing a high load on the server:
- Run the Server Status Tool.
- Expand the system, then the WebX folder, then select the Links category.
- Use the Links category to determine whether there is an excessive amount of Original WebX activity or an inappropriate number of Original WebX clients:
- Examine the number of Original WebX links. There should be 2 or 3 links per Original WebX client. If there appears to be an excessive number of Original 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 Original WebX clients are probably causing a high server load. Proceed to step 4.
If there are an appropriate number of Original WebX links and they have the correct Long Time entries, refer back to Diagnose and Resolve the Server Load Problems.
- Reduce the load on the server that is caused by the Original 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 Original WebX clients.