Adding JBoss Application Server sources

To capture resource monitoring data from JBoss Application Server, you must configure the data source.

Before you begin

Before you can capture resource monitoring data from JBoss Application Server, you must specify the path to the JBoss client file, jbossall-client.jar on the JBoss Client Preferences page. The JBoss client file is provided with JBoss, not with HCL OneTest™ Performance. The version of the JBoss client file must match the version of JBoss Application Server running on the server under test.
Note: HCL OneTest Performance supports JBoss Application Server version 5.x.


To configure the JBoss Application Server data source:

  1. On the Location page, specify the connection and authentication information for the instance of JBoss Application Server to use to capture resource monitoring data. If you need to change the SOAP port used to communicate with the computer that is running JBoss Application Server, change the Connection information. Typically, your JBoss system administrator specifies this information.
  2. If administrative security is enabled on the computer that is running JBoss Application Server, select Administrative security enabled.
    1. Type the user ID and password for JBoss Application Server in Authentication.
    2. Select Save Password to save your password locally. If you do not save your password, you might be prompted for it (depending on the host system configuration) when you edit the configured location or when you run test schedules that use the location.
  3. On the Resource page, select the type of data to capture. The tree view shows the application server and its counter groups and counters. Be selective; monitoring all possible resource data requires substantial amounts of memory. Clear the Show only selected counters check box to see all available counters. Hold your mouse pointer over a counter to see details about what that counter measures.
  4. Configure the options on the Options page.
    1. Type the Polling Interval in seconds, for collecting resource data. For example, if you accept the default of 5 seconds, counter information will be collected at 5-second intervals from the specified host during the schedule run.
    2. Type the Timeout Interval in seconds. If the resource monitoring host does not respond within this amount of time during a schedule run, an error will be logged.
  5. To collect the resource monitoring data for the system under test that is in the cloud, in the Cloud Options tab, click the Location in Public Cloud check box.
  6. Click Next.
  7. Specify a location and name and click Finish.