2. Structural Changes in JBoss ON 3.0

There are some structural changes JBoss Operations Network 3.0 compared to JBoss ON 2.4/2.4.1 which should be called out because they affect the usage and experience of JBoss ON.

2.1. Removing Discovery Queue from the Default Dashboard

In previous versions of JBoss ON, the Discovery Portlet was included in the Dashboard by default. This portlet is no longer configured in the default Dashboard, but it can still be added to the Dashboard.
The autodiscovery queue can also be viewed in the Inventory area of the GUI.

2.2. Deprecated Platforms and Browsers

Several things that were deprecated in JBoss ON 2.4 are no longer supported in version 3.0 of JBoss Operations Network:
  • Java 5 is no longer supported for the JDK or JRE.
  • Microsoft Internet Explorer 6, Internet Explorer 7, and Firefox 2.x are no longer supported for accessing the JBoss ON GUI.
  • Solaris 9, HP-UX 11, AIX 5.2, Microsoft Windows XP, and Microsoft Windows 2000 are no longer supported platforms for the JBoss ON server or agent.
Additionally, this supported server platform is deprecated in JBoss ON 3.0:
  • Microsoft Server 2003

2.3. New and Changed Remote API Methods

Many new classes and methods have been added to the JBoss ON remote API to support new functionality, and some existing methods have changed.
The list of changes between 2.4 and 3.0 is available with the API at https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.1/html/API/index.html.

2.4. Different Name Keys for JBoss AS and JBoss EAP Servers

In previous versions of JBoss ON, both JBoss AS and JBoss EAP instances were identified in the UI as JBoss AS resources. Beginning in JBoss ON 3.0, EAP resources are identified as EAP rather than AS.