CloudTran Home

 
  
<< Back Contents  >  8.  Management and Performance Tuning Forward >>

8.2 Management bean overview

The attributes of the application are organized into separate beans, which means they will be accessible under different directory nodes. Most of the beans becomes visible when the application is started up, some of them only becomes visible if there are transactions in the system and some of them requires the application to be started with a special parameter to become visible.

Bean namePurposeWhere can be found?When becomes visible?
Application life cycleProvides life cycle information about the application, and also provides operations to control the life cycle of the coordinator.CoordinatorWhen the coordinator starts up.
CoordinatorMonitor and tune the Coordinator.CoordinatorWhen the coordinator starts up.
DatasourceMonitor and tune the path to the datasource.CoordinatorWhen the coordinator starts up or when the coordinator have to process a transaction which belongs to a still unused datasource.
Resolve transactions to cohortMonitor and tune the transaction resolving to the cohorts.CoordinatorWhen the coordinator starts up.
CohortMonitor and tune the CohortAll CohortsWhen the cohort starts up.
Coordinator crash testProvides interface to deliberately crash the Coordinator.CoordinatorIf the following attribute -Dct.crashTest=true added to the virtual machine startup parameters.
Cohort crash testProvides interface to deliberately crash the cohort.All CohortsIf the following attribute -Dct.crashTest=true added to the virtual machine startup parameters.

Copyright (c) 2008-2013 CloudTran Inc.