This document is archived and information here might be outdated.  Recommended version.

IServerObjectExtension Interface (ArcObjects .NET 10.8 SDK)
ArcObjects Help for .NET developers > ArcObjects Help for .NET developers > ArcObjects namespaces > Server > ESRI.ArcGIS.Server > Interfaces > IS > IServerObjectExtension Interface
ArcGIS Developer Help

IServerObjectExtension Interface

Provides access to the members that control a server object extension.

Product Availability

Available with ArcGIS Engine, ArcGIS Desktop, and ArcGIS Server.

When To Use

The IServerObjectExtension interface is used by developers who want to create their own server object extensions.


Name Description
Method Init Initializes and starts the server object specified by the IServerObjectHelper reference.
Method Shutdown Stops the server object specified by the IServerObjectHelper reference.

Classes that implement IServerObjectExtension

Classes Description
GraphicFeatureServer (esriCarto) The Graphic Feature Server component provides programmatic access to the Graphic Features.
JPIPServer (esriCarto) The JPIP Server Object Extension.
KmlServer (esriGlobeCore) The Kml Server Object Extension.
MobileServer (esriCarto) The Mobile Server Object Extension provides functionality for Mobile clients.
NAServer (esriNetworkAnalyst) Deprecated as of 10.0. A MapServer object extension for performing network analysis within a stateless environment.
WCSImageServer (esriCarto) The WCS Server Object Extension for Image Server services.
WCSServer (esriCarto) The WCS Server Object Extension.
WFSServer (esriGeoDatabaseDistributed) The WFS Server Object Extension.
WMSImageServer (esriCarto) The WMS Server Object Extension for Image Service.
WMSServer (esriCarto) The WMS Server Object Extension.
WPSServer (esriGeoprocessing) The WPS Server Object Extension.


Server objects may have extensions that extend their base functionality for more specialized uses. Each type of server object may have a set of extensions that can be enabled or disabled based on its configuration. ArcGIS for Server includes some server object extensions out of the box, and developers can extend ArcGIS for Server by writing their own server object extensions.

Server objects extensions also have SOAP interfaces for handling SOAP requests to execute methods and returning results as SOAP responses. This support for SOAP request handling makes it possible to expose server object extensions as Web services that can be consumed by clients across the Internet.

Developers can create their own server object extensions. The goal of creating a server object extension is to provide coarse-grained methods that do a lot of work in the server, rather than pay the cost of making a large number of calls into the server from the client.

Extending a server object rather than creating a generic COM object that is created on demand in the server context has the following advantages:

  1. Developers don�t need to explicitly create instances of a server object extension in a context. The server object extension is created by the GIS server when the server object instance itself is created.
  2. If the functionality that is exposed by the extension requires resources that can be costly to aquire, the initialization cost of creating the object is paid once when the server object and its extensions are initially created.
  3. If the functionionality that is exposed by the extension can benfit from some caching logic, it's possible to implement such logic because the cache will remain for as long as the server object instance remains in the pool.
  4. The ArcGIS Server administration applications can be extended to include custom property dialogs for configuring custom extensions for specific server object configurations.
  5. Unlike utility COM objects, server object extensions are registered and configured with specific server objects and are not for add-hoc use or use with an empty server context.

The process for creating a server object extensions is as follows:

IServerObjectExtension is a mandatory interface that must be supported by all server object extensions, and includes two methods: Init and Shutdown. This interface is used by the server object to manage the lifetime of the server object extension. The server object cocreates the server object extension and calls the Init method, handing it a back reference to the server object via the server object helper argument. The server object helper implements a weak reference on the server object. The extension can keep a strong reference on the server object helper (for example, in a member variable) but should not keep a strong reference on the server object. Extensions should get the server object from the server object helper in order to make any method calls on the server object and release the reference after making the method calls. Init is called once when the instance of the server object extension is created.

The Shutdown method informs the server object extension that the server object�s context is being shutdown and is about to go away. In response, the server object extension should release its reference on the server object helper as follows:

private IServerObjectHelper m_SOH;
public void Init(IServerObjectHelper pSOH)
  m_SOH = pSOH;
public void Shutdown()
  m_SOH = null;

In your custom methods, you use the server object helper to get a reference to the server object, for example:

IMapServer mapsrv = m_SOH.ServerObject as IMapServer;

Your server object extension can also optionally implement IObjectConstruct, IObjectActivate, and ILogSupport.