Vikram,
Here is an interesting tidbit I got in my BOE330 class today. I was trying to research it for better understanding and saw this thread. I'll share what I learned but I can't profess to fully understand it.
In the BI Launchpad, look at Preferences for WEBI. There will be options for "view" and for "modify". Based on those settings, the processing of the WEBI will vary.
- DHTML and Rich Internet Client will process through the WebIntelligenceProcessingServer
- Web/ActiveX will actually process through your Web Application Server
So instead of troubleshooting your WEBI servers, it looks like you need to make sure your Web Application Server isn't the culprit that is causing these hangs. The number of simultaneous connections is quite different for these two. These are the recommended maximums to set. I would guess that you might be hitting the max for your Web Application Server which makes you "wait" until a connection is free.
- WebIntelligenceProcessingServer = 25 simultaneous connections per instance (cpu).
- Web Application Server = 100 simultaneous requests per core for the Java viewer. 50 simultaneous requests per core for the HTML viewer.
What you see when you Schedule the report is consistent with this. It's another similar setting. When you schedule a report, down under Destinations you will specify how the report will be "viewed" by the recipient. The same applies here too. If the reports chooses DHTML as the viewer for that delivery then it is using WEBI, which you seem to have working ok.
If you Schedule a report to deliver as "Web" (on the Web Application Server) but the recipient wants to view it in DHTML or the Rich Internet Client, then it will need to convert and that is done on the WEBI Processing Server.
Good luck.
-Richard