I'm going to test BO E6 and I'm wondering wich http/aplication server would be better :confused: . We are currently using BO5.1.3/2.6.3 in a W2000 environment with IIS, and the only good reason I've found to change to Apache&Tomcat is that Auditor is not supported with our current web server.
Are there any other advantages / disadvantages of using apache&tomcat and IIS, in terms of functionality, performance and scalability? Any comments would be greatly apreciated.
If your a Windows shop, you may have more in-house experience with IIS⦠being that is a Microsoft product. It takes less fuss to get IIS set-up. Plus both the app and web server are all in one product.
Whereas, Tomcat/Apache is open sourceā¦having to rely on the open source community for support(documentation). You need to set up the bridge between the two products (mod_jk.dll) This can be a little tricky.
BO does a good job of supporting either stack⦠I just had a support call on my Sun OS Apache.Tomcat stack with V6.1 and the lady was able to solve my problem in 15 minutesā¦
Which one is better? who knows⦠its like picking chevy or a ford⦠they both get the job done.
If you are a COM shop use IIS if you are a java shop use Apache (assuming you are on Windows servers).
When we upgrade from 5 to 6 we will migrate from IIS to Apache. Not because IIS is not a good platform, because we are a J2EE shop and we will want to incorporate Webi into our in-house development at some point. It also gives me the opportunity for an easy move to a ux machine if our usage begins to raise faster than anticipated.
In the test lab we spun up the IIS and Apache versions and found them to be similar in performance (on the same class of machine) and stability.
Weāre running v6.1 in a Windows 2000 environment with IIS and we just ordered Auditor. Will Auditor not be supported with our setup? Am I reading this right?
From what Iāve read in the PAR (Product Availability Report), Auditor only works with JSP (Apache and Tomcat) on Windows 2000. Keep in mind that weāre talking just about the GUI interface for Auditor. The reports and universes would still work without using the JSP-based GUI.
The GUI is pretty nice. You can build some nice dashboards.
We asked our sales rep about Auditor and they said things changed with v6.1. Through v6.0 it was only available in a JSP version, so you were forced to use Apache/Tomcat, but now it can work with IIS. Our system admin is very relieved to hear this. (-:
Steve, what functionality is not able in Infoview with the IIS platform? I talked to BO people and they told me that functionality was the same in both platforms. Can you give me some examples?
We are not using the SDK at the moment, but Iāll take that into my mind for the future
Business Objects recommended us using JSP, they said it would be more scalable.
There is something that I found very interesting: we tested BO E6 with apache&tomcat and we noticed that wiqt processes consumed less CPU than in 2.7.x, but tomcat processes were sometimes very active⦠BO said that this behaviour is normal since now part of the process is done in the application server. Any comments?
Our sales rep recanted what he told us earlier. He checked into it further and found out that ASP is not currently available for Auditor. Apparently IIS is supported with v6.1, but we would need to use WebLogic 6.1 as the JSP engine. Alternatively, we can switch to an Apache configuration with Tomcat as the JSP engine.
Steve: When you talk about interactive HTML viewing does that only work for reports which were created with Webi? Do you get the same functionality if your reports are created in Full Client and accessed through Webi?
Only WebI reports have the interactive functionality.
I feel much better now. Not that you wonāt be able to use Auditor on ASP, but that I could read the PAR correctly. There are so many products now that the PAR is pretty complex. Itās nice to know I can figure it out.
However, the PAR is pretty clear that Auditor needs Tomat and Apache. It probably works fine with IIS and something else, but BO the supported stack is via Tomcat and Apache.
Seems we keep beating a dead horse on this Interactive HTML issue. However, I am using W2K SP4 with IIS and I am able to Add/Sort/Filter columns without returning to the query panel screen.
Sure would be nice to have a more definitive answer from BusObj on JSP vs. ASP.
I like ASP but since the Auditor and AF need JSP i move to JSP. When i moved to JSP i have a problem with togle draft/page mode, so i switch back to ASP and wait whether minor release e6.1a have solved that problem or not.
Steve K,
Is it ill-advised to install Tomcat alongside our IIS6 ASP pages on the same Win2003 server?
We want to turn on Auditor, but since it is only JSP, will we be risking it if we run Infoview & Webi as ASP and Auditor as JSP from the same primary node server?
Steve H.
Auditor has some terrific universe and some very nice reports. These universes and reports will work just fine with IIS and ASP. If you want the fancy GUI that goes with Auditor, then you need JSP.
I believe that, over time, youāll grow tired of the fancy interface and simply run the Audit reports and use the universes for ad-hoc. Weāve been running Auditor for years and have never even configured the GUI.
Also, thereās nothing preventing you from implementing Auditor using Tomcat on the exact same server that you have running WebI with IIS/ASP.
Personally, I would run IIS with Tomcat and just use ASP for everything.
According to the PAR 6.1.3 is not supported with IIS as a web server only 6.5.1, it would be interesting to hear what tech support say about 6.1.3,
Again as an app server you would have to use tomcat or another bridged piece of software. Like you said!
I have a nice doc on bridging IIS6 and tomcat 5 if anyone wants it