Basic DataSplice Architecture

This diagram shows how the various DataSplice components interact with each other:

• The DataSplice clients are capable of using any TCP network interface to communicate with the server
• The Server has the ability to integrate with multiple back end data sources simultaneously
  

Network Connectivity

Because DataSplice is an n-tiered application suite, it is important to understand how the different components connect over a network.

DataSplice Clients to the Server

The Remote Client and Administration Client needs to be able to connect to the DataSplice server over a single TCP/IP port, which is 4100 by default. Because this is the only port involved, it is very easy to setup firewalls and routing between the clients and the server.

Network security, if desired, should be provided by a VPN or similar technology that secures network traffic between two endpoints. There are several commercial products that work on Windows CE as well as desktop versions of Windows.

Note that the clients never connect directly to any databases so they need not have any client software installed, or even be able to connect to the target databases.

DataSplice Server to External Data Sources

Obviously, if the DataSplice Server is to provide access to information in a database it must be able to connect to that database. This means that the necessary client software must be installed, and the server machine must have permission to access the databases.

Depending on the installation size, the DataSplice Server can either be installed on the same machine as the database server or a separate dedicated machine.

Online/Offline Operation

DataSplice clients are capable of working in two modes:

Online/Connected to the Server

• All queries and transactions are processed by the server, providing real-time access to the backend data
• License is only consumed while actively connected to the server
  
• Network/server outages prevent users from accessing DataSplice
  

Offline/Store and Forward

• Users synchronize with the server to cache all the needed data on the device
• All modifications are stored locally and are committed during the next synchronization
  
• License is consumed until user logs out and releases it
  

Various groups can be configured to operate only in one particular mode, or allow the user to switch between them as desired.

In order to support offline functionality, a version of Microsoft SQL Server must be available so the Remote Client can persist and search through the available data.

Windows Mobile Devices - Microsoft SQL Server Mobile (version 3.0 or greater) must be installed.

Desktop Windows Versions - The simplest method is to use SQL Server Express for desktop platforms, which is freely available. However, any installation of SQL Server can be accessed if desired.

Maximo Plug-in Architecture

The following diagram demonstrates how DataSplice integrates with a Maximo application server for mobile access:

• Note that only the server communicates with Maximo, the clients do not need to directly access any of the components
  

• Data queries use a native database connection for performance reasons and are processed by the same database user

• All transactions to modify data are committed through the Maximo Business Object (MBO) layer, which ensures that user permissions, customizations, etc. are respected.