Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

3. JBoss Operations Network Prerequisites and Basic Installation

The list of supported platforms for JBoss Operations Network are listed at https://access.redhat.com/site/articles/112523.

3.1. Supported Configuration Information
Link kopieren

3.1.1. Changes in Required Java Versions
Link kopieren

JBoss ON supports two versions of Java:
  • Java 6 (deprecated)
  • Java 7 (new)
Both Oracle and OpenJDK Java are supported.
The server requires the JDK, while the agent only requires the JRE.

3.1.2. Changes in Supported Web Browsers
Link kopieren

JBoss ON has added these browsers that are used for testing and are supported for version 3.2.
  • Firefox 17 ESR (new)
  • Internet Explorer 9 (new)

3.2. Quick Setup for JBoss Operations Network 3.2
Link kopieren

The Installation Guide has more information on configuring databases for the JBoss ON server, upgrading servers, and other installation information. This is a quick summary of performing an initial installation.
  1. Set up a database named rhq and a database user named rhqadmin. Make sure the database user has adequate permissions to perform operations on the JBoss ON database.
    For more detailed database setup information:
  2. Download the JBoss ON binaries from the Customer Portal.
    1. In the Customer Portal, click the Downloads tab, and then the Downloads icon in the page.
    2. Select the JBoss Operations Network link under the System Management area in the Downloads page.
    3. Download the JBoss Operations Network 3.2 Base Distribution package by clicking the Download icon.
    4. There are additional plug-in packs available for EAP, EDS, EWS, and SOA-P. If any of those plug-ins will be used with the JBoss ON server, then download them as well.
  3. Unzip the server distribution to the desired home directory for JBoss ON. For example: 
    [root@server ~]# unzip jon-server-3.2.zip -d /opt/jon
    Copy to Clipboard Toggle word wrap
    This creates a version-specific installation directory, /opt/jon/jon-server-3.2. A directory with this name should not exist prior to the unzip operation.
  4. Optional. By default, the installer script assumes that the backend database is a PostgreSQL server running on the same system as the server. The server configuration settings — such as the database password, the server port numbers, the server name, and the way it handles database schema — use predefined defaults. One parameter, the bind address for the server, is empty and prompted by the control script if it is not set.
    The parameters are set in the serverRoot/jon-server-3.2/bin/rhq-server.properties file.
  5. Run the JBoss ON control script to configure the server and other services. If the rhq-server.properties file is not edited, then the script prompts for a bind address for the server; this can be set to 0.0.0.0. 
    [root@server ~]# serverRoot/jon-server-3.2/bin/rhqctl install --start
23:07:00,901 INFO  [org.jboss.modules] JBoss Modules version 1.2.2.Final-redhat-1

The [jboss.bind.address] property is required but not set in [rhq-server.properties].
Do you want to set [jboss.bind.address] value now?
yes|no: yes
jboss.bind.address: 0.0.0.0
Is [0.0.0.0] correct?
yes|no: yes
    Copy to Clipboard Toggle word wrap
    This command does two things:
    • Configure the JBoss ON server, a storage node, and an agent.
    • Start all services when the configuration process is complete.

3.3. Upgrading to JBoss Operations Network 3.2
Link kopieren

Warning

It is not possible to revert your JBoss ON server to the previous version after it is upgraded. Back up all data before upgrading.
The Installation Guide has more information on configuring databases for the JBoss ON server, upgrading servers, and other installation information. This is a quick summary of performing an initial installation.
  1. Stop the JBoss ON agent running on the server machine. Agents installed with the server are not autoupdated and must be updated with the JBoss ON server. All other agents will update themselves automatically when the server is upgraded.
    This is done by stopping the agent service or by using the exit command at the agent command prompt. 
    [root@server ~]# agentRoot/rhq-agent/bin/rhq-agent.sh 
> exit
    Copy to Clipboard Toggle word wrap
  2. Windows only. If the RHQ_AGENT_RUN_AS or RHQ_AGENT_RUN_AS_ME parameter was set in the agent's rhq-agent-env.bat file, then there must be a password and the password prompt must be disabled. 
    RHQ_AGENT_PASSWORD=secret
RHQ_AGENT_PASSWORD_PROMPT=false
    Copy to Clipboard Toggle word wrap

    Note

    If one of the RHQ_AGENT_RUN_AS* parameters is set without a password, then the agent upgrade process hangs.
    Alternatively, the RHQ_AGENT_RUN_AS* parameter can be removed prior to upgrading.
  3. Stop any currently running JBoss ON instances. 
    [root@server ~]# serverRoot/jon-server-3.1.0.GA/rhq-server.sh stop
    Copy to Clipboard Toggle word wrap
    If the JBoss ON server being upgraded is part of a high availability cloud, then all of the existing JBoss ON instances must also be stopped.
  4. Download the server packages from the Customer Portal.
    1. Click Software in the top menu.
    2. In the Product field, select the JBoss Operations Network product.
  5. Back up the server database before going through the upgrade script. In case there is a problem with the upgrade process, the backup allows you to restore to its previous state.
  6. Unzip the server packages. 
    [root@server ~]# unzip jon-server-3.2.zip -d serverRoot/jon-server-3.2
    Copy to Clipboard Toggle word wrap

    Important

    Do not copy the new server installation on top of a previous server installation.
    The directory structure within the server package gives the new server installation directory a version-specific name, such as /opt/jon/jon-server-3.2.
  7. Optional. Copy over any changes in the original rhq-server.properties file to the new file in serverRoot/jon-server-3.2/bin. Changes to this file include things like setting up SSL and enabling SMTP for email notifications.
  8. Run the rhqctl script with the upgrade subcommand and options for the original server and agent installation directories. For example: 
    [root@server ~]# ./serverRoot/jon-server-3.2/bin/rhqctl upgrade --server-dir /opt/rhq/rhq-server-old --from-agent-dir /home/rhq/rhq-agent-old --run-data-migrator
    Copy to Clipboard Toggle word wrap
    The upgrade command installs and configures a storage database automatically as part of upgrade; the --run-data-migrator option migrates the existing monitoring data into the new database. Otherwise, all historic monitoring data would be lost.
  9. Start the JBoss ON server and agent. 
    [root@server ~]# serverRoot/jon-server-3.2/bin/rhqctl start
    Copy to Clipboard Toggle word wrap
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat