Managing global aggregates

An administrator can intervene to manage global aggregate jobs and can fine-tune how global aggregates are run.

About this task

In most situations, when a global aggregate is running you do not need to intervene. For example, if you upgrade the version of a solution, your global event aggregations continue to run. Similarly, if you have a partial outage of your system, global aggregates restart when the system is restored to ensure continuity of the calculations.

However, in some situations you might want to override or fine-tune system behavior, and you can do so by running scripts and modifying properties.

Procedure

To override the schedule of a global aggregate job, force the recalculation of a global aggregate, start or stop a job, or obtain information about a job or the queue of jobs, run the jobManager script or use the JobManagerMXBean interface. The jobManager script outputs a plain text file.
For example, the following Java™ code uses an MBean call to start a global aggregate job whose variable name is defined as HighScoringCustomers:
```
public void callMBean() throws Exception
{
MBeanServerConnection connection = getRemoteConnection();
ObjectName globalRuntimeObjectName = new ObjectName("com.ibm.ia:type=JobManager");
JobManagerMXBean bean = JMX.newMXBeanProxy(connection, globalRuntimeObjectName, JobManagerMXBean.class);

bean.submitJob("defvarHighScoringCustomers", "FastTrackSolution", "Submitting scoring customers job.", null);
} 
```

To fine-tune global aggregate calculations and performance, configure the global aggregate properties by using the propertyManager script or the solutionManager setproperty command.

You can configure the following properties for global event aggregates:

Table 1. Tuning properties for global event aggregates
Tuning goal	Property
Balance performance and data loss if an outage occurs.	eventAggregateAggregationEngineCheckpointFrequency
Improve the accuracy of global event aggregations after an outage.	eventAggregateValueSaveInterval, eventAggregateValueSaverThreadPoolSize, and saveEventAggregateEngineStateByTimer
Capture debug information.	debugEventAggregates
Specify the number of threads to broadcast partial results.	eventAggregatePartialResultsBroadcasterThreadPoolSize

You can configure the performance of global entity aggregates:

Table 2. Tuning properties for global entity aggregates
Tuning goal	Property
Restrict the length of time that batch jobs take.	defaultJobTimeout
Capture debug information.	debugEntityAggregates
Set the life span of job histories.	jobHistoryTTL