Maximo

 View Only

 Guidance Needed: Using Automation Script with CRON for Asset Integration (Checkpoint + Logging Issues)

IBM App Upload's profile image
IBM App Upload posted 07/25/25 01:48 AM

Hi everyone,

I'm currently working on a Maximo integration where we fetch asset data from an external system and create or update assets in Maximo. The process needs to run at regular intervals, and we also need to maintain a checkpoint to track what data has already been processed.

We initially considered using MIF, but due to a few constraints—like the external system using OAuth and complexity in mapping the API response to Maximo’s Asset object—we decided to go with a fully script-based approach.

Here's what we have so far:

  • An automation script that handles fetching, mapping, and asset creation/updating.

  • A CRON task triggers this script periodically.

This setup works well functionally, but we’re facing two key challenges:

  1. Checkpoint Storage – We need to store the page number (used for pagination) as a checkpoint between script runs. What’s the recommended way to persist such a value in Maximo?

  2. Logging – When the script runs via CRON, we can see the run status, but not the logs or debug output from the script itself. During test runs, the logs are visible. Is there a standard way to access logs or capture output from CRON-executed automation scripts?

Any guidance or best practices would be greatly appreciated. Thanks in advance!

Jas Sidhu's profile image
Jas Sidhu

Is the page number going to be consistent between all runs or is this changing?

If it's consistent, the two recommended approaches is either creating a system property and using the following to access it from the script:

maximo = MXServer.getMXServer()
maximo.getProperty("PROPNAME")

The second method could be to add it to the cron task instances parameters under SCRIPTARG. If you are already using SCRIPTARG, consider appending multiple arguments and breaking them up with |
I.E: ARG1 | ARG2 |  ARG3

As for logging, if you use service.log throughout your script, it should be shown in the logs when the script runs, depending on the log level set.