Several components need to be installed and configured properly in order for the plug-in to function correctly. The following diagram shows the schema of the DataSplice .NET integration plug-in in relation to the Maximo and database systems:

DataSplice Server

The DataSplice Server has the ability to load available plug-ins on startup to provide behavior that is not part of the default application suite.

Plug-ins are loaded from the following directories, where [DataSpliceRoot] indicates the path where DataSplice was installed (by default, this is C:\Program Files\DataSplice):

DataSplice .NET Integration Plug-in

The DataSplice .NET integration plug-in for Maximo 5.x installs a server library that provides access to .NET action plug-ins available in the DotNetModules directory, as well as the assemblies needed to connect to Maximo.

DataSplice Views

As part of the plug-in installation process, the associated DataSplice views are also installed. Although a DataSplice view can reference a database view, it is important to realize the difference between the two. DataSplice views are objects that represent a set of data in the target database and meta-data that control how the view is used in DataSplice. DataSplice views are configured in the DataSplice Administration Client and are stored on the DataSplice Server. Database views, on the other hand, are pre-compiled SQL statements that can then be queried as a simpler statement. Database views are stored and maintained on the database server.

The associated DataSplice views are included as part of the installation process. The DataSplice views are created by executing the provided database scripts. Scripts are included for both Oracle and SQL Server.

JNBridge

The DataSplice .NET integration plug-in uses a bridge component provided by JNBridge to connect the .NET events generated by the DataSplice Server to the Maximo Java API. Licensing for the JNBridge software is handled automatically through the DataSplice .NET integration plug-in installation process. Additional information about the bridge can be found at http://www.jnbridge.com.

Maximo Java API

The Maximo Java application programming interface (API) provides the interface for the bridge to efficiently communicate with the Maximo server.

Maximo 5.x Server

The Maximo server interacts with the database server to provide a structure for the data to be manipulated in a way that is productive with many CMMS tasks. The tasks fall under such categories as enterprise asset management, inventory management, and work management.

Database Server

The database server acts as a repository for all of the data in the system.