Several components work together to allow the functionality of the DataSplice MAXIMO® integration plug-in to take place. The following diagram shows the schema of the DataSplice MAXIMO® integration plug-in in relation to the various other required components in a typical system. Please keep in mind that this layout is examined for educational purposes and may vary considerably depending on the actual environment. For example, the DataSplice Server, database server, and MAXIMO® server might actually all be located on the same physical server.

DataSplice Server

The DataSplice Server manages the remotely-connected clients and handles the communication between those connections. The DataSplice Server also has the ability to load available plug-ins on startup to provide behavior that is not part of the default application suite.

DataSplice MAXIMO® Integration Plug-in

The DataSplice MAXIMO® integration plug-in utilizes JNBridge® to communicate between .NET events in the DataSplice Server and remote method invocation (RMI) Java calls to the MAXIMO® Java API.

JNBridge®

The DataSplice MAXIMO® 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 plug-in installation process. Additional information about the bridge can be found on the JNBridge® website.

DataSplice Views

As part of the plug-in installation process, the associated DataSplice views are also installed. DataSplice views for MAXIMO® integration are included for Oracle and SQL Server platforms. 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.

MAXIMO® 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 order management.

MAXIMO® Java API

The MAXIMO® Java application programming interface (API) receives RMI calls and in turn uses MAXIMO® business objects (MBOs) to interact with the MAXIMO® server.

Database Server

The database server acts as a repository for all of the data in the system. This may be on a separate physical server or the same one as the MAXIMO® server.