1
Introduction to MapViewer 1-1
1
Introduction to MapViewer
Oracle Mapviewer MapViewer is a programmable tool for rendering maps using spatial data managed by Oracle Spatial or Oracle Locator also referred to as Locator.
MapViewer provides tools that hide the complexity of spatial data queries and cartographic rendering, while providing customizable options for more advanced
users. These tools can be deployed in a platform-independent manner and are designed to integrate with map-rendering applications.
This chapter contains the following major sections:
■
Section 1.1, Overview of MapViewer
■
Section 1.2, Getting Started with MapViewer
■
Section 1.3, Prerequisite Software for MapViewer
■
Section 1.4, Installing and Deploying MapViewer
■
Section 1.5, Administering MapViewer
■
Section 1.6, Oracle Real Application Clusters and MapViewer
■
Section 1.7, High Availability and MapViewer for advanced users
■
Section 1.8, Secure Map Rendering
■
Section 1.9, MapViewer Demos and Tutorials
1.1 Overview of MapViewer
MapViewer is shipped as part of Oracle Fusion Middleware. Its main deliverable is a J2EE application that can be deployed to a J2EE container, such as that for Oracle
Fusion Middleware. MapViewer includes the following main components:
■
A core rendering engine Java library named SDOVIS that performs cartographic rendering. A servlet is provided to expose the rendering functions to Web
applications.
■
A suite of application programming interfaces APIs that allow programmable access to MapViewer features. These APIs include XML, Java, PLSQL, and an
AJAX-based JavaScript API.
■
A graphical Map builder tool that enables you to create map symbols, define spatial data rendering rules, and create and edit MapViewer objects.
■
Oracle Map, which includes map cache and FOI feature of interest servers that facilitate the development of interactive geospatial Web applications.
The core rendering engine connects to the Oracle database through Java Database Connectivity JDBC. It also reads the map metadata such as map definitions, styling
1-2 Oracle Fusion Middleware Users Guide for Oracle MapViewer
rules, and symbologies created through the Map Builder tool from the database, and applies the metadata to the retrieved spatial data during rendering operations.
The XML API provides application developers with a versatile interface for submitting a map request to MapViewer and retrieving the map response. The JavaBean-based
API and the PLSQL API provide access to MapViewers rendering capabilities. The JavaScript API enables you to create highly interactive web applications that use the
Oracle Maps feature of MapViewer.
The Map Builder tool simplifies the process of creating and managing map, theme, and symbology metadata in a spatial database. For information about this tool, see
Chapter 9 .
Oracle Maps, built on core MapViewer features, uses a map tile server that caches map image tiles, and a feature of interest FOI server that streams live data out of a
database to be displayed as interactive features on a map. You can use the AJAX-based JavaScript API with Oracle Maps to provide sophisticated mapping solutions. Oracle
Maps also allows for advanced customization and querying capabilities.
The primary benefit of MapViewer is its integration with Oracle Spatial, Oracle Locator, and Oracle Fusion Middleware. MapViewer supports two-dimensional vector
geometries stored in Oracle Spatial, as well as GeoRaster data and data in the Oracle Spatial topology and network data models. Oracle MapViewer is also an Open
Geospatial Consortium OGC-compliant Web Map Service WMS server.
1.1.1 Basic Flow of Action with MapViewer
With MapViewer, the basic flow of action follows a two-step requestresponse model, whether the client requests a map or some MapViewer administrative action.
For a map request:
1.
The client requests a map, passing in the map name, data source, center location, map size, and, optionally, other data to be plotted on top of a map.
2.
The server returns the map image or a URL for the image and the minimum bounding rectangle MBR of the map, and the status of the request.
For a MapViewer administrative request:
1.
The client requests a MapViewer administrative action, passing in the specific type of request and appropriate input values.
2.
The server returns the status of the request and the requested information. Figure 1–1
shows the basic flow of action with MapViewer.
Introduction to MapViewer 1-3
Figure 1–1 Basic Flow of Action with MapViewer
1.1.2 MapViewer Architecture
Figure 1–2 illustrates the architecture of MapViewer.
Figure 1–2 MapViewer Architecture
As shown in Figure 1–2
:
■
MapViewer is part of the Oracle Fusion Middleware middle tier.
■
MapViewer includes a rendering engine.
■
MapViewer can communicate with a client Web browser or application using the HTTP protocol.
■
MapViewer performs spatial data access reading and writing Oracle Spatial and Oracle Locator data through JDBC calls to the database.
■
The database includes Oracle Spatial or Oracle Locator, as well as mapping metadata.
Oracle Spatial
MapViewer Mapping Client
Map Request:
- Map Name - Data Source
- Center and Size
or Administrative Request:
- Type of Request - Input Values
Map Response:
- Map Image - MBR of the Map
- Status
or Administrative Response:
- Status - Output Values
MapViewer
Client
Middle Tier Oracle
Application Server
Database JDBC
HTTP
rendering engine Web Browser or Application
Spatial or
Locator Mapping
Metadata
1-4 Oracle Fusion Middleware Users Guide for Oracle MapViewer
1.2 Getting Started with MapViewer
