9.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 name	Purpose	Where can be found?	When becomes visible?
Application life cycle	Provides life cycle information about the application, and also provides operations to control the life cycle of the coordinator.	Coordinator	When the coordinator starts up.
Coordinator	Monitor and tune the Coordinator.	Coordinator	When the coordinator starts up.
Datasource	Monitor and tune the path to the datasource.	Coordinator	When the coordinator starts up or when the coordinator have to process a transaction which belongs to a still unused datasource.
Resolve transactions to cohort	Monitor and tune the transaction resolving to the cohorts.	Coordinator	When the coordinator starts up.
Cohort	Monitor and tune the Cohort	All Cohorts	When the cohort starts up.
Coordinator crash test	Provides interface to deliberately crash the Coordinator.	Coordinator	If the following attribute -Dct.crashTest=true added to the virtual machine startup parameters.
Cohort crash test	Provides interface to deliberately crash the cohort.	All Cohorts	If the following attribute -Dct.crashTest=true added to the virtual machine startup parameters.