The Maximo Manage services ReorderCronTask and PMWoGenCronTask can be process- intensive. To segregate the workload, where are the relevant properties set?

Question

Options

• Aserver bundle
• BMAXVARS table
• CSystem Properties application
• Dmaximo.properties file

• A
  75% (18)
• B
  4% (1)
• C
  17% (4)
• D
  4% (1)

Explanation

In Maximo Manage (MAS), server bundles define logical groupings of server instances, and CronTask assignments are configured at the bundle level - meaning you specify which bundle runs ReorderCronTask and PMWoGenCronTask, routing their heavy workloads to dedicated servers rather than the general-purpose tier. This is the correct mechanism for workload segregation in a multi-server Maximo deployment.

Why the distractors are wrong:

• B (MAXVARS table): Stores legacy system variables but has no role in CronTask-to-server routing.
• C (System Properties application): Manages runtime configuration like email or LDAP settings - not server bundle assignments.
• D (maximo.properties file): A low-level server config file for JVM and DB connection settings; CronTask segregation is not handled there.

Memory tip: Think of server bundles as job queues for specific servers - just as you'd assign a heavy manufacturing job to a dedicated machine on a factory floor, you assign CPU-heavy CronTasks to a dedicated bundle so they don't compete with user-facing transactions.

No community discussion yet for this question.