CN101493825A - GIS middleware collocation and management method - Google Patents

Abstract

The present invention relates to geographic information system, especially a kind of GIS middleware configuration management method, its steps are as follows: 1) customer software creates heterogeneous data source information and transmits to data source driver manager; 2) data source driver manager according to The heterogeneous data source information loads the corresponding middleware interface and the heterogeneous data source driver; 3) the heterogeneous data source driver in the step 2) directly accesses the heterogeneous data source, and then returns the successful information to the data source Source driver manager, so far the connection between the data source and the corresponding data source driver is successful; 4) The client software sends out a request action, and the data source driver manager responds to the request, calls the corresponding data source driver to complete the actual processing of the data, and then reports to the client The software returns the processing result; 5) The client software displays the result data. This method does not require frequent data format conversion, and can realize the integration of multi-source data without a lot of repetitive labor.

Description

A GIS Middleware Configuration Management Method

technical field

The invention relates to a geographic information system, in particular to a GIS middleware configuration management method.

Background technique

At present, there are mainly three modes for the integration of GIS multi-source spatial data: one is spatial data exchange, which constrains and standardizes various existing geographic information systems by establishing a unified data exchange standard, and uses data exchange standards to exchange spatial data; The first is the data interoperability mode, which establishes an open geographic data interoperability specification and performs geographic information system interoperability; the third is the direct operation mode, which implements direct access, storage and spatial analysis of other software data formats in one GIS software.

The above three integration modes have the following disadvantages:

The data exchange mode is to convert data in other formats into the data format of the system through a special data conversion program, and copy it to the database or file of the current system. In order to exchange data with other systems, many softwares have formulated clear exchange formats, such as ArcInfo's E00 format and ArcView's Shapefile format. However, due to the lack of a unified description method for spatial objects, the information of the original data cannot be completely and accurately expressed after conversion, and some information is often lost. In addition, the process of converting data through the exchange format is relatively complicated. It is necessary to first use software A to output to a certain exchange format, and then use software B to import from the exchange format.

The data interoperability mode is a data sharing specification developed by the OpenGIS Consortium (OGC). GIS interoperability means that in the case of heterogeneous databases and distributed computing, GIS users can transparently obtain the required information on the basis of mutual understanding. According to the specifications promulgated by OGC, the software that provides data sources can be called Data Servers, and the software that uses data can be called Data Clients. The process of data clients using certain data is to send data requests. The process of data server providing services, its ultimate goal is to enable data clients to read the spatial data provided by any data server. However, the interoperability mode has flaws in practical applications. When a software accesses the data of other software, it must have the host software in the data format to be accessed at the same time, and both of them run at the same time to complete the data interoperability process. This will inevitably increase the user's burden.

Direct data access is to use the method of spatial data engine in a GIS software to realize direct access, storage and spatial analysis of other software data formats. Direct data access not only avoids cumbersome data conversion, but also does not require the user to own the host software of the data format, let alone run the software. However, for each data format to be directly accessed, the client software must write its read-write driver, so direct data access must fully understand the data format of the host software. If the data format of the host software is not disclosed, or the data format changes, the client software will have to invest a lot of manpower and financial resources in researching the data format of the host software, which limits the scalability of the software. From the perspective of the entire GIS industry, such a model will inevitably waste a lot of manpower and material resources, and it is undoubtedly not advisable.

Contents of the invention

The technical problem to be solved by the present invention is to provide a GIS middleware configuration management method, which does not require frequent data format conversion, does not require host software to run at the same time, and can realize multi-source data without a lot of repetitive labor integration.

The technical solution adopted by the present invention to solve the problems of the technologies described above is:

A GIS middleware configuration management method, the difference is that its steps are as follows:

1) The client software creates heterogeneous data source information and sends it to the data source driver manager;

2), the data source driver manager loads the corresponding middleware interface and heterogeneous data source driver according to the heterogeneous data source information;

3), the heterogeneous data source driver in the step 2) directly accesses the heterogeneous data source, and then returns the successful information to the data source driver manager, so far the heterogeneous data source and the corresponding data source driver are connected successfully;

4) The client software sends a request action, the data source driver manager responds to the request, calls the corresponding data source driver to complete the actual processing of the data, and then returns the processing result to the client software;

5) The client software displays the result data.

According to the above scheme, the specific steps of step 2) are: the data source driver manager matches the heterogeneous data source driver according to the received heterogeneous data source information, and then the data source driver manager matches the heterogeneous data source driver according to the heterogeneous data source Information loads the corresponding middleware interface and heterogeneous data source drivers.

The specific steps of said step 4) are: the client software sends out a request action, the data source driver manager responds to the request, and the data source driver manager and the heterogeneous data source driver described in step 2) pass through step 2). The loaded corresponding middleware interface performs information interaction, and the data source driver manager returns the processing result to the client software after completing the actual processing of the data.

According to the solution above, the heterogeneous data source information includes data types and connection attributes.

According to the above solution, the connection attribute is the directory information of the three modules of management, control and configuration.

According to the above solution, the request actions issued by the client software in step 4) include browsing, updating, rebuilding topology, and spatial analysis.

According to the above scheme, the step 1) also includes the following steps: before the client software creates the data source information, first judge whether the request data is heterogeneous data; if the request data is heterogeneous data, then the client software creates The data source information is sent to the data source driver manager; otherwise, the client software processes the requested data by itself, and no longer creates heterogeneous data source information and sends it to the data source driver manager.

According to above scheme, described step 2) the establishment process of middleware interface described in comprises the following specific steps:

2.1), first, create a module group including a management module, a control module, and a configuration module. The module group is configured according to the GIS middleware module specification, and a series of interfaces are configured under each module according to the GIS middleware interface specification;

2.2), and then map the heterogeneous data sources into geographical objects operable by the system through the object instance generator, wherein the object instance generator includes a middleware management module object pool and a middleware control module object pool.

According to the above scheme, the management module is a module responsible for data source operations, and the interfaces included in the management module are: the management object pool object life cycle control interface responsible for the management object pool object generation and destruction work, responsible for the geographic server object The management object pool object interface responsible for the geographic database object life cycle control work, the geographic server object interface responsible for the interactive work of geographic server objects, and the geographic database object interface responsible for the interactive work of geographic database objects; the control module is responsible for the related operations of geographic data The control module includes the following interfaces: the control object pool object life cycle control interface responsible for controlling object pool object generation and destruction, the control object pool object interface responsible for geographic data object life cycle control, and responsible for each geographic data model The geographic data model object interface of object interaction, the geographic metadata object interface responsible for the interaction of each geographic metadata object; the configuration module is a module responsible for middleware interface callback, and the configuration module includes geographic database creation, geographic database attachment , interface callback configuration interface for geographic database logout and geographic database deletion, interface for the number of bootstrap middleware data sources, interface for bootstrap middleware data source information, interface for callback creation of data sources when configuring middleware geographic data sources, The interface is for the user to call through the data source driver manager when creating, attaching, canceling, and deleting the geographic database under the configured middleware data source.

According to the above solution, the geographic objects include simple feature classes, annotation classes, network classes, and object classes.

According to the above scheme, before step 1), the following specific steps are also included: first put the middleware-related information into the configuration file of the client; then generate the geographic data source according to the geographic data source name specification with the middleware-related information in the configuration file The name connection string is parsed on the server side, so that the client software can identify the middleware interface and data source driver corresponding to the heterogeneous data source.

According to the above solution, the middleware-related information includes the following parts: middleware name, middleware description, management module name, control module name, and configuration module name.

The beneficial effects of the present invention are: 1), apply GIS middleware configuration management method, facilitate the calling of different heterogeneous data source drivers and provide consistent data operation interface to client software, client software needn't care about specific spatial data format just can Seamlessly integrate multi-source heterogeneous data; 2), the GIS middleware configuration management method adopts the method of directly reading heterogeneous spatial data, which avoids the shortcomings of frequent data format conversion and information loss in the spatial data exchange mode; 3), GIS software developers write data source drivers to access their own data according to OGC standards, and develop and release heterogeneous data source drivers together with their own GIS data. Once the internal data format changes, the corresponding heterogeneous data source drivers will be modified. It can also be carried out synchronously, and the GIS client software using this driver can still integrate multi-source heterogeneous data without making any changes, avoiding that in the direct reading mode, each GIS software must read the corresponding data internally 4) By applying the GIS middleware configuration management method, as long as the heterogeneous data source driver is successfully written, it can be registered into the GIS middleware immediately and used by other GIS client software, making GIS Middleware is highly scalable.

GIS middleware adopts the design idea of driving, which is similar to the design idea of Windows device driver. Different devices are connected to computing, and the device manager dynamically loads the driver provided by the device vendor to control the input and output of the device. The device manager provides a unified interface to the OS, and specific devices are transparent to the OS. Similarly, GIS middleware integrates multiple data source drivers, and embeds them in client software in a registered manner. When client software requests a certain data source, GIS middleware dynamically loads the requested data source driver. GIS middleware follows the OGC standard to provide a unified interface to client software, and the specific data source is transparent to client software. Originally, the client software writes the read-write driver for the data format of the accessed host software, but the host software writes the read-write driver for its own data format, and all the realized drivers are integrated and managed by the middleware, so that different GIS software can use it Realize access to multi-source spatial data. When the structure of a certain data source changes, only its data source driver needs to be changed. In this way, frequent data format conversion is not required and a lot of repetitive labor is avoided.

GIS middleware is the conversion of heterogeneous data at the semantic level and the mapping between data models. It allows users to reconstruct data during the conversion process, so that users can extract different levels of content from the same data source according to their specific requirements, rather than inputting data in a single format. Different software uses different modeling methods to represent the real world. For example, in MapGIS, closed polygons are used to represent elements such as houses and ponds, and the description information of houses and ponds, such as the number of floors and areas of houses, is stored as attribute data. , while in CAD, polylines are used to represent elements such as houses and ponds, and the attribute data is in the form of hierarchical annotation. GIS middleware combines semantic mapping and spatial operations to realize the reconstruction of spatial data and attribute data, and avoid information loss caused by different semantics of elements.

Description of drawings

Fig. 1 is a schematic flow chart of a GIS middleware configuration management method;

Figure 2 is a schematic diagram of the GIS middleware module framework;

Fig. 3 is a schematic diagram of a module framework of a data source driver manager;

Figure 4 is a schematic diagram of the use flow of GIS middleware.

specific implementation plan

The embodiments of the present invention will be further described below in conjunction with the accompanying drawings.

Fig. 1 is a schematic flow chart of a GIS middleware configuration management method, as shown in Fig. 1, a GIS middleware configuration management method, its steps are as follows:

1), the client software creates heterogeneous data source information and transmits it to the data source driver manager; for example

2), the data source driver manager loads the corresponding middleware interface and the heterogeneous data source driver according to the heterogeneous data source information; for example, if the heterogeneous data source is the Shapefile file data of ArcGIS, then the heterogeneous data source object Send to Shapefile driver;

3), the heterogeneous data source driver in the step 2) directly accesses the heterogeneous data source, and then returns the successful information to the data source driver manager, so far the heterogeneous data source and the corresponding data source driver are connected successfully;

4) The client software sends a request action, the data source driver manager responds to the request, calls the corresponding data source driver to complete the actual processing of the data, and then returns the processing result to the client software;

5) The client software displays the result data.

At this point, an information interaction has been completed. If the client software still needs to access the data source, repeat steps 2)-5). If access to the data source is no longer required, the user can also manually uninstall the data source driver. The specific data source type is transparent to the GIS client software. The GIS client software does not need to know the specific conversion steps of the data. It only needs to judge whether it is a heterogeneous data source, and if so, call the middleware interface; otherwise, access the data according to normal steps.

According to the above embodiment, the specific steps of step 2) are: the data source driver manager matches the heterogeneous data source driver according to the received heterogeneous data source information, and then the data source driver manager matches the heterogeneous data source driver according to the heterogeneous data Source information loads the corresponding middleware interface and heterogeneous data source drivers.

According to the above embodiment, the specific steps of step 4) are: the client software sends a request action, the data source driver manager responds to the request, and the data source driver manager and the heterogeneous data source driver described in step 2) Information interaction is performed through the corresponding middleware interface loaded in step 2), and the data source driver manager returns the processing result to the client software after completing the actual processing of the data.

According to the above embodiments, the heterogeneous data source information includes data types and connection attributes.

According to the above embodiment, the connection attribute is the directory information of the three modules of management, control and configuration.

According to the above embodiment, the request actions issued by the client software in step 4) include browsing, updating, topology reconstruction, and spatial analysis.

According to the above embodiment, the step 1) also includes the following steps: before the client software creates the data source information, first judge whether the request data is heterogeneous data; if the request data is heterogeneous data, then the client software Create data source information and send it to the data source driver manager; otherwise, the client software processes the requested data by itself, and no longer creates heterogeneous data source information and sends it to the data source driver manager.

According to the above embodiment, the establishment process of the middleware interface described in the step 2) includes the following specific steps:

2.1), first, create a module group including a management module, a control module, and a configuration module. The module group is configured according to the GIS middleware module specification, and a series of interfaces are configured under each module according to the GIS middleware interface specification;

2.2), and then map the heterogeneous data sources into geographical objects operable by the system through the object instance generator, wherein the object instance generator includes a middleware management module object pool and a middleware control module object pool.

According to the above embodiments, the management module is a module responsible for data source operations, and the interfaces included in the management module are: the management object pool object life cycle control interface responsible for the management object pool object generation and destruction work, responsible for the geographical server The management object pool object interface responsible for the lifecycle control of objects and geodatabase objects, the geoserver object interface responsible for the interworking of geoserver objects, and the geodatabase object interface responsible for the interworking of geodatabase objects; specifically, the management module includes open The Open interface of the geographic database, the GetName interface for obtaining the name of the geographic database, the Close interface for closing the geographic database, the NewServer interface for applying for a geographic server object, the DeleteServer interface for releasing a geographic server object, and the NewGDB interface for applying for a geographic database object , the DeleteGDB interface used to release the geographic database object, ..., wherein, the NewServer interface used to apply for the geographic server object, the DeleteServer interface used to release the geographic server object, the NewGDB interface used to apply for the geographic database object, and the geographic database object used to release The DeleteGDB interface of the database object belongs to the management object pool object interface, and the life cycle control interface of the management object pool object includes the NewMngrIFactory interface and the DeleteMngrIFactory interface.

The control module is a module responsible for the related operations of geographic data, and the control module includes the following interfaces: the control object pool object life cycle control interface responsible for controlling object pool object generation and destruction work, and responsible for the life cycle control work of geographic data objects The control object pool object interface, the geographic data model object interface responsible for the interactive work of each geographic data model object, and the geographic metadata object interface responsible for the interactive work of each geographic metadata object; specifically, the control module includes the Get Interface, the SetName interface for setting the name of the dataset, the GetInfo interface for obtaining the graphic information of the geometric entity, the NewFCls interface for applying for the feature class object, the DeleteFCls interface for releasing the feature class object, the RemoveFCls interface for deleting the feature class object, ..., Among them, the NewFCls interface used to apply for a feature class object, the DeleteFCls interface used to release a feature class object, and the RemoveFCls interface used to delete a feature class object belong to the control object pool object interface, and the control object pool object lifecycle control interface includes NewXclsIFactory interface and DeleteXclsIFacory interface .

Described configuration module is the module that is responsible for middleware interface callback, and described configuration module comprises the interface callback configuration interface of geographic database creation, geographic database addition, geographic database cancellation, geographic database deletion, the interface of bootstrapping middleware data source number, automatic Give the interface of middleware data source information, and call back the interface of creating data source when configuring the middleware geographic data source. The interface is for users to pass data when creating, attaching, canceling, and deleting geographic databases under the configured middleware data source. Source driver manager call.

According to the above embodiments, the geographic objects include simple feature classes, annotation classes, network classes, and object classes.

According to the above embodiment, according to the above embodiment, before step 1), the following specific steps are also included:

Put the middleware-related information into the configuration file of the client first; then generate the geographic data source name connection string according to the geographic data source name specification according to the middleware-related information in the configuration file, and analyze it on the server side, so that the client software can identify Middleware interfaces and data source drivers corresponding to heterogeneous data sources. The middleware-related information includes the following parts: middleware name, middleware description, management module name, control module name, and configuration module name. The middleware name and middleware description can be customized by the user; the management module is responsible for the connection of the data source and the opening of the database; the control module is responsible for the related operations of simple feature classes, annotation classes, network classes, etc.; the configuration module Responsible for middleware interface callback.

Geographic data source name (GDSN) connection string specification, the first method is implemented in the form of key-value pairs, examples are as follows:

GDSN="DSN=ArcGISLocal; USER=""; PSW=""; MANAGERMODULE=esri_Manager.dll; XCLSMODULE=esriMng_XCls.dll;";

Among them: a), the keyword GDSN indicates the geographic data source name; b), the keyword USER indicates the user; c), the keyword PSW indicates the password; d), the keyword MANAGERMODULE indicates the name of the middleware management module; e), the keyword XCLSMODULE represents the middleware control module name;

Another implementation of the Geographic Data Source Name (GDSN) connection string specification:

URL (Uniform Resource Locator) Uniform Resource Locator describes the real physical location of the resource. The address consists of a series of segments. The previous segment describes the methods and parameters that need to be used to obtain the next segment. A URL specification is uniform across the data center, i.e. it uses the same basic syntax whether it is looking for a particular type of resource or describing the mechanism through which to obtain that resource.

The general format of a URL is:

scheme://host[:port][/path][? query][#fragment]

Among them, the content in [] is optional; the meaning of each item is as follows.

Scheme: communication protocol scheme

Host: Host, Domain Name System (DNS) host name or IP address of the specified server

Port: port number, integer, optional, if omitted, use the default port of the scheme, such as the default port of http is 80.

Path: path, a string separated by zero or more "/" symbols, generally used to indicate a directory or file address on the host.

Query: query, optional, used to pass parameters to dynamic webpages (such as webpages made using CGI, ISAPI, PHP/JSP/ASP/ASP.NET and other technologies), there can be multiple parameters, separated by "&" symbols , the name and value of each parameter are separated by the "=" symbol.

Fragment: information fragment, character string, used to specify the fragment in the network resource. For example, there are multiple noun explanations in a web page, and fragments can be used to directly locate a noun explanation.

The valid scheme names provided in the scheme attribute of the data center are as follows, and user-defined protocols that follow the URL specification are supported.

The following scheme protocols are provided by the data center:

File: Local File Transfer Protocol (File Protocol), mainly used to access files in the local computer, just like opening files in Windows Explorer

ftp: File Transfer Protocol FTP (File Transfer Protocol), is a protocol for two-way transmission of control files on the Internet

gopher: (RFC-1436) The Internet Gopher Protocol (The Internet Gopher Protocol), is a protocol for obtaining data from remote servers before the development of the Internet.

http: Hypertext Transfer Protocol HTTP (Hypertext Transfer Protocol), used to transmit WWW data

https: Secure Hypertext Transfer Protocol HTTPS (Secure Hypertext Transfer Protocol)

mailto: Email protocol (Mailto Protocol), the resource is an email address, accessed through SMTP, through which a hyperlink to an email address can be created.

Emails can be sent on the Internet via this link.

News: Access this resource through NNTP.

gdbp: Geo-Database Protocol GDBP (Geo-Database Protocol), which realizes the positioning of geodatabase resources on the local geodatabase server.

gdbpns: Geodatabase domain name resolution service protocol (Domain Name System), to achieve access to local or remote geographic database servers.

ImageBandDrv: Raster image data protocol, which realizes the positioning of raster image data resources on the local geographic database server.

Dbms: Database protocol, realizes access to local or remote databases, supports three data formats of Access, SQL, and Oracle.

Figure 2 is a schematic diagram of the GIS middleware module framework. As shown in Figure 2, according to the design idea of driving, the design of general GIS middleware is a two-layer model: data source driver manager, and heterogeneous data source driver. In order to use the GIS middleware, the client software needs to provide a data interface connected with the GIS middleware. The data interface is responsible for information interaction with the GIS middleware, passing the requested data source type and actions of the client software to the GIS middleware, and returning the data results to the client software.

The data source driver manager communicates with specific client software and dispatches heterogeneous data source drivers. When the client software requests a certain type of heterogeneous data source, the data source driver manager loads the corresponding heterogeneous data source driver, and returns the data access result to the client software. It provides a unified data operation interface for all client software, and different spatial data types are transparent to client software.

Each heterogeneous data source driver is responsible for accessing its corresponding spatial data, completing the actual reading and writing of spatial data, and returning the result to the data source driver manager. Heterogeneous data source drivers are also transparent to users. The types of heterogeneous data sources include: ArcGIS data, AutoCAD data, VCT data, MapInfo_Mif data, . . .

Figure 3 is a schematic diagram of the module framework of the data source driver manager. As shown in Figure 3, the module framework diagram of the data source driver manager can be divided according to the GIS middleware module specification and the GIS middleware interface specification.

1. Divided according to the GIS middleware module specification:

1.1 Management module: realize the standard interface of management object pool, geoserver object and geodatabase object.

1.2 Control module: realize the standard interface of control object pool and geographic data object.

1.3 Configuration module: The interior has been introduced in detail.

2. According to the GIS middleware interface specification:

2.0 object pool object life cycle control interface, including management object pool object life cycle control interface, object pool object life cycle control interface, these two types of interfaces are responsible for the generation and destruction of their respective object pool objects.

2.1 Management object pool object interface: responsible for the lifecycle control of geoserver objects and geodatabase objects.

2.2 Control object pool object interface: responsible for the life cycle control of geographic data objects.

2.3 Geographic server object interface: responsible for the interactive work of geographic server objects.

2.4 Geographic database object interface: responsible for the interactive work of geographic database objects.

2.5 Geographic data model object interface: responsible for the interactive work of each geographic data model object.

1), feature class object; 2), simple feature class object; 3), annotation class object; 4), object class object;  …

2.6 Geographic metadata object interface: responsible for the interactive work of each geographic metadata object.

1) Spatial reference system object;  …

2.7 Configuration management interface: responsible for special configuration of heterogeneous data sources.

1) Bootstrap data source; 2) Create data source;  …

Figure 4 is a schematic diagram of the use flow of GIS middleware. Before using a middleware, you need to load the middleware first.

Step 1: Register GIS middleware

1) In the framework of the Catalog (enterprise manager directory tree) of MapGIS, right-click the "GDBConnection label" to pop up the right-click menu.

2) Click "Configure MapGIS Data Source" in the pop-up menu, and the "MapGIS Client Configuration Management" dialog box will appear.

3) In the "MapGIS Client Configuration Management" dialog box, click the "MapGIS Middleware" tab, and then click the "Register" button to pop up the "Register Middleware" dialog box. Among them, "Middleware Name" and "Middleware Description" can be customized by users; "Single File Feature" can be omitted for users who do not need to operate single-machine files; otherwise, fill in the suffix name of the file to be operated, if Multiple types of files are separated by semicolons; the "management module" is the Xxx_Manager module, which is responsible for the connection of data sources and the opening of the database; the control module is the Xxx_XCls module, which is responsible for simple feature classes, annotation classes, and network classes and other related operations; the configuration module is the Xxx_Config module, which is responsible for the callback of the middleware interface.

4) In the "Register Middleware" dialog box, fill in all items and click OK to return to the "MapGIS Client Configuration Management" dialog interface. If all the interfaces required by the three modules have been realized, the registration will be successful, and the interface will be represented as "√", otherwise "×". At this point, the middleware registration is complete.

Step 2: Add a data source

After the first step is completed, the middleware has been registered as a data source recognized by the MapGIS platform, and we also need to add this data source to the Catalog (enterprise manager directory tree).

1) In the "MapGIS Client Configuration Management" dialog box, click the "MAPGIS Data Source" tab, and then click the "Add" button to pop up the "Add MapGIS Data Source Type" dialog box.

2) In the "Add MapGIS Data Source Type" dialog box, select the data source type just registered, click "Next", and the "Add MapGIS Data Source Information" dialog box will pop up. What is displayed in the dialog list is a list of different data source names of the same data source type, which are generally bootstrapped by the middleware. If the middleware data source type only corresponds to one data source name, clicking "Add Data Source" will not respond, otherwise, a dialog box will pop up to add a data source. "MapGIS data source name" is the data source name displayed on the Catalog (enterprise manager directory tree) of the data source. ArcGISLocal, VctGISLocal, and MapGIS6xLocal all have only one data source, and there is no response when clicking the "Add Data Source" button; but ArcSDE can manage many types of large databases (SQL, Oracle, etc.), and it can add multiple data sources . Click the "Add Data Source" button, and the "Add ArcSDE Data Source" dialog box will pop up, and all items must be filled in.

Server name: The server name where the database managed by this data source resides. For example, if the data source manages an Oracle database, then the server name of the data source is the server name where Oracle is located, such as WEILIPING or 192.168.10.152.

Instance name: For different databases, different ArcSDE instances need to be installed, and an instance name will be generated at this time. The instance names of ORARCL and SQL are different, such as esri_sde or 5152.

Database name: Each ArcSDE data source has only one database. When ArcSDE is installed, the database name has already been generated, such as sde.

Version number: A certain version name generated during the editing process of the database being operated, generally the default version: SDE.DEFAULT.

Data source name: the user can define it by himself, it is not displayed on the Catalog (enterprise manager directory tree), but is saved by the middleware itself.

3) According to the instructions in (2), configure the items in the "Add MapGIS Data Source Information" dialog box, click "Finish", and return to the "MapGIS Client Configuration Management" interface, and you can see the newly added data source item . The newly added data source item can also be seen in the Catalog (Enterprise Manager directory tree). So far, the data source has been successfully added.

Step 3: Attaching a database (optional) To operate this type of data, the user needs to attach the folder where the data is located to the data source in the form of a database. If the database contained in this type of data source is certain, the data When the source is successfully added, the database already exists, so this type of data source does not need the third step. Under the Catalog (enterprise manager directory tree) framework, right-click the data source, then click the Additional Database menu item, and a dialog box will pop up. Among them, the "database path to be attached" must be filled in, which is the folder where this type of data is located. After filling in all items, click OK, and you can see that the database has been attached in the Catalog (enterprise manager directory tree). Each ArcSDE data source has only one and only one fixed database, so it is not possible to attach a database. ArcGISLocal, VctGISLocal, and MapGIS6xLocal all require additional databases. ArcGISLocal can attach three types of databases: shapefile, access, and coverage. Both VctGISLocal and MapGIS6xLocal can only attach one type of database.

A middleware can be uninstalled when it is no longer used.

Step 1: Delete data sources To uninstall this type of middleware, you need to delete all data sources of this type. In the "MapGIS Client Configuration Management" dialog box, under the "MapGIS Data Source" tab, select the data source to be deleted, and click the Delete button. Step 2: Unregister middleware In the "MapGIS Client Configuration Management" dialog box, under the "MapGIS Middleware" tab, select the middleware to be unregistered, and click the "Logout" button.

The interface described in the patent specification of the present invention is not necessarily just one interface, but may also be a collective name of a group of interfaces.

The embodiments of the present invention have been described above in conjunction with the accompanying drawings. Those skilled in the art can develop specific software codes in conjunction with the MapGIS secondary development help and the disclosed GIS development data. Those skilled in the art can refer to the attached rights Various changes or modifications are made within the required scope.

Claims (12)

1, a kind of GIS middleware configuring management method, it is characterized in that: its step is as follows:

1), client software is created isomeric data source information and is sent data resource drive manager to;

2), data resource drive manager loads corresponding middleware interface and heterogeneous data source driving according to described isomeric data source information;

3), described step 2) in heterogeneous data source drive directly visit heterogeneous data source, will visit successful information then and return to data resource drive manager, so far heterogeneous data source and the successful connection of heterogeneous data source driving accordingly;

4), client software sends request action, data resource drive manager responds its request, calls and returns result to client software after corresponding data source drives the actual treatment work of finishing data;

5), client software display result data.

2, GIS middleware configuring management method as claimed in claim 1, it is characterized in that: concrete steps described step 2) are: data resource drive manager is mated heterogeneous data source according to the isomeric data source information that receives and is driven, and data resource drive manager loads corresponding middleware interface and heterogeneous data source driving according to described isomeric data source information then.

3, GIS middleware configuring management method as claimed in claim 1, it is characterized in that: the concrete steps of described step 4) are: client software sends request action, data resource drive manager responds its request, data resource drive manager and step 2) described in heterogeneous data source drive between by step 2) in the corresponding middleware interface that loaded carry out information interaction, data resource drive manager is returned result to client software after finishing actual treatment work to data.

4, GIS middleware configuring management method as claimed in claim 1, it is characterized in that: described isomeric data source packet is drawn together data type and connection attribute.

5, GIS middleware configuring management method as claimed in claim 4 is characterized in that: described connection attribute is the directory information of management, control, 3 modules of configuration.

6, GIS middleware configuring management method as claimed in claim 1 is characterized in that: the request action that client software sends in the described step 4) comprises browses, upgrades, rebuilds topology, spatial analysis.

7, GIS middleware configuring management method as claimed in claim 1 is characterized in that: further comprising the steps of in the described step 1): before client software is created data source information, judge whether the described request data are isomeric data earlier; If the described request data are isomeric datas, then client software is created data source information and is sent data resource drive manager to; Otherwise client software oneself is handled request msg, no longer creates isomeric data source information and sends data resource drive manager to.

8, as claim 1 or 2 or 3 or 4 or 5 or 6 or 7 described GIS middleware configuring management methods, it is characterized in that: the process of setting up of middleware interface described step 2) comprises following concrete steps:

2.1), at first, create the module group comprise administration module, control module, configuration module, the module group is configured according to GIS middleware module standard, wherein disposes a series of interfaces according to GIS middleware interface standard again below each module;

2.2), by the object instance generator heterogeneous data source is become the exercisable geographic object of system then, wherein the object instance generator comprises middleware administration module object pool and middleware control module object pool.

9, GIS middleware configuring management method as claimed in claim 8, it is characterized in that: described administration module is a module of being responsible for data source operation, and the interface that comprises in the described administration module is: the management object pond object life cycle control interface of being in charge of the generation of object pool object and the work of destruction, be responsible for the management object pond object interface of the life cycle Control work of geolocation server object and geographical data bank object, be responsible for the geolocation server object interface of geolocation server object interaction work, be responsible for the geographical data bank object interface of geographical data bank object interaction work;

Described control module is the module of the associative operation of responsible geodata, includes in the control module with lower interface: the geodata model object interface of the controlling object pond object life cycle control interface of the object generation of responsible controlling object pond and the work of destruction, the controlling object pond object interface of being responsible for the life cycle Control work of geodata object, responsible each geographical data model object interaction work, the geographical metadata object interface of responsible each geographical metadata object interworking;

Described configuration module is a module of being responsible for middleware interface readjustment, described configuration module comprises that geographical data bank is created, geographical data bank is additional, geographical data bank is nullified, the interface of the interface of the interface readjustment configuration interface of geographical data bank deletion, bootstrapping middleware data source number, bootstrapping middleware data source information, readjustment was created the interface of data source when middleware geodata source was configured, and described interface is newly-built, additional under the middleware data source of configuration for the user, nullify, call by data resource drive manager when deleting geographical data bank.

10, GIS middleware configuring management method as claimed in claim 8, it is characterized in that: described geographic object comprises elementary factor class, annotation class, network class, object class.

11, GIS middleware configuring management method as claimed in claim 1 is characterized in that: before step 1), also comprise following concrete steps: the configuration file of earlier the middleware relevant information being put into client; Then the middleware relevant information in the configuration file is generated the geodata parent name by geodata parent name standard and connect string, and resolve, thereby make client software can discern pairing middleware interface of heterogeneous data source and data source driving at server end.

12, GIS middleware configuring management method as claimed in claim 11, it is characterized in that: described middleware relevant information comprises with the lower part: middleware names, middleware description, administration module title, control module title, configuration module title.

Images