Introduced in Turbonomic v5.0 is the ability to add your Java Application Servers into Turbonomic by leveraging for Red Hat JBoss, the managed domain – domain controller or the standalone server. This methodology provides more information of heap, thread pool utilization, and average servlet response times - information used to drive decisions to resize heap or the thread pool, or clone to scale out horizontally.
This article describes some tips on adding a JBoss managed domain – domain controller or standalone server as a target, and terminology used.
Looking for information on Oracle WebLogic or IBM Websphere support introduced in Turbonomic 5.1? Check out: Turbo Tip: Application Control Module and adding Oracle WebLogic as a Target and Turbo Tip: Application Control Module and adding Oracle WebLogic as a Target
License key for Application Control Module or Application Edition is required and Turbonomic v5.0 or higher to see Red Hat JBoss as a target.
Overview: Red Hat JBoss
Managed Domain – domain controller
Managed Domain will be Auto-detected and requires HTML API port and user/password. Ports are obtained from xml configuration files:
JBoss Target Configuration
From within Turbonomic, Navigate to Admin --> Target Configuration --> Application Server and select JBoss to input the necessary credentials:
JBoss – Port Info
Look for the Http-interface in the management section in host.xml. Default is 9990.
Note: The interface must be made accessible from remote location: the inet-address for management interface must be set on 0.0.0.0.
The thread commodity exists only if the HTTP connector defines a thread pool. To make sure, look for the executor attribute in the HTTP connector, domain.xml:
<subsystem xmlns="urn:jboss:domain:web:1.4" …>
<connector name="http" protocol="HTTP/1.1” executor="JBossWeb…
JBoss – Naming Convention
There are three parts in the name of a discovered JBoss AS instance:
- IP address
- Controller name/STANDALONE
<?xml version='1.0' encoding='UTF-8'?>
<host name="master" …>
- Server name
<server name="server-one" …>
- Standalone installation: the host name