Red Hat Training

A Red Hat training course is available for Red Hat JBoss Operations Network

2. Structural Changes in JBoss ON 3.1

There are some structural changes between JBoss Operations Network 3.1 and 3.0 which are called out because they affect the usage and experience of JBoss ON.

2.1. General Changes to the Remote API

All changes to the remote API, used by alert scripts and CLI scripts, are detailed in the change list for the 3.1 API.

2.2. Changes in the Resource Live Availability Method

As part of the availability monitoring enhancements, the resource manager API has been improved to change how it handles different resource states. Instead of the returning a null value for the UNKNOWN state, the ResourceManagerRemote.getLiveResourceAvailability() method now properly returns AvailabilityType.UNKNOWN.
This may affect existing remote clients or CLI scripts.

2.3. Obfuscated Passwords for Content Providers

Passwords used to access content providers such as the JBoss Customer Portal are now stored in the JBoss ON database in an obfuscated form.
During server upgrade, existing content provider configuration is upgraded as well so that the saved passwords will be obfuscated.

2.4. Deprecated Plug-ins

  • The JBoss AS/EAP 4 resource plug-in is deprecated in JBoss ON 3.1. Support will be removed in a later release, coincidental with the sunset of JBoss AS 4.
  • The PostgreSQL database resource plug-in is deprecated in JBoss ON 3.1. Support will be removed in a later release.
  • The Generic Database resource plug-in is deprecated in JBoss ON 3.1. Support will be removed in a later release.
  • The default attribute for the c:option element in agent plugin-descriptors is deprecated and will be removed in a future JBoss ON version.

2.5. Delayed Plug-In Releases for JBoss Enterprise Web Server and Tomcat

The latest versions of some JBoss products are scheduled after the general availability of JBoss Operations Network 3.1. The initial release of JBoss ON 3.1, then, will not include updates for these resources:
  • JBoss Enterprise Web Server
  • Tomcat
The EWS plug-in pack contains the resource plug-in to monitor both EWS instances and generic Tomcat servers. This plug-in will be released at some point after the 3.1 GA release.

Important

Because previous versions of JBoss ON had EWS/Tomcat plug-in packs available, existing customers who are using that plug-in to manage EWS or Tomcat instances should not upgrade to JBoss ON 3.1. Upgrading without an available EWS/Tomcat plug-in would mean that any EWS or Tomcat resource will no longer be managed by JBoss ON.
Existing JBoss ON users who are managing EWS/Tomcat resources are encouraged to stay on JBoss ON 3.0.1 until the EWS/Tomcat plug-in is available for JBoss ON 3.1.
For information on the projected release schedule for the EWS/Tomcat plug-in or to discuss issues or workarounds for EWS/Tomcat management, please contact Red Hat Global Support Service.

2.6. Deprecated Webservices Class in the Remote API

The Webservices class in the remote API is deprecated in JBoss Operations Network 3.1. Its use is not recommended.
The Webservices API will be removed in the next release of JBoss ON.