Managing web service performance issues
This section describes configuration changes that might be required when using web services with the AR System server.
Managing the number of server threads
If an AR System server calls itself through a web service, twice the number of fast and list threads are used. Therefore, the minimum number of fast and list threads should be more than two. The number of server threads should be two times the expected number of users that will use the web-services feature if they are consuming on the same server.
Because each web service call consumes two threads, it is easy to get into a deadlock situation by running out of threads.
To consume a web service created on the same AR System server, you must increase the number of threads. To increase the number of server threads, open the AR System Administration: Server Information form, select the Ports and Queues tab, and adjust the number of threads.
Setting the time-out
If an external web service is too slow, the AR System server times out in 40 seconds, by default. Set the time-out to 20 seconds.
You must restart the AR System Server if you change the web service time-out in the Centralized Configuration.
To modify the time-out setting, perform the following:
- In a browser, open the BMC Remedy AR System Administration Console, and click System > General > Centralized Configuration.
- In the AR System Configuration Generic UI form, from the Component Name list, select the com.bmc.arsys.server.extension. webservice component.
- From the settings table, select the timeout setting.
- Edit the timeout setting value, and click Apply.
- Click Close.
AR System Server behavior when calculating the web service timeout
When you set the Filter API Timeout parameter and the Web Service API Timeout parameter, the web service time-out is calculated by using the following formula:
Filter API Timeout parameter value – 5.
After applying the formula, the lesser value from the Filter API Timeout parameter or the Web Service API Timeout parameter is considered as the web service timeout value.
Refer to the following examples:
If the Web Service API Timeout parameter value is 100 seconds and the Filter API Timeout parameter value is 102 seconds, the web service timeout is calculated as follows:
102 – 5. The web service timeout is 97 seconds.
If the Web Service API Timeout parameter value is 105 seconds and the Filter API Timeout parameter value is 100 seconds, the web service timeout value is calculated as follows:
100 - 5. The web service timeout is 95 seconds.