Video Screencast Help

ServiceDesk Performance - A Cheat to Cache the Forms and Processes Periodically

Created: 29 Jun 2010 • Updated: 01 Jul 2010 | 2 comments
Language Translations
mike.gibson's picture
+2 2 Votes
Login to vote

We have had a number of customers complaining about the time it takes to initially load up the feeder forms and log in.

This is mainly due to the amount of work required to load into memory the core Workflow and process manager applications the first time they are accessed.
Since they are recycled periodically, or due to a lack of activity in an environment that does not have 24/7 access to the service desk, a sufficient time gap will occur, and the first person to access service desk will have to wait 3-4 minutes to log their first call. (Usually the first country East of the US West coast that has a support team - Australia / Singapore / India )

The main Symantec response has been to increase the cache settings in IIS to hold the applications in memory for longer.

However, we decided to take a slightly different approach that effectively fires up your chosen forms and logs into process manager on a particular schedule, hence allowing the applications to recycle, whilst not affecting the natural order of recycling the applications.

I have included a web form project that does exactly this.
This project is a simple form full of iframes pointing to all of the main feeder forms and process manager.

It has been set so that every 5 minutes the browser automatically shuts down, and hence allows a scheduled task to run periodically to re-open this page.

The difficulty of getting the browser to shutdown was overcome by using the following java script which is embedded into the 'Close Dialog' page:


var browserName=navigator.appName;  if (browserName=="Netscape") {   function closynoshowsme()  {  window.open('','_parent','');  window.close();}  }  else {  if (browserName=="Microsoft Internet Explorer") 
{
  function closynoshowsme() 

window.opener='X';
window.open('','_parent','');
window.close();  } 

 }

This is called by the Body Custom Events as shown below.

(We use a similar trick to join the Feeder forms to the processes by using an iFrame to preserve security to link to the process, and then closing both windows at the end - but this will be in another article)

As long as the user that the scheduled task is running under is recognised for AD identification, or a suitable guest account is created, and the password cached in the user or SYSTEM context, then you can set any schedule you like to cache all of the pages you wish.

 

Comments 2 CommentsJump to latest comment

Harold.Moore's picture

What is the expierience?

0
Login to vote
JoeBolster's picture

All I need to do now is publish it and Than what make a task that calls it?  is that all?

Can I delete the frames of the projects I am not using?

0
Login to vote