2.3. JBossAS7 Standalone Server (Tech Preview)
The JBoss AS 7 is available through a special, tech preview plug-in pack.
Note
Secured AS7 is not supported in this tech preview. If the JBoss AS 7 server is running in secure mode, JBoss ON can detect the server but it cannot manage it.
To test AS 7 with JBoss ON, first remove the
security-realm="ManagementRealm"
flag from the HTTP interface element in the AS7_installDir/standalone/configuration/standalone.xml
file:
<management-interfaces> <native-interface security-realm="ManagementRealm"> <socket-binding native="management-native"/> </native-interface> <http-interface security-realm="ManagementRealm"> <socket-binding http="management-http"/> </http-interface> ....
The correct configuration is:
<http-interface> <socket-binding http="management-http"/> </http-interface>
Warning
This resource is tech preview in JBoss Operations Network 3.0. This resource is not fully-supported. If you configure this resource in JBoss Operations Network 3.0, it must be uninventoried and re-added in later versions of JBoss Operations Network. It cannot be migrated. This means that you can lose monitoring data.
Overview
Description: | Standalone AS7 server |
Singleton: | no |
Plugin: | jboss-as-7 |
Parent Resource Types
Child Resource Types
none
Autodiscovery Process Scans
Name | Query |
---|---|
StandaloneAS | process|basename|match=^java.*,arg|org.jboss.as.standalone|match=.* |
Connection Properties
Name | Description | Required | Internal Name |
---|---|---|---|
Log Event Sources | yes | logEventSources | |
Hostname | yes | hostname | |
Port | yes | port | |
User | Management user for a secured AS | no | user |
Password | Password for the management user | no | password |
Configuration | Running configuration | yes | config |
Base directory | Base directory of the server installation | no | baseDir |
Start Script | Script used to start the server. If the path is not absolute, it is relative to the base directory | yes | startScript |
System Properties | yes | system-properties |
Note
You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.
Metrics
Name | Type | Description | Internal Name |
---|---|---|---|
Number of management requests | measurement | Number of requests sent to the controller | _internal:mgmtRequests |
Number of management requests per Minute | measurement | Number of requests sent to the controller | _internal:mgmtRequests |
Time used for management requests | measurement | Total time for requests | _internal:requestTime |
Time used for management requests per Minute | measurement | Total time for requests | _internal:requestTime |
Maximum request time | measurement | Max time for a request since last metric get | _internal:maxTime |
Note
You must use the internal name to reference Traits in Dynamic Group Definition expressions.
Configuration Properties
Name | Description | Required | Internal Name |
---|---|---|---|
Installed extensions | no | * |
Note
You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.
Operations
Name | Description |
---|---|
Reload | Make the server re-load the (changed) configuration. To load a different startup config use 'restart' |
Start | Start the server by invoking its start script |
Restart | Restart the server by shutting it down and invoking its start script |
Shutdown | Shut down the server. |
Package Types
none