-
Language:
English
-
Language:
English
Red Hat Training
A Red Hat training course is available for Red Hat JBoss Operations Network
Release Notes
for release information
Copyright © 2012 Red Hat, Inc.
Abstract
1. New Features in JBoss Operations Network 3.1
1.1. New: JBoss Resource Plug-ins for JBoss Enterprise Application Platform 6
- A new architecture for managed domains, which introduce the idea of centralized domain controllers, local system host controllers, and low-level managed servers, with configuration defined in concentric levels from the domain down to local applications.A classic standalone server still exists that parallels the JBoss EAP 4 and 5 servers, which can be clustered or configured for high availability.
- Classes are modular, so classes can be loaded and unloaded as needed, lowering the EAP footprint and improving system performance.
- Define and manage application workflows. Test an application on a single server and then promote the application to a server group or deploy it on a new domain, a standalone server, or a cluster through a single provisioning path.
- Manage multiple standalone instances and EAP 6 domains from a single management console.
- Gain complete, chronological visibility into availability, performance metrics, auditable operations, events, and configuration changes.
- Organize EAP 6 resources in a platform-oriented hierarchy that offers a deployment-focused perspective on servers, services, and child applications.For example, a datasource in the EAP 6 console has three separate resources — the datasource definitions and then two separate views for metrics and configuration. In JBoss ON, this is consolidated into a single view for the datasource.
- Automatically detect runtime environment variables and launch script arguments. These start options can be viewed and edited through JBoss ON, which makes them easy to apply to other managed resources.
Note
1.2. Enahanced: More Control over the Start Script Environment
- The start script used, including custom start scripts.
- Required environment variables set in the
run.conf
file or the parent process (a subset of possible or all environment variables). - Any arguments passed with the start script itself.
- EAP 6 only. What user the script is running as. If the EAP server and JBoss ON agent users are different, JBoss ON assigns a
sudo
command as a prefix command to use with the start script, such assudo -u jboss -g jboss
.
Note
1.3. Enhanced: More Responsive, Accurate, and Granular Availability Monitoring
One of the biggest changes to availability is allowing availability to be scheduled at different intervals for different resources and resource types, much like a metric schedule. This allows important resources to be prioritized higher than others.
- Server availability is collected every minute.
- Service availability is collected every 10 minutes.
- Some dependent child resources have availability checking disabled entirely, and they default to the parent availability state. These resource can have availability checking enabled if desired.
A resource can be in several different states: UP, DOWN, UNKNOWN, and DISABLED.
Note
Table 1. Group Availability States
If the Resource States Are .... | ... the Group State Is ... |
---|---|
Empty Group (Unknown) | Empty |
All Red (Down) | Red (Down) |
Some Down or Unknown | Yellow (Mixed) |
Some Orange (Disabled) | Orange (Disabled) |
All Green (Up) | Green (Up) |
Previously, JBoss ON could send an alert on an availability state change, whether a resource went up or down. Alerting based on availability has been enhanced in two ways:
- A new not up option has been added for availability state changes. An alert can now be fired if a resource comes up, goes down, or goes into another (not up) state.
- A new alert condition has been added for availability duration. If a resource changes state and then stays in that state for a given amount of time, an alert is fired.
The avail
command for the agent command prompt can send an availability report that contains only changed availability states or all current states, regardless of changes. This has always been true.
avail
command checked every single resource in the agent's inventory. Now, it only checks the next scheduled resource by default. Checking the complete inventory requires the --force
option.
The agent heartbeat (the signal to the server that the agent is running) has been removed from general availability reporting. Instead, the agent sends a lightweight ping to the server.
1.4. New: Export Reports to CSV
1.5. Tech Preview: REST Interface
http://server.example.com:7080/rest/
1.6. Enhanced: Additional Monitoring Metrics
- A new trait has been added to datasource and connection factory monitoring metrics for JBoss AS 5 servers which determines whether the connection is available. This tests the connection settings every 15 minutes, by default.
- A new count for the number of open files for a JVM process has been added. Operating systems commonly put limits on how many open files a single process can have, which can cause otherwise performant JVM processes to fail when they hit that limit. Tracking the open files metric can help signal administrators when the JVM is approaching that limit.This metric is only relevant on Linux and Unix systems; it is not available on Windows systems.
- New actual free memory and actual total memory metrics have been added for platforms. These memory counts include cache and buffer settings in the available memory calculation.
- A new maximum thread count metric has been added to the embedded JBossWeb Connector resource for JBoss AS 5 servers.
1.7. New: Access Control Permission to View User Details
1.8. Enhanced: Better Discovery and Management for Custom JVM Resources
- JMX remoting is enabled, and the remoting port is set through the command line, so that the agent can read the options. This is the method that has always been used to discover JMX servers.
- The JVM process is accessible through the Java attach API and has a resource key system property set in its command line. The key allows the agent to identify the appropriate Java process and provide a unique resource identity.In this case, the agent and the JVM must be running as the same system user, or the agent cannot attach to the process.
1.9. New: Resource Plug-in to Monitor and Manage JBoss Data Grid (Infinispan)
1.10. Enhanced: Additional Information in SNMP Notifications
1.11. New: Send the Current JBoss ON Server State to the Logs
2012-05-14 19:44:28,587 INFO [SystemInfoManager] SystemInformation: ******** CAM_LDAP_BIND_PW: [- non null -] AlertDefinitionCount: [2] CAM_LDAP_BASE_DN: [o=JBoss,c=US] AVAILABILITY_PURGE: [31536000000] CAM_JAAS_PROVIDER: [false] BuildNumber: [ca099bc:3a46aff] ServerCount: [27] DATABASE_DRIVER_NAME: [PostgreSQL Native Driver] RESOURCE_GENERIC_PROPERTIES_UPGRADE: [false] ... 8< ...