JBoss

Turbonomic supports connecting to JBoss targets running in the Managed Domain or Standalone operation modes.

  • Managed Domain

    A collection of JBoss servers in a domain, with a single Domain Controller process acting as the central management control point. In this case, the VM that hosts the Domain Controller will be the target. You configure a Domain Controller via the domain-controller entry in the host.xml file on the JBoss machine.

  • Standalone

    A single JBoss server. The VM that hosts the server is the target.

Prerequisites

  • JBoss Application Server 6.3+

  • The target VM is properly configured as Domain Controller or standalone, depending on the operation mode

  • Hosting VM is discovered through a hypervisor target

    Turbonomic discovers JBoss servers that are running on VMs, or on containers that are deployed on VMs. To set the target for a JBoss server, you must have first discovered the hosting VM through a hypervisor target.

    For information about hypervisor targets, see Hypervisor Targets.

  • JBoss server must define a thread pool in its configuration files

    Turbonomic monitors the Threads resource in application servers to track utilization of thread pool capacity. To monitor threads in JBoss, each JBoss server must define a thread pool in its configuration files. For instructions on specifying thread pools, see the JBoss documentation.

  • JBoss supports Role-Based Access Control (RBAC) as a way to specify a set of permissions for user accounts

    JBoss disables RBAC by default. If you enable RBAC, Turbonomic requires the Monitor role for the target JBoss account in order to discover JBoss servers.

Adding a JBoss target

You can add an individual JBoss server as a target, or you can add all matching targets within a given scope.

  1. Click Settings > Target Configuration.

  2. Click New Target > Applications and Databases.

  3. Select JBoss.

  4. Configure the following settings:

    • Target Name

      Specify a name that uniquely identifies this connection.

      This name is for display purposes only and does not need to match any name in JBoss.

    • Username

      Specify the username of the account Turbonomic uses to connect to the target.

      Username should not include the Active Directory domain.

    • Password

      Specify the password of the account Turbonomic uses to connect to the target.

    • Scope

      Specify the scope Turbonomic uses for application discovery.

      The scope is a group of virtual machines that contain the databases that are discovered as part of a separate Turbonomic target.

      If you set a scope, Turbonomic searches for virtual machines in the selected group.

      Turbonomic can monitor up to 500 virtual machines in a group. If you have more than 500 virtual machines in your environment, split them across smaller groups and then add those groups as individual targets.

    • JBoss Webservice port

      Specify the port for connections to the JBoss server. By default, the HTTP port is 9990.

    • Authenticate all database servers

      If you select this option, Turbonomic attempts to authenticate all database servers in the selected scope. If Turbonomic is unable to authenticate a database server, the target is not added and no data is collected.

    • Connect using HTTPS

      If you select this option, Turbonomic connects to the target servers using HTTPS. Make sure that the required certificate is configured for use on the host.

    • Proxy configuration

      Specify proxy information only if you connect through a proxy.

      • Proxy hostname or IP address

        Specify the address of the proxy used for this target.

      • Proxy port

        Specify the port to use with the proxy used for this target. By default, the port is 8080.

      • Proxy username

        Specify the username to use with the proxy.

      • Proxy password

        Specify the password to use with the proxy.

      • Connect using HTTPS

        Select this option if Turbonomic will connect to the proxy through HTTPS.

Application component names

Turbonomic displays discovered JBoss servers in the user interface. These names indicate whether they're standalone or in a managed domain.

The name is divided into three sections:

  • Domain Controller name or “STANDALONE”

  • The server name

  • The name or IP address of the VM hosting the JBoss server

For example:

STANDALONE:acm-jboss73 [ACM-JBoss7.3-171.47]

Monitored resources

Turbonomic monitors the following resources:

  • Application Component

    • Transaction

      Transaction is a value that represents the per-second utilization of the transactions that are allocated to a given entity.

    • Heap

      Heap is the portion of a VM or container’s memory allocated to individual applications.

    • Response time

      Response time is the elapsed time between a request and the response to that request. Response time is typically measured in seconds (s) or milliseconds (ms).

    • Threads

      Threads is the measurement of thread capacity utilized by applications.

    • Connection

      Connection is the measurement of database connections utilized by applications.

    • Remaining GC capacity

      Remaining GC capacity is the measurement of Application Component uptime that is not spent on garbage collection (GC).

Actions

Turbonomic supports the following actions:

  • Application Component

    • Resize Heap

      This action can only be executed outside Turbonomic.

    • Resize Thread Pool

      This action can only be executed outside Turbonomic.

    • Resize Connection Capacity

      This action can only be executed outside Turbonomic.