The web blog http://www.learnsccd.com strives to be a comprehensive guide to SCCD, TADDM, SERVICE NOW and MAXIMO tools. This is a personal site maintained solely by me. I intend to update it regularly.For live updates please follow us on.

Archiving of Message Tracking data in Maximo 7.6

Archiving of Message Tracking data in Maximo 7.6

NOTE:  This utility is for version Maximo 7.6.0.0 (or higher)

Starting in release 7.6, the integration messages that are configured to be saved as part of the Message Tracking functionality will be persisted in the Maximo database, no longer on the file system.  With this change, a utility is being provided that gives you the option to archive the message tracking file data (and related metadata) from the Maximo database.

The MsgTrackingArchive.zip files includes
  • a script file: track_archive.dbc (under folder ..\tools\maximo\en\mif)
  • a CRON Task class file: CleanMsgTrackingCronTask.class
We should unzip this file into your Maximo build file structure and then rebuild and redeploy the Maximo EAR file.
Run the script file:  by setting your directory to ....\tools\maximo\internal and running this command
                        runscriptfile -cmif -ftrack_archive
                        A resulting log file will be saved in the ...tools\maximo\log  folder

Once that is done, you can configure the CRON task instance to copy the message data to the file system and also have the message purged from the Maximo database.  Additionally you can purge the corresponding message tracking data (associated with the message).

When you create an instance of the CRON task, the following parameters are available to configure:
  • EXTERNALSYSTEM
  • SERVICENAME
  • NUMBEROFDAYS
  • FILEDIR
  • MOVETOFILE
  • PURGEMSG
  • USEDESTOUTBOUND

These parameters drive the filtering of the data to be processed:

EXTERNALSYSTEM - Configure this parameter with a valid external system name to limit the processing message tracking records to those tied to the external system specified.
SERVICENAME - Configure this parameter with an enterprise service or publish channel name to limit the processing message tracking records to those tied to the service or channel specified.
NUMBEROFDAYS - Configure this parameter with a numeric value to process records based on age.  A value of 30 would direct processing to process records that are 30 days or older.  If no value is provided processing would review all rows of data (while also considering other filtering conditions).

These parameters drive the archiving/purging of the data that meets the filtering criteria:

PURGEMSG - Configure this parameter with one of the following values
  • 0 - do not purge message data
  • 1 - purge message data (default)
  • 2 - purge message data and its related message tracking metadata.
MOVETOFILE - Configure this parameter with one of the following values
  • 0 - do not move message data to a file on the file system (default)
  • 1 -move message data to a file on the file system
FILEDIR - The file directory location message tracking files are to be written.  This location must be accessible from the server(s) where the CRON task is running.

USEDESTOUTBOUND - For files associated to publish channels (outbound messages), by default they would be created under a folder named MX (based on the value registered in the MXSYSID maxvar).  If you prefer the file to be created under a folder that is named using the external system (where the message was sent), then set this parameter to 1 (true).

We can configure multiple instances of the CRON task to perform different archiving/purging rules for different channels, services or external systems to satisfy your business requirements.  You can also choose to use one CRON instance to move message data to a file immediately while another CRON may purge that same message data 30 days later.