IBM Support

mxe.crontask.donotrun and mxe.crontask.dorun system properties for a clustered environment

Question & Answer


Question

When do we use the mxe.crontask.donotrun and the mxe.crontask.dorun Maximo system property?

Cause

Maximo 7.6 introduced a new system property: mxe.crontrask.dorun.

Answer

With Maximo 7.5, there is a property called mxe.crontask.donotrun. This is used in a clustered environment on the servers to help separate functionality where you DO NOT want certain cron tasks to run.

With Maximo 7.6 a new system property mxe.crontask.dorun was added. This is used in a clustered environment on the servers where you DO want certain cron tasks to run.

One thing to note is, mxe.crontask.donotrun will take precedence and overwrite any values that are assigned for mxe.crontask.dorun. So if you have mxe.crontask.donotrun = ALL, no cron tasks will run on that server, no matter what you have specified to run for mxe.crontask.dorun.

In Maximo 7.6 which property should you use? Below is a simple example of how this can be used in a clustered environment.

1. Cron JVM - you only want the JMS outbound cron task to run.

Previously in 7.5, mxe.crontask.donotrun was set to a very long value consisting all the possible cron tasks set up in your environment.

With version 7.6, you could use the mxe.crontask.dorun and specify all of the cron tasks you DO want to run in the CRON JVM. However, as this is the Cron JVM, the list would be very long.

You could simplify this and use the mxe.crontask.donotrun that already existed in 7.5. You would include all the cron tasks you don't want to run on this Cron JVM.

With version 7.6, you could simplify this and have (for example):

mxe.crontask.donotrun = JMSQSEQCONSUMER, IFACETABLECONSUMER, FLATFILECONSUMER, XMLFILECONSUMER

mxe.crontask.dorun = NULL (no value)

2. MIF JVM - you only want integration inbound related cron tasks to run.

Previously in 7.5, mxe.crontask.donotrun was set to a very long value consisting all the possible cron tasks not related to integration inbound set up in your environment.

With version 7.6, you could simplify this and have:

mxe.crontask.donotrun = NULL (no value)

mxe.crontask.dorun = JMSQSEQCONSUMER.SEQQIN, IFACETABLECONSUMER, FLATFILECONSUMER, XMLFILECONSUMER

This means, on the MIF JVM only the inbound integration cron tasks will run.



Note: If you copy and paste these task names from this document, be sure that they match up with the names of the parameters in Maximo or your properties files will not work correctly.

[{"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Business Unit":{"code":"BU005","label":"IoT"},"Component":"System Related","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6","Edition":""}]

Document Information

Modified date:
17 June 2018

UID

swg21903012