JBoss.orgCommunity Documentation

Chapter 7. BlackTie Administration

7.1. BlackTie Administration Functions
7.1.1. The following operations all perform functionality at the domain level
7.1.2. The following operations perform functionality at the server level
7.1.3. Viewing Transaction Statistics
7.2. BlackTieAdminService XATMI Service
7.3. BlacktieAdminService JMX Bean
7.4. AtmiBrokerAdmin XATMI Service
7.5. Monitoring and management of blacktie servers by blacktie-rhq-plugin
7.5.1. Install blacktie-rhq-plugin
7.5.2. How to manage a blacktie server
7.5.3. How to monitor a blacktie server
7.6. BlackTie Command Line Administration
7.6.1. Introduction
7.6.2. btadmin
7.6.3. generate_server
7.6.4. generate_client

The Section 7.1, “BlackTie Administration Functions” are exposed through a both a JMX MBean and a Java XATMI service deployed into JBoss AS, configured the same btconfig.xml of the domain it is administering

Each BlackTie server exposes the same administration service, registered during AtmiBrokerServer startup

  1. Section 7.4, “AtmiBrokerAdmin XATMI Service”

Queue administration for the AtmiBrokerAdmin service is performed through a separate Java XATMI service

  1. stompconnectservice: BlacktieStompAdministrationService

Administration is facilitated graphically from a JBoss AS RHQ administration console plugin

  1. Section 7.5, “Monitoring and management of blacktie servers by blacktie-rhq-plugin ”


Figure 7.1. Administration

In a typical BlackTie installation the transaction service will be running in the JBoss Application server where you installed the stomp connect service. In such a setup basic transaction management information is exposed by the native transaction service running in the AS. For example to enable statistics open the JBossTS property file located at:

and set the enableStatistics property to YES:

<!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
<span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">property</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">name</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;com.arjuna.ats.arjuna.coordinator.enableStatistics&quot;</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">value</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;YES&quot;</span><span class="xml_tag_symbols">/&gt;</span><span class="xml_plain"></span><br />

The statistics are then available via any standard JMX browser or programatically via JMX. The object name of the MBean that maintains the stats is:

<!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
<span class="xml_plain">jboss.management.local:J2EEServer=Local,j2eeType=JTAResource,name=TransactionManager</span><br />

If you are using the web based JBossAS jmx console then look for the name

<!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
<span class="xml_plain">J2EEServer=Local,j2eeType=JTAResource,name=TransactionManager</span><br />

in the section called jboss.management.local

In the jmx console some extra transaction information is also exposed as a service with the following name:

<!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
<span class="xml_plain">service=TransactionManager</span><br />

The statistics are global to the application server. We would like to provide similar information on a per BlackTie domain and per BlackTie server basis in a future release.

Defined in stompconnectservice:BlacktieAdminServiceXATMI

Contains the same functionality as the JMX bean

The XATMI service is accessed by:

Defined in the module: stompconnectservice:BlacktieAdminServiceMBean

The JMX bean is accessed by either:

The BlackTie administration services marshal calls to this raw administration service deployed in each server

The service is bound with a well known name:

Each server exposes the administration service for the duration of its lifespan

Clients (typically the BlackTie administration services) are able to invoke a standard XATMI service with a structured command

Command structure is (note the trailing comma's):