ActiveSpaces® Transactions supports JMX access to all administrative commands. It also supports JMX notifications for all log events.

When a JVM is started in ActiveSpaces® Transactions a JMX server is automatically started. The address of the JMX server can be found in the JVM details screen in the JMX Service Address and JMX Service URL fields. See Figure 1.12, “JMX address”.

Figure 1.12. JMX address

Valid ActiveSpaces® Transactions node credentials must be specified in the JMX console login panel to access the ActiveSpaces® Transactions JVM. The user name and password specified must already be defined for the node.

Figure 1.13. JMX console log in

ActiveSpaces® Transactions exposes MBeans for:

All of the ActiveSpaces® Transactions Mbeans can be found in the com.kabira.platform.management name space.

Figure 1.14. ActiveSpaces® Transactions MBeans

Configuration MBean

The JMX configuration MBean supports execution of all ActiveSpaces® Transactions configuration commands. Figure 1.15, “Configuration MBean” shows an example of displaying node configuration loaded into a ActiveSpaces® Transactions node.

Figure 1.15. Configuration MBean

Event MBean

The JMX event MBean supports:

• dynamically adding and removing topics for which the MBean will receive events

• receiving event notifications

Figure 1.16, “Events MBean” shows event notifications being displayed.

Figure 1.16. Events MBean

Management MBean

The JMX management MBean supports execution of any ActiveSpaces® Transactions or application defined management command. Figure 1.17, “Management MBean” shows an example of displaying all JVMs running on a ActiveSpaces® Transactions node.

Figure 1.17. Management MBean