Synchronization settings - j5 - 28.0 - Administration & Configuration - Hexagon PPM

j5 Maximo Integration Configuration

English (United States)
Search by Category
Administration & Configuration
j5 Version

The j5 interface has two different mechanisms for synchronization with Maximo.

The first is a full synchronization in which all locations, assets, service requests, and work orders are fetched from Maximo. The full data set is processed in j5 to identify entries that should be inserted, updated, or deleted and the changes are applied to the j5 database. Assets are remapped based on the changes received from Maximo. This is currently an intensive, long-running task and is started manually from the Maximo console. j5 controls the memory usage and load on the Maximo server by querying and processing Maximo data in batches. Number of records to fetch in a batch for full sync sets the size of each batch that j5 processes.

If the Number of records to fetch in a batch for full sync setting is set too large, the individual SOAP requests will time out and the sync will fail. A SOAP time out is dependent on the number of records it is retrieving and also the performance of the Maximo instance. If the setting is too small, the initial sync might take longer than expected to run. You might need to tweak this value, but j5 recommends an initial value of 100 (which is the default).

The second mechanism is an incremental synchronization with Maximo. j5 identifies the last data it received from Maximo and queries Maximo for data that has changed since the last successful synchronization. Date format for SOAP requests is used when querying Maximo for the incremental changes. For example, if the last successful synchronization was at 2020-01-01 08:45, and the changed date field in Maximo is set to "CHANGEDATE", j5 looks for "CHANGEDATE > 2020-01-01 08:45".

It is not possible for the incremental synchronization to identify entries that are deleted in Maximo. This is only handled by the full synchronization which is necessary in the unlikely occurrence that Maximo data is removed. When an asset is no longer needed in Maximo, the common practice is to mark the equipment as DISABLED instead of removing it from the system. In this case, the equipment is marked as disabled in the j5 Asset Register through the incremental synchronization.

The full synchronization is typically used as the initial integration step with Maximo. The incremental synchronization runs at the configured schedule (if automatic synchronization is enabled) and is sufficient to retrieve all the changes in Maximo going forward. If for some reason the incremental synchronization does not run for a long time and the SOAP request times out due to there being too many records to fetch, you might need to manually run the full synchronization again to allow the incremental synchronization to succeed.