3. JBoss Operations Network Prerequisites and Basic Installation
The list of supported platforms for JBoss Operations Network are listed at http://www.redhat.com/resourcelibrary/articles/jboss-operations-network-supported-configurations.
3.1. Supported Platforms
The JBoss Operations Network server and agent require Java 6. Any operating system which supports the appropriate JVM could be run a JBoss ON server or agent. Check with Red Hat support for specific platform and environment information.
These platforms are fully supported with native JVM support:
- Red Hat Enterprise Linux 6 (32-bit and 64-bit)
- Red Hat Enterprise Linux 5 (32-bit and 64-bit)
- Red Hat Enterprise Linux 4 (32-bit and 64-bit)
- Microsoft Windows 2008 R2 (32-bit and 64-bit)
- Solaris 11 (64-bit)
- Solaris 10 (64-bit) (deprecated)
The JBoss ON server requires a Java 6 JDK, while the JBoss ON agent requires a Java 6 JRE.
3.2. Supported Databases
JBoss Operations Network 3.0.1 supports these databases for the JBoss ON server:
- Oracle 11g
- Oracle 10g (deprecated)
- PostgreSQL 9.0 (new)
- PostgreSQL 8.4.x
- PostgreSQL 8.3.x
- PostregSQL 8.2.4 and later releases (deprecated)
3.3. Hardware Requirements
Regardless of the server or database platform, there are certain minimum requirements that must be met to install the JBoss ON server and its associated database.
| Minimum | |
|---|---|
| Memory | 2 GB |
| Installation Directory Storage[a] | 10 GB |
| Temporary Directory Storage | 10 GB |
[a]
The server runs as a system user. Make sure that any system limits on user memory are set high enough to accommodate the JBoss ON server and all its data.
| |
3.4. Required Java Versions
Sun and OpenJDK Java are supported.
Note
The server requires the JDK, while the agent only requires the JRE.
3.5. Installing JBoss Operations Network 3.0.1
The Installation Guide has more information on configuration databases for the JBoss ON server, upgrading servers, and other installation information. This is a quick summary of performing an initial installation.
- Set up a database named
rhqadminand a database user namedrhqadmin. Make sure the database user has adequate permissions to perform operations on the JBoss ON database. - Stop any currently running JBoss ON instances.
serverRoot/jon-server-3.0.1.GA/bin/rhq-server.sh stop
If the new JBoss ON server will use a database that existing JBoss ON instances are also using, then all of the existing JBoss ON instances have to be stopped. Otherwise, the installer will hang when it tries to contact the database and the database is unavailable because it is in use by another JBoss ON server. - Download the server packages from the Customer Support Portal.
- Click Software in the top menu.
- In the Product field, select the product.
- Unzip the server distribution to the directory where will be executed from. For example:
cd /opt unzip jon-server-3.0.1.GA.zip
This creates ajon-server-3.0.1.GA/directory in your chosen installation root. - Install any additional agent plug-ins. Plug-in packs are available for EWS, EAP, and SOA-P.
cd /opt/jon/jon-server-3.0.1.GA unzip jon-plugin-pack-agent_plugin_name-3.0.1.GA.zip
- Run the JBoss ON server:
serverRoot/jon-server-3.0.1.GA/bin/rhq-server.sh start
- Open the server UI at
http://localhost:7080/. This will display the JBoss ON server installer. - Clicking the Click here to continue the installation link brings you to the main installer page.
- Go through the installer and fill in the information. Advanced settings can be exposed in the form.The main installer page appears different depending on the database settings.
Important
If any JBoss ON 3.0.1 instance has been opened in a browser on that machine, then it may be necessary to clear the cache manually and the restart the browser for the UI of the newly-installed server to load properly.
Simply using Ctrl+F5 is not sufficient to clear the cache.
If the server is upgraded from a 2.3.x version, then the cache must be cleared in order to load the new CSS and page styles used in JBoss ON 2.4.2.
