Search

3.8. Basic Setup: Installing the Server on Microsoft Windows

download PDF

Procedure 3.3. 

  1. When opening the Microsoft Windows command prompt, right-click the name or icon, and select Run as Administrator.
  2. Download the JBoss ON binaries from the Customer Support Portal.
    1. In the Customer Support Portal, click the Downloads tab to open the Product Downloads page.
    2. Select the Red Hat JBoss Operations Network link under the JBoss Development and Management to access the Software Downloads page.
    3. Download the Red Hat JBoss Operations Network 3.3 Base Distribution package by clicking the Download link.
    4. There are additional plug-in packs available for use with the JBoss ON server, accessable by using the Product drop-down menu. Plug-ins include:
      • Red Hat JBoss Enterprise Application Platform (JBoss ON for EAP),
      • Red Hat JBoss Enterprise Data Services (JBoss ON for EDS),
      • Red Hat JBoss Enterprise Web Server (JBoss ON for EWS), and
      • Red Hat JBoss Service Oriented Architecture Platform (JBoss ON for SOA-P).
  3. Create a directory for the server to be installed in.
    Use a relatively short name. Path names longer than 19 characters can cause problems running the server or executing some tasks.
  4. Unzip the server distribution to the desired home directory for JBoss ON. For example:
    C:> winzip32 -e jon-server-3.3.2.GA.zip C:\jon
    This creates a version-specific installation directory, C:\jon\jon-server-3.3.2.GA. A directory with this name should not exist prior to the unzip operation.
    Important
    Be careful when using the extract all command. Expanding the archive automatically creates a directory called jon-server-VER.RELEASE/, which is about 20 characters. Using extract all, instead of specifying the directory to which to extract the archive, can double the directory name by extracting to the archive name and then to a subdirectory — for example, C:\example\jon-server-3.3.2.GA\jon-server-3.3.2.GA. Using other tools may install it to a downloads directory such as C:\Users\Administrator\Downloads.
    If directory paths are too long, then installations on Windows can fail.
    It is recommended that you extract the archive to C:\jon, such as C:\jon\jon-server-3.3.2.GA.
  5. Set the directory path to the JDK installation. For example:
    set RHQ_JAVA_HOME=C:\Program Files\Java\jdk1.6.0_29
  6. Optional. By default, the script assumes that the database is a PostgreSQL server running on the same system as the server. Other 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.
    To change any of these defaults or to set additional information, edit the rhq-server.properties file. This is briefly covered in Section 3.6.2, “Attributes in the Properties File”.
  7. Optional. The Windows services run by default as the local system account (Default or .\LocalSystem). It is possible to configure the services to run as different users by setting the appropriate properties in the rhq-server-env.bat script.
    The RHQ_*_RUN_AS parameter sets the user account to use. The RHQ_*_RUN_AS_ME parameter uses the logged in user as the service account. If both parameters are set, then the RHQ_*_RUN_AS_ME parameter is the one which is used.
    RHQ_SERVER_RUN_AS=.\username
    RHQ_SERVER_PASSWORD=password
    
    RHQ_STORAGE_RUN_AS=.\username
    RHQ_STORAGE_PASSWORD=password
    
    RHQ_AGENT_RUN_AS=.\username
    RHQ_AGENT_PASSWORD=password
    The defined user account must have the log on as service permission. This may need to be granted explicitly.
  8. 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 and for rhq.autoinstall.server.admin.password.
    C:\jon\jon-server-3.3.2.GA\bin> serverRoot/jon-server-3.3.2.GA/bin/rhqctl install --start
    06:21:40,773 INFO  [org.jboss.modules] JBoss Modules version 1.3.3.Final-redhat-1
    
    The [rhq.autoinstall.server.admin.password] property is required but not set in [rhq-server.properties].
    Do you want to set [rhq.autoinstall.server.admin.password] value now?
    yes|no: yes
    rhq.autoinstall.server.admin.password (enter as plain text): 
    Confirm:
    rhq.autoinstall.server.admin.password (enter as plain text): 
    
    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
    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.
  9. It may take several minutes for the server process to start. Once started, the web-based user interface for the JBoss ON server can be accessed to configure resources via a web browser using the server URL http://hostname:7080. For example:
    http://server.example.com:7080
    or http://localhost:7080 for local installs.
    The username is rhqadmin and the password is the value set when running the installation program in the previous step, or configured manually by altering the value for rhq.autoinstall.server.admin.password in the rhq-server.properties file as described in Section 3.6.2, “Attributes in the Properties File”.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.