Cycle

Admin Console connects to OIPA through JMX connection and issues commands to the CycleClient. The Admin Console can issue a Start command to begin a cycle step and a Stop command to end the cycle step and each of the threads that are executing.

The Cycle and Activity results are published to a JMX connection, which the Admin Console listener converts these results to persisted data. Then, the Admin Console displays this persisted data to enable the users to monitor the high level details of cycle progress in real time or a near real time.

Through the Admin Console, a user can:

• Start and Stop cycle.
• Monitor cycle and activity processes in different views, in both textual and graphical formats with past and present information.
• Monitor cycle progress in terms of percentage of completed work.
• View static data that aggregates information from the database.
• View history of cycle/activity metric data.
• Drill down through information to activity level.

Note: The Cycle feature can be enabled in OIPA using the jmx.notification.entities=cycle,activity,activityprofiling system property and value. As specified, the value of the property can be a comma delimited list of the entity data to be persisted.