Improving Servicedesk Incident Template Loading
One of the more common concerns among new Servicedesk users is the speed with which the incident management templates load. The recent release of MR1 has improved that process, but there are still some complaints. The procedure outlined below will help reduce that time even further. Please note that there are some fields that may require access to external databases, such as the Symantec Management Platform database. If that database is slow in being accessed, load times will be affected until all data is received at the Servicedesk server.
Since each of the pages (templates) are contained in the SD.Feeder projects (and resulting web pages), creating an application pool specifically for those pages will allow them to receive a small performance gain. This is especially useful on Servicedesk servers that have a large amount of RAM available.
To create the application pool and assign it to the websites:
- Open up IIS
- Right-Click on Application Pools, Select New>Application Pool
- Name the Application Pool - suggested naming like"SD.Feeder_AppPool", etc.
- Right-Click on the newly created application pool, select Properties, then Select the Identity tab.
- If you are using KB 50197, then you will need to change the Application Pool Identity to reference the select the Configurable option and adding in the Domain Service account used in the KB article.
- Next, expand the Default Web Site, and locate all of the the SD.Feeder websites
- Right-Click on each one, Select Properties, and then, using the menu dropdown for Application pool:, select the Application pool previously created.
- Click OK
- Reset IIS and Restart the Logicbase Server extensions.
This will improve web page performance for the incident templates.