ARCIMS Development Experience Summary (4) (Arcims Client Connector Selection)

Client selection. For IMS, HTML Viewer Java Standard Viewer Java Custom Viewer Java Standard Viewer, Java Custom Viewer features are similar. For programmers, Chinese customers come. Java Standard Viewer is basically not available. Typical fat clients, Image and Feature MapServices are available to download Applet, and the client is equipped with JRE. As Microsoft IE matures the APPLET's resistance and ArcGIS Server (Remote Data Analysis, Feature MapServices) matures, it is estimated that this fat client has nothing to use, at least I think it is like China. In the WebGIS project I have contacted, Applet is not a lot, and the government department is even less used by security. (Http://www.668map.com/) Use Applet, but if we have more business queries, analysis. It is estimated that the practice of putting the data into the buffer is hung. And if I want to add an easy application, the amount of data is more terrible. I personally is not optimistic about the prospect of Java Viewer.

HTML Viewer: DHTML and JavaScript implementation. With the popularity of the web program, the maturity of DHTML, JavaScript, CSS (perfect for different browsers has a unified standard, but the client IE is still boss). ArcGIS Server's client is also HTML View (no way .NET, J2EE or browser as the main client). In addition, HTML is so light, the page can be so beautiful, expanded, and maintenance does not need to be compiled. Although FEATURE MAPSERVICE is not supported, the application of Feature MapService can be implemented by ArcGIS Server. Connector selection. .NET LINK, ACTIVEX, AppSerLink, ColdFusion, General, Java, Servlet, WMS thinking is to encapsulate ArcXML, send requests to Arcims, and clients. The following provides examples of Arcims to explore the Servlet Connector, Javaconnector. Please configure an example of HTMLVIEW and JavaSconnector yourself.

Servlet Connector: Modify Viewer.htm so that JSForm.htm can be seen in the page. (

JSform.htm load map before code ... function passxml () {} ... loaded by the map ... function passxml () {var xmlresponse = ' < Output url = "http: // zhangkj: 8080 / output / txzy_zhangkj188425841.jpg" /> '; parent.mapframe.ProcessXML (XmlResponse);} ...... .. seen in aimsXML.js function function htmlSendToServer (URLString, XMLRequest, theType) and function processXML (theReplyIn) at a glance, htmlSendToServer send our portfolio arcXML to com.esri.esrimap.Esrimap? ServiceName, returned XMLResponse by the processXML display. The core code is these, and most of the JS files in the JavaScript folder are the arcxml string and resolution returned from Arcims from ArcIMS. Other JS files are DHTML, parameters, public functions, and more. It looks very scary. I personally think that the JS code in the HTMLVIEW example is high. But you must be familiar with these code, functions. Compared with other connections, HTMLVIEW can be said to be the easiest. Familiar with HTML, familiar with JavaScript, with ArcXML documents, this is enough. The rest is to construct different Arcxml with JavaScript, request Arcims, use DHTML, JavaScript display to return Arcxml. (You can take a look at JSPform.jsp, use the com.esri.AIMTier.io.ConnectionProxy class to request IMS service. And The above flow is almost.http: //support.esri.com/index.cfm? Fa = knowledgebase.techarticles.gateway & p = 16 & pf = 217 The above is good, from a deeper point of view, each connection

JAVACONNECTOR: Package the ArcXML document with Java objects. Combining ArcXML work is made by purely object-oriented Java language, com.esri.AIMS.MTIER.IO.CONNECTIONPROXY object requests an IMS server, returning a Java object response. Servlet Connector is a string, while Java Connector is a Java object. In this way, the advantages of Java language, the operability of Java objects, ease of use, and convenience are revealed. Javaconnector increases the Dynamic Dynamics of Arcims.

Map Map = new map (); map.initmap (MapCon, 750, false, false, false, false); map.setHeight (500); map.setwidth (400); map.refresh (); string URL = MAP. GetMapOutput (). getURL (); Map object package arcxml, map.refresh () requests IMS service. The request for the Map object includes the contents of the response. (In fact, Map.initmap also triggered a problem with the class library design requesting Get_ServerInfo.javaconnector.) Servlet Connector and Javaconnector

First, Performance Servlet Connector: Users download JavaScript files. Combine Arcxml is executed on the client. If the user machine is not too slow, performance should be the best, and the server pressure is also small. It is said that the IMS cluster is installed, and millions of users can support millions of users. JAVACONNECTOR: It is not a servlet connection. 1. The package of Java objects is running on the server. (However, negligible) 2, the performance loss established by the MAP object. Map.initmap (), map.refresh () must trigger request IMS. Operation a map to create a map of MAP

The practice of icons is impossible. There are two resolution to put the Map object in the session and the Map object pool. Put the Map object in Session, more users, the Web server is very pressure, and it is not feasible when multiple users. The MAP object pool, the passivation of the MAP object, activation (EJB proposal) is complex. Because different users are different from operating status (in ArcGIS9 Server, the status saving is a place worth studying). Use Javaconnector performance issues to consider. (Personally think that there is a problem with the Javaconnector class library. With the anti-compilation tool, the code design has improved places to solve the MAP object initialization problem).

Second, the function: Servlet Connector: All features of Arcxml. The problem is on the ArcXML and the ARCXML of the displayed response. Because these use JavaScript implementation. Have certain limitations. For example, I want to sort the query results of Arcxml. Realize the event. (ArcXML query does not support Order By). Do not operate with IMS service. Javaconnector: All features of ArcXML. There are many problems with the advantages of Java language. For example, in the previous sort. The dynamic layer is more convenient to achieve the superposition of the remote sensing image map. It is also possible to handle the original data in conjunction with the Java interface of ArcSDE.

to be continued.....