Soe-rest development in Java environment (first knowledge)

In ArcGIS, objects used for coarse-grained communication with data are called server objects. these server objects provide the ability to access, operate, analyze, and display data for the ArcGIS Server service. For example, when you access the map content through the map server object, you can locate the map through a locator development, GP server objects can be used for geographic processing. These server objects can provide geographical information services for transportation, communications, and other industries, such as map services, geocoding services, and GP services.

However, these serverobjects that are not assembled cannot provide complete process processing for the industry. Therefore, in the ArcGIS Server, we need a scalable framework that allows you to create Scalable Server objects, and build a custom solution. the development method of this extension Server Object is called the SOE development method.

In ArcGIS 10.1, arcgisserver does not support DCOM connections, which means that we cannot use more functions provided by ArcObjects through local connections, therefore, we recommend this new method to implement these functions, which is the SOE Server Object extension.

Necessity for development: SOE only needs to be created once and exists throughout the lifetime of the service object, so it can Cache Information and reuse, it also shows that the overhead is very expensive. You should also consider this when considering whether it is necessary to use SOE for expansion.

Developer requirements: Suitable for developers who have experience on multiple platforms. Developing a SOE usually uses AO,. Net or Java, rest or soap web service communication technology.

Soe supports soap (soap is a means of building Web Services and communicates with each other through XML) and rest (Table-like state transfer, web services can be fully utilized as a stateless client to locate resources through URLs and simplify HTTP protocol constraints.) These two access methods use powerful ao to expand service objects, it can also be run in a client without ao. The rest access mode is described below.

 

1. soe exists in the lifetime of the service object. a soe is usually initialized when the service object is created, and will only be created once during the lifetime of the service object. SOE has two necessary interfaces, init () and Shutdown (). it is used for SOE program initialization and cancellation respectively. For details, see the AO development help manual.

2. During SOE development, you must understand@ ServerobjectextpropertiesNote: It is a comment pair that is displayed during SOE deployment. The specific explanation is as follows:

L displayname-when you manage ArcGIS Server as the administrator, this name will be used in ArcGIS
The SOE display name in the Server Manager or ArcMap catalog window.

L description-this is mainly used to briefly describe SOE functions.
The deployment window of manager or ArcMap catalog is displayed.

L properties-this is mainly used as some external input parameters of the SOE program for interaction with the SOE program. This attribute can be used as the global attribute of the SOE program.

L allsoapcapabilities-when exposing your SOE as a web service, you cancreate functionality that can be enabled or disabled by an administrator ofarcgis for server. Such functionality
Is called a "Web Capability". thisparameter's value is a comma-separated list that holds all capabilities exposedby an SOE.

L defasosoapcapabilites-this parameter's value lists all web capabilitiesthat are enabled on the SOE by default.

3) Interface Description:

LCom. ESRI. ArcGIS. system. iobjectconstruct

This interface is only available in ArcGIS Server Manager. it is necessary to enter attributes to inherit from the global variables of SOE. It provides a very simple construct () method. After SOE is created, it is called after Init () initialization. You can use this method to obtain the input parameters.

L com. ESRI. ArcGIS. system. iobjectactivate

This is an optional inherited interface. Unless you need to perform logical operations before or after the request is sent, you do not need to inherit this interface.

· Activate ()-The client executes the command before making a request.

·Deactivate ()-The client completes the execution once.

LCom. ESRI. ArcGIS. system. irestrequesthandler

If you want to use rest WebService as your SOE development extension, you must inherit the irestrequesthandler interface, which provides two methods:

· Handlerestrequest ()-execute each HTTP request.

· Getschema ()-used to query ArcGIS rest handler resources and operation hierarchies when running SOE.

If you use the eclipse wizard for SOE development, these two methods are automatically generated, so that you can focus on the implementation of your resource methods and operation methods.