Ok I can see from reading James’s post: http://www.spatiallyadjusted.com/2007/03/23/the-webadf-licensing-issue-revisited/, he is not happy with about the fact that the ADF has to be licensed if you want to run it on another machine. I know quite a few people are unhappy about this and as I mentioned in yesterdays post it is a highly debated topic. I also mentioned I cannot really comment on this issue but I can provide some help for people out there that are being affected by it.
Rather than complaining now about the issue, I think you have to tackle issue on a project specific basis. I think you need to look very closely at your customer needs and also understand quite thoroughly the capabilities of ArcGIS Server 9.2. Like someone mentioned “that is the business model for today” so we have to work with it.
The need to have the ADF running on another machine has been lessened in ArcGIS Server 9.2. I know quite a few customers still “want” a 3-tier architecture, but you can work around this. The ADF is fast!, very fast in fact!. Depending on the complexity of applications you are creating for users, the majority of the applications are going to either make extensive use of the ADF or the ArcGIS Server or both. If you are making extensive use of the ArcGIS Server then you are obviously doing a lot of work against the SOC’s and intensive geoprocessing tasks or editing. Even with this you need to measure it. If you are developing an application that is viewing and browsing with some searching then you are making use of the ADF so the utilisation of the ArcGIS Server is nothing.
So, let’s look at a scenario. You are developing an AJAX web based viewing application for a customer. The application makes use of cached layers, and has a searching capability as well. The user can type something into the search and if instantly zoomed to the location which is also highlighted using the graphics layer. Pretty simple application yea? Alright well let’s look at what’s happening behind the scenes. This application would make extensive use of the ADF. It does not need ArcGIS Server to do any of things tasks mentioned. Why? Ok so this comes down to design and implementation. You can design the searching to make a webservice call which would be sitting at your business logic tier so that covers that side of things. For the maps, browsing, scrolling this we will configure ArcGIS Server to serve our cached tiles. These will be served out by the ADF. So ArcGIS Server is doing nothing. Now can someone justify to me why you would want to the place the ADF on a separate machine when the utilisation on the ArcGIS Server is 0?
That same scenario also applies depending on the editing you are doing. I know the thresholds very well as I have done extensive testing with the ADF and ArcGIS Server 9.2. I think the point I’m trying to get across is that tackle it on a project to project basis. Know the needs of the customer well and then come up with innovative ideas to implement it. Make the customer understand the ArcGIS Server 9.2 architecture. For a web based application you should be making use of cached services. If you are not I would re-think the reasons behind it. It instantly takes the load of ArcGIS server and also makes the maps instantaneous. Suddenly for a viewing application that makes your ArcGIS Server redundant!
In my last project – a truly enterprise application – the web UI was hosted both on the company’s web servers (a shared platform, many machines in a DMZ behind a firewall) and on the intranet platform (different authentication/authorization), also a shared platform. The AGS and GIS-related services were running on a separate, dedicated machine. This is a very typical enterprise setup: shared platforms are very important because they are relatively cheap (because the IT costs are spread out over many customers = business units), are well balanced, etc, while dedicated machines are much, much more expensive and used for special OS environments only.
My impression of the new license strategy is that ESRI is still equating "enterprise" with "enterprise GIS department". Real enterprises have IT departments (the infra guys) that nowadays prescribe deployment strategies that are moving away from ESRI’s architectural blueprints.
"Now can someone justify to me why you would want to the place the ADF on a separate machine when the utilisation on the ArcGIS Server is 0?"
There are several things wrong with this statement. For starters, look at the names of the products we are talking about. The D in ADF stands for Developer. It’s tough to explain to clients why they are paying extra for something named Developer when you are the developer trying to deliver a polished application. Secondly the S in AGS is for Server. If the application that you mention is not using ArcGIS Server in anyway then something is wrong with either the architecture or the naming convention. Server implies (and used to imply to ESRI) that this is a powerful machine with minimal user interaction. It’s a rack server in a closet that doesn’t have iTunes on it because you use the horsepower. Your application (or rather ESRI’s suggested implementation of it) has this workhorse of a server sitting around doing nothing on it expect housing some expensive software.
While I’m up here on my soapbox: Is there another adf in the world that is licensed or this expensive? Is there an IT disciple out there today that would recommend installing all components of an application on a single machine because the software vendor asked nicely?
If the licensing architecture was the way it was supposed to be (or even the way it will be shortly) then ESRI executives would have no problem defending it along with the licensing scheme.
Based on the rantings at the conference it sounds like ESRI would like for the users to tell them how to make, use and charge for their products. I don’t have an issue with this but I honestly don’t think they know how to listen yet.