Ishmael is definitely a rock start amongst the Geogeeks here at the UC. Every session is packed – in fact yours truly is writing this on the floor. It also is a clear indication as to how important ArcGIS for Server is to the Esri community.
The simple message is that ArcGIS for Server has been on a diet and gone to a Black Ops boot camp. How?
No SOM and SOC. This increases scalability, robustness and ease of use. No DCOM in the server means that it ArcGIS Server is a pure web services server you can only talk to it via HTTP for remote/cloud access makes life a lot easier. This is why there are no Java or windows versions anymore due to this re architecture.
Don’t worry too much about your previous client developments as they will be compatible with 10.1 – you just won’t be able to take advantage of the new capabilities. You will of course have to republish your old 10 services in 10.1.
Some other highlights:
- The new admin tool will make life so much easier to manage your site.
- Server Object extensions will be easier to deploy.
- Login is richer with query tools to help search for issues.
- Optional Web Adaptor will be separate install to connect/integrate with IIS or Java based web servers – you can use the Web Adaptor to block access to admin services, security eg port access control.
- You can use Python scripting to help manage your website – particularly with repetitive tasks and analysing logs. Check the help on ArcGIS Resources and the Server blogs for more.
- A new concept for Server Admin called an ArcGIS Site can be used to help multi-installs – particularly multi machine, cloud or large enterprise deployments.
Esri’s Server technology has come such a long way from the old ArcViewIMS, ArcIMS and ArcGIS Server 9.0. ArcGIS for Server 10.1 is mainstream IT. You need web administrators to help you effectively deploy your ArcGIS for Server sites. We barely saw maps in this session; it was about architectures, ports, clustering, security and administration.