Maximo Spatial Database Federation

Originally posted on the developerWorks blog.

Maximo Spatial Database Federation

Author: Rodrigo Dombrowski, Maximo Product Designer & Architect
This article describes the Maximo Spatial architecture that integrates the IBM Maximo Asset Management database with a GIS geodatabase.

All information below is valid for Maximo Spatial 7.5 version.

Maximo Spatial integrates with the GIS database using a concept called database federation, often also called database links.

Database Federation provides the following benefits:

  • No data replication needed as GIS data can be exposed and displayed on Maximo forms
  • Distributed database transactions to ensure consistency
  • Higher performance for batch read and creation of GIS records and Maximo records
  • All Maximo framework functionality and security available when displaying and editing GIS data
  • Multiple geo databases support

Documentation about how to configure Maximo Spatial to integrate with feature class tables is available in:

http://publib.boulder.ibm.com/infocenter/tivihelp/v49r1/index.jsp?topic=%2Fcom.ibm.spl.doc%2Ft_ctr_configuring.html

Documentation about how to expose GIS data to Maximo forms is available in:

http://publib.boulder.ibm.com/infocenter/tivihelp/v49r1/index.jsp?topic=%2Fcom.ibm.spl.doc%2Fconfigure%2Ft_ctr_customize_spatial_apps.html

The Maximo Spatial database configuration is done independently for each feature class that the client want to integrate with Maximo. This allows supporting multiple geodatabases and feature classes in any database schema. For GIS data insert and updates Maximo Spatial requires that both databases be from the same vendor. Oracle+Oracle, or DB2+DB2, or SQLServer+SQLServer.

Configuration Overview

Configuration Overview

In some cases it is not possible to have both Maximo and GIS database from the same vendor or it is not possible to configure database links.
For these cases currently there are the following options:

Option 1 – Read only mode – No database federation (database link)

  • Same configuration process, including Database Configuration steps, but without database link
  • It makes Maximo Spatial only read-only mode for GIS data
  • Map toolbar tools like selection, query by attributes and update GIS list stays working
  • No GIS record link or cron task will be available
  • No GIS geometry creation and editing from Maximo

Option 1

Option 1

Option 2 – No federation, read/write GIS data moved to local Maximo database

Example: Maximo running on DB2 and GIS data on Oracle database

  • Full Maximo Spatial functionality for the GIS data that is moved to Maximo database
  • No federation required when GIS is on the same Maximo database instance
  • GIS data that can be read only to Spatial can stay on Oracle
  • May require additional ArcSDE license
Option 2

Option 2