Skip to Content
0
Former Member
Apr 23, 2009 at 03:42 PM

Edge 3.1 with WACS

25 Views

When using the WACS installation of Edge 3.1, I only see a couple of folders deployed to the "...\Business Objects\BusinessObjects Enterprise 12.0\Web Content" folder and connected to IIS (such as Xcelsius and Analytical Reporting)

Everything else appears to be in the WACS wrapper. So when I hit InfoView it is hitting the logon.jsp in the following location:

...\Business Objects\BusinessObjects Enterprise 12.0\java\server\work\EDGESERVER.WebApplicationContainerServer\businessobjects\InfoViewApp\12\InfoViewApp-12.war\logon.jsp

However, there was a single occasion (which I couldn't replicate again) where when I restarted the WACS, the InfoViewApp war files were re-deployed (but none of the other web appliactions such as CmcApp, or PlatformServices, etc). It hasn't happened again, but it's good to know if this can occur for backing up customizations made to the SDK.

So if this mean the WACS actually executed the jsp from within the *.war containers - it seems to me this would mean it's running entirely using system RAM which would be a performance issue. Where as by using a web application server like Tomcat that runs the files after they've been exploded and unpackaged into a directory of their own you avoid performance degradation.

Is this documented somewhere and can some light be shed on why the Express install default uses the WACS as opposed to deploying Tomcat (which required an Advanced install)?