In my role at Esri Australia resolving Enterprise and Developer support issues, there’s rarely a day that goes by where it’s not immensely useful to investigate communication between the different parts of a system. When a component of a GIS is not behaving as expected, forming a complete picture of the behaviour across the system is often instrumental in understanding the underlying cause. This article will focus on the special case of intercepting HTTP requests generated by applications running on top of Microsoft IIS, such as ArcGIS Web Adaptor and the Esri Resource Proxy.
Recently in the Australian media there has been a lot of commentary around the impending update to Australia’s primary datum. From GDA94 to GDA2020. It has even made the British media http://www.bbc.com/news/technology-36912700.
At Esri Australia this has prompted a lot of questions from clients in regards to the support of the new datum GDA2020 in ArcGIS. Will ArcGIS support GDA2020 and when will ArcGIS support GDA2020?
Before we start to answer these questions I think it is important we understand exactly what the new datum is and why Geoscience Australia is moving towards a new datum.
Have you ever wanted to include capabilities files with your OGC Service? An OGC service exposes service-level metadata through its capabilities file. The capabilities file is the XML response that clients receive when they make a GetCapabilities request on the service. Below is my step by step guide on how to complete this process for a WMS Service. To use external capabilities files with OGC services in ArcGIS, you will need to create the files for use with the service. In my situation I want my WMS service to support different versions of WMS protocols – for example 1.0.0, 1.1.0, 1.1.1 and 1.3.0. To do this I must create one capabilities file for each version of WMS.
Although there has been a great blog on this subject already (see: http://esriaustralia.wordpress.com/2011/02/17/the-new-arcgis-runtime/ ) there still seems to be a bit of confusion over what the ArcGIS Runtime actually is and what you can do with it. First of all ArcGIS Runtime is actually a series of 6 runtimes, each based on a specific platform. These cover IOS, Android, Windows Phone, Windows Mobile, Windows and Linux. So we have 4 runtimes for mobile and 2 runtimes for ArcGIS Desktop. When people refer to the “New ArcGIS Runtime”, most are referring to the Desktop version(s) and this is where I will focus this blog.
So what is it for?
ArcGIS Runtime will enable developers to build custom applications that can be easily distributed to users. Such applications may be required to deliver custom interfaces and/or automate of a set of tasks . Additionally there is a LOT of functionality within ArcGIS Desktop, but most users use only a fraction of it. Being able to strip out unrequired buttons, menus and the underlying code, libraries etc is a big bonus. Not only does this make an application more intuitive and streamlined, it also has the potential to reduce the size of the installation footprint and decrease licensing costs. Continue reading
There may be situations where you need to automate the Start/ Stop/ Restart/ Publishing of all or some of your ArcGIS Server Services. This may be for maintenance reasons (where you want to do a restart at a time when no users are logged on) or to account for updates to data (e.g. where a restart is required after adding new data for a time aware map service).
This can be achieved through the combined use of a handy little utility called AGSSOM, a Batch File and Task Scheduler in Windows. Continue reading