Platform Support
Installation
Getting Started
ESJMap API
Fixes and Enhancements in Release 2.1
Known Issues in Release 2.1
Release 2.1 supports data services executing on:
- Windows NT, 2000, XP
- Sun Solaris 8+
- Linux on Intel
connecting to any Oracle 8i or 9i databases.
ESM 2.1 comes packaged with Xmarc Enterprise Spatial ES 6. Follow the installation instructions to install it on your machine.
NOTE: ESM Release 2.1 can co-exist with an existing (earlier) ESM installation.
A summary of the ES 6 directory structure is as follows:
deploy A sub-directory designed to be published by your web-server, either directly or by copying it to a suitable location within the web-server hirerachy deploy/app The configuration files and libraries used for ESM applications and services deploy/smartmap The SmartMap Java applet used for esPublish application clients (not currently supported) deploy/resources Symbology resources made available to ES applications deploy/webfire The Fire plugins used for web-deployed Fire applications, and the JAM Java applet for its installation documentation The documentation html herarchy es Scripts for starting tools and services, plus database-specific load files es_fire Full source code of an example viewing application (ES Viewer) which uses the ES API es_jmap The ESJmap Java classes used for creating Java client applications using the ES API fire The Xmarc Fire kernel and associated support files servlet The Java servlet extensions which enable a web-server to manage and distribute Fire and database services across the web (Service Manager, Service Broker, Service Agent)
A brief summary of the system is available, and how to get up and running quickly can be found here.
Full documentation for configuring ES and installing the ES Metadata schema and the ES Tutorial are found in the ESM Online Help.
Note: If you are upgrading from a version of ESM prior to 2.0, it is recommended that you install the new ESM schema under a different user name (e.g. esm2), or alternatively, you may drop your existing esm user and re-install the new schema from scratch.
ESM Release 2.1 will automatically upgrade your existing schema from ESM 2.0.
In order to build Java applications and/or applets with Xmarc's ESJMap API, you will need to install the Java 2 Technology Development Kit which is available from various vendors. For the ESJMap API we require Java SDK 1.3.1 or later.
Please note, the ESJMap API utilizes Java SDK features such as the Swing toolkit. As a consequence, applets will not run in browsers that do not have a compliant JVM (such as Microsoft's Internet Explorer using Microsoft's JVM). However this situation can be remedied by using the new Java Plugin technology. For further information refer to Java Plug-in HTML Converter and Sun's Java Plug-in Product.
Existing ESJMap programmers migrating from ES5 will need to change their esjmap source to accommodate package name changes in ES6. All package names are now lower case, and the 'formida' package prefix is now 'xmarc'. Examples of changes are:
COM.formida.FJClass ==> com.xmarc.fjclass
COM.Xmarc.WIISE ==> com.xmarc.wiiseThere are also some new packages, notably com.xmarc.shape containing some entity classes formerly resident in COM.formida.FJClass. Consult the javadoc for details. We apologise for any inconvenience this may cause, but the changes were necessary for platform independence reasons.
Further information about how to get started with the ESJMap API can be found here.
ESM Release 2.1 contains the following fixes and enhancements:
General - The splash screen control is centralized in the ES-Lib application. The application configuration file (eslib.fsc) now has a variable, ~eslib.enable_splash, which can be set to disable splash screens in ALL ES applications. The default value is false, no splash.
ES-Fire
- goOnline() and goOffline() methods added to esMetaDB class, allowing the user to dynamically switch data source connections on and off.
- Switching to a location with "location-specific data" now cleans out any existing data and loads new data correctly.
- The is_browseable / is_selectable settings defined in the ES-Admin tool now have an effect on browse behavior. They were previously ignored.
- The view history tools (next, previous, first, last) are linked into the window's view history. They will ghost when not available.
The overview window pan tool has been improved to lock on to the overview window box from within the box (it used to only lock at the box edges). The look and feel now more closely mimics the pan tool. The overview window box now displays in blue and uses the same red/green color feedback as the pan tool to indicate whether any action will be taken, based on a distance tolerance from the starting position.
ES-Admin - Modified the Collection configuration screen to better support browseable / selectable settings. A layer must be browseable before it can be selectable.
ES-Publish/Smartmap - Support for this facility is not included in this release.
The ES Admin tool is currently supported on Windows platforms only.
Uninstallation process of ESM. The problem affects customers who are
installing over an existing installation and which share the
/deploy directory (or any other directory) through their web server
(which is the recommended method), i.e. have an alias to
/deploy in their http configuration file for their web server. A
workaround is to stop the web server prior to uninstalling/installation. This
frees the file locks and allows normal file deletion to take place.
Note: If the files in the installation directories are in use by any
other program, e.g. a running service, etc., the installer will also NOT be
able to delete them. For this reason it is recommended that you shut down all
running applications, as well as stop the web server, prior to installation.
The Oracle error message will look like this:
ORA-29902: error in executing ODCIIndexStart() routine
It may be proceeded by "(fx8i)", which is the name of the Xmarc application which trapped the error.
To solve this problem, you need to include a line in your ESJMap application which reads:
ESSystem.getInstance().setProjection("Longitude / Latitude (WGS 84)");
Where "Longitude / Latitude (WGS 84)" is a valid Oracle coordinate system, matching the coordinate system used for storing your data. This client coordinate system is used as the coordinate system for the view extents shape. This line should be placed early in the initialization of your application.
The coordinate string can be retrieved from Oracle's MD_SYS.CS_SRS table using the SRID from the USER_SDO_GEOM_METADATA table using SQL. For example, to retrieve the coordinate string for SRID 8307, you would use:
SELECT cs_name FROM mdsys.cs_srs WHERE srid = 8307;