Fuse HQ
Installing Fuse HQ
Version 4.3
November 2010
The experts in open source integration and messaging
Installing Fuse HQ
Version 4.3
November 2010
Installing Fuse HQ
Version 4.3
Publication date 18 Nov 2010
Copyright © 2001-2010 Progress Software Corporation and/or its subsidiaries or affiliates.
Legal Notices
These materials and all Progress software products are copyrighted and all rights are reserved by Progress Software Corporation.
The information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility
for any errors that may appear therein. The references in these materials to specific platforms supported are subject to change.
Actional, Apama, Apama (and Design), Artix, Business Empowerment, DataDirect (and design), DataDirect Connect, DataDirect
Connect64, DataDirect Technologies, DataDirect XML Converters, DataDirect XQuery, DataXtend, Dynamic Routing Architecture,
EdgeXtend, Empowerment Center, Fathom, Fuse Mediation Router, Fuse Message Broker, Fuse Services Framework, IntelliStream,
IONA, IONA (and design), Making Software Work Together, Mindreef, ObjectStore, OpenEdge, Orbix, PeerDirect, POSSENET,
Powered by Progress, PowerTier, Progress, Progress DataXtend, Progress Dynamics, Progress Business Empowerment, Progress
Empowerment Center, Progress Empowerment Program, Progress OpenEdge, Progress Profiles, Progress Results, Progress
Software Developers Network, Progress Sonic, ProVision, PS Select, Savvion, SequeLink, Shadow, SOAPscope, SOAPStation,
Sonic, Sonic ESB, SonicMQ, Sonic Orchestration Server, SonicSynergy, SpeedScript, Stylus Studio, Technical Empowerment,
WebSpeed, Xcalia (and design), and Your Software, Our Technology–Experience the Connection are registered trademarks of
Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and/or other countries. AccelEvent, Apama
Dashboard Studio, Apama Event Manager, Apama Event Modeler, Apama Event Store, Apama Risk Firewall, AppsAlive, AppServer,
ASPen, ASP-in-a-Box, BusinessEdge, Business Making Progress, Cache-Forward, DataDirect Spy, DataDirect SupportLink, Fuse,
Future Proof, GVAC, High Performance Integration, ObjectStore Inspector, ObjectStore Performance Expert, OpenAccess, Orbacus,
Pantero, POSSE, ProDataSet, Progress ESP Event Manager, Progress ESP Event Modeler, Progress Event Engine, Progress RFID,
Progress Software Business Making Progress, PSE Pro, SectorAlliance, SeeThinkAct, Shadow z/Services, Shadow z/Direct, Shadow
z/Events, Shadow z/Presentation, Shadow Studio, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects,
SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow,
Sonic Business Integration Suite, Sonic Process Manager, Sonic Collaboration Server, Sonic Continuous Availability Architecture,
Sonic Database Service, Sonic Workbench, Sonic XML Server, The Brains Behind BAM, WebClient, and Who Makes Progress
are trademarks or service marks of Progress Software Corporation and/or its subsidiaries or affiliates in the U.S. and other countries.
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
Any other trademarks contained herein are the property of their respective owners.
Third Party Acknowledgments
Fuse ESB 4.3 incorporates ANTLR, Another Tool for Language Recognition v2.7.7 from Terrence Parr. Such technology is subject
to the following terms and conditions: SOFTWARE RIGHTS ANTLR 1989-2006 Developed by Terence Parr Partially supported
by University of San Francisco & jGuru.com. We reserve no legal rights to the ANTLR--it is fully in the public domain. An individual
or company may do whatever they wish with source code distributed with ANTLR or the code generated by ANTLR, including
the incorporation of ANTLR, or its output, into commercial software. We encourage users to develop software with ANTLR.
However, we do ask that credit is given to us for developing ANTLR. By "credit", we mean that if you use ANTLR or incorporate
any source code into one of your programs (commercial product, research project, or otherwise) that you acknowledge this fact
somewhere in the documentation, research report, etc... If you like ANTLR and have developed a nice tool with the output, please
mention that you developed it using ANTLR. In addition, we ask that the headers remain intact in our source code. As long as
these guidelines are kept, we expect to continue enhancing this system and expect to make other tools available as they are
completed. The primary ANTLR guy: Terence Parr parrt@cs.usfca.edu parrt@antlr.org.
Fuse ESB 4.3 incorporates ANTLR, Another Tool for Language Recognition v3.0.1 from Terence Parr. Such technology is subject
to the following terms and conditions: [The "BSD licence"] Copyright 2003-2006 Terence Parr All rights reserved. Redistribution
and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse
or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY
THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Fuse ESB 4.3 incorporates Apache ORO v2.0.8 from the Apache Foundation. Such technology is subject to the following terms
and conditions: Apache Software License Version 1.1 Copyright 2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation
included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed
by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software
itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Apache" and "Apache Software
Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For
written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor
may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS
PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For
more information on the Apache Software Foundation, please see http://www.apache.org/. Portions of this software are based
upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois,
Urbana-Champaign.
Fuse ESB 4.3 GA incorporates ASM v1.5.3 from INRIA, France Telecom. Such technology is subject to the following terms and
conditions: ASM: a very small and fast Java byte code manipulation framework Copyright 2000, 2002, 2003 INRIA, France
Telecom All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list
of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither
the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Fuse ESB 4.3 GA incorporates JDOM v1.1 from Jason Hunter& Brett McLaughlin. Such technology is subject to the following
terms and conditions: jdom License - Copyright 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved. Redistribution
and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer. 2.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows
these conditions in the documentation and/or other materials provided with the distribution. 3. The name "JDOM" must not be
used to endorse or promote products derived from this software without prior written permission. For written permission, please
contact {request_AT_jdom_DOT_org}. 4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear
in their name, without prior written permission from the JDOM Project Management {request_AT_jdom_DOT_org}. In addition,
we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the
software itself an acknowledgement equivalent to the following: "This product includes software developed by the JDOM Project
(http://www.jdom.org/)." Alternatively, the acknowledgment may be graphical using the logos available at
http://www.jdom.org/images/logos. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Fuse ESB 4.3 incorporates OSCore – opensymphony v2.2.4, OSWorkflow v2.7.0, PropertySet – opensymphony v1.3. Such
technologies are subject to the following terms and conditions: The OpenSymphony Software License, Version 1.1 (this license
is derived and fully compatible with the Apache Software License - see http://www.apache.org/LICENSE.txt) Copyright 2001-2004
The OpenSymphony Group. All rights reserved. Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. 1. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
2. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product
includes software developed by the OpenSymphony Group (http://www.opensymphony.com/)." Alternately, this acknowledgment
may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 3. The names
"OpenSymphony" and "The OpenSymphony Group" must not be used to endorse or promote products derived from this software
without prior written permission. For written permission, please contact license@opensymphony.com. 4. Products derived from
this software may not be called "OpenSymphony" or "OSCache", nor may "OpenSymphony" or "OSCache" appear in their name,
without prior written permission of the OpenSymphony Group. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION
OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Fuse ESB 4.3 incorporates Saxon XSLT and XQuery Processor – saxon v9.1.0.1. The contents of this file are subject to the Mozilla
Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a
copy of the License at http://www.mozilla.org/MPL/. Software distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and
limitations under the License. The Original Code is all Saxon modules labeled with a notice referring to this license. The Initial
Developer of the Original Code is Michael Kay, except where otherwise specified in an individual module. Portions created by
other named contributors are copyright as identified in the relevant module. All Rights Reserved. Contributor(s) are listed in the
documentation: see notices/contributors.
Fuse ESB 4.3 incorporates Rhino: JavaScript for Java v1.7R1. The contents of this file are subject to the Mozilla Public License
Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License
at http://www.mozilla.org/MPL/. Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY
OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the
License. The Original Code is Rhino code, released May 6, 1999. The Initial Developer of the Original Code is Netscape
Communications Corporation. Portions created by the Initial Developer are Copyright 1997-1999 the Initial Developer. All Rights
Reserved. Contributor(s).
Table of Contents
1. Installation Prerequisites ..................................................................................................... 13
Planning your installation ................................................................................................. 14
Fuse HQ Server Requirements ........................................................................................... 15
Fuse HQ Agent Requirements ........................................................................................... 17
Fuse HQ Repository Requirements ..................................................................................... 18
2. Preparing the Fuse HQ Repository ......................................................................................... 19
The Built-in Repository .................................................................................................... 20
Preparing an Oracle Database ........................................................................................... 21
Preparing a PostgreSQL Database ...................................................................................... 22
Preparing a MySQL Database ............................................................................................ 26
Backing Up Your Repository ............................................................................................. 28
3. Installing the Fuse HQ Server ............................................................................................... 29
Downloading a Fuse HQ Server Installation Package ............................................................... 30
Running the Fuse HQ Server Installer .................................................................................. 31
Fuse HQ Server Configuration Settings ................................................................................ 35
Installing the Fuse HQ Server License ................................................................................. 37
4. Installing Fuse HQ Agents ................................................................................................... 39
Downloading a Fuse HQ Agent Installation Package ................................................................ 40
Fuse HQ Agent Installations .............................................................................................. 41
5. Running the Fuse HQ Server and the Fuse HQ Agent ................................................................. 43
Starting and Stopping the Fuse HQ Server ............................................................................ 44
Starting and Stopping the Fuse HQ Agent ............................................................................ 46
6. Upgrading Fuse HQ ............................................................................................................ 51
Upgrading the Fuse HQ Server .......................................................................................... 52
Upgrading the Fuse HQ Agent ........................................................................................... 54
7. Uninstalling Fuse HQ Components ......................................................................................... 57
Uninstalling the Fuse HQ Server ........................................................................................ 58
Uninstalling a Fuse HQ Agent ........................................................................................... 59
9Fuse HQ Installing Fuse HQ Version 4.3
Fuse HQ Installing Fuse HQ Version 4.310
List of Tables
3.1. Installation Mode Arguments for the setup Command ................. 31
3.2. Configuration Settings for the Fuse HQ Server ........................... 35
5.1. Configuration Settings for the Fuse HQ Agent ........................... 46
11Fuse HQ Installing Fuse HQ Version 4.3
Fuse HQ Installing Fuse HQ Version 4.312
Chapter 1. Installation Prerequisites
Before attempting to install Fuse HQ, decide where you are going to install Fuse HQ components and make sure
your systems meets the minimum requirements.
Planning your installation ......................................................................................................... 14
Fuse HQ Server Requirements ................................................................................................... 15
Fuse HQ Agent Requirements ................................................................................................... 17
Fuse HQ Repository Requirements ............................................................................................. 18
13Fuse HQ Installing Fuse HQ Version 4.3
Chapter 1. Installation Prerequisites
Planning your installation
What is Fuse HQ Fuse HQ is a tool for monitoring and managing the Fuse infrastructure. With
Fuse HQ you can:
• Inventory resources on your network
• Monitor resources
• Send alerts when problems occur
• Control resources
Fuse HQ Components Before you begin installation of Fuse HQ, you must decide where you will
install the following Fuse HQ functional components:
DescriptionComponent
Fuse HQ Server
Fuse HQ Agent
Fuse HQ Repository
The central component that controls agents, manages
data, and provides a browser-based GUI
The component that finds resources, gathers data,
controls software, and communicates with the server.
Agents are installed on the systems in a network that
you want to monitor or control. See "Fuse HQ Agent
Requirements" on page 17 Note that agents cannot
function remotely; they can only monitor resources on
the system where they are installed.
A database, managed by the Server. It stores Fuse HQ
data and is responsible for ensuring data integrity and
access.
See "Fuse HQ Repository Requirements" on page 18
Fuse HQ Installing Fuse HQ Version 4.314
Fuse HQ Server Requirements
Fuse HQ Server Requirements
Check this section before you install HQ Server on the machine that will be
the central control and management system for Fuse HQ.
Hardware • 1 GHz or higher Pentium 4, or equivalent (2 × 2.4GHz Pentium Xeon or
equivalent recommended)
• 1 GB RAM (4 GB or more recommended)
• 1-5 GB Free Disk Space
Operating systems • Linux
• Windows 2003 Server
• Solaris 10 or higher
• Max OS X (Intel x86)
Note
Although HQ Server is not supported under Windows XP in production
environments, the configuration works; you can run small evaluation
deployments under Windows XP.
Web browsers Fuse HQ supports the following Web browsers:
• Firefox 1.5.x and 2.0.x
• Safari
• Internet Explorer 6 and 7
• Internet Explorer 8, except on Windows 2008
Firefox is the recommended browser.
Java The Fuse HQ Server is bundled with a JRE and its use is recommended.
However, if you prefer to use a JRE (or JDK) that may already be installed
15Fuse HQ Installing Fuse HQ Version 4.3
Chapter 1. Installation Prerequisites
on the system, the JRE or JDK should be version 1.5 or 1.6. We recommend
Java 1.5.
IP address The system where you install the Fuse HQ Server must have a static IP
address. A dynamic IP address may disable communication with the Fuse
HQ Agent. Check with your system administrator to determine if you need to
implement a static IP address on the system where you want to install the
Fuse HQ Server.
X windows On UNIX platforms, Fuse HQ Server requires some of the X libraries to create
charts and other graphics in the user interface. Specifically libXp.so.6 must
be installed on the system.
The symptoms of missing X libraries are broken graphics and error messages
similar to the following:
java.lang.NoClassDefFoundError at
net.hyperic.hq.ui.taglib.NavMapTag._getResourceTree(NavMapTag.java:252)
at
net.hyperic.hq.ui.taglib.NavMapTag.doStartTag(NavMapTag.java:160)
etc . . .
Fuse HQ Installing Fuse HQ Version 4.316
Fuse HQ Agent Requirements
Check this section before you install the Fuse HQ Agent on the systems that
you want to monitor.
Hardware • 500 MHz Celeron or higher, or equivalent
• 256 MB RAM
• 500 MB Free Disk Space
• Supported Operating System
Operating systems • Linux
• Windows XP, 2003 Server, or 2008 SE
• Windows 7
• Solaris 8 or higher
Fuse HQ Agent Requirements
• Mac OS X
• HP-UX 11.11 or higher
• AIX 5.2 or higher
Java The Fuse HQ is bundled with a JRE and its use is recommended. However,
if you prefer to use a JRE (or JDK) that may already be installed on the system,
the JRE or JDK should be version 1.5 or 1.6. We recommend Java 1.5.
IP address The system where you install the Fuse HQ Agent must have a static IP address.
A dynamic IP address may disable communication with the Fuse HQ Server.
Check with your system administrator to determine if you need to implement
a static IP address on the system where you want to install the Fuse HQ
Agent.
17Fuse HQ Installing Fuse HQ Version 4.3
Chapter 1. Installation Prerequisites
Fuse HQ Repository Requirements
For evaluation and testing purposes, the Fuse HQ Server installation includes
a default, built-in database that you can install on the local host. However,
for actual deployment of Fuse HQ (particularly in large installations), you
should install and configure one of the following databases on a remote host:
• Oracle 10g or 11g
• PostgreSQL 8.3 or higher (not supported on Windows in production
environments)
• MySQL 5.0.45 or higher (5.1.x is recommended)
See "Preparing the Fuse HQ Repository" on page 19 for more information.
Fuse HQ Installing Fuse HQ Version 4.318
Chapter 2. Preparing the Fuse HQ Repository
Before installing the Fuse HQ Ser ver or Agents, you should prepare a database to serve as a repository for Fuse
HQ data.
The Built-in Repository ............................................................................................................ 20
Preparing an Oracle Database ................................................................................................... 21
Preparing a PostgreSQL Database .............................................................................................. 22
Preparing a MySQL Database .................................................................................................... 26
Backing Up Your Repository ..................................................................................................... 28
19Fuse HQ Installing Fuse HQ Version 4.3
Chapter 2. Preparing the Fuse HQ Repository
The Built-in Repository
The built-in repository requires no preparation. It is available as an option
when you install theFuse HQ Server. If you intend to use the built-in repository,
go to "Installing the Fuse HQ Server" on page 29.
The built-in database is useful for testing and evaluation purposes. However,
for actual deployment of Fuse HQ you should consider setting up an Oracle,
PostgreSQL, or MySQL database.
Fuse HQ Installing Fuse HQ Version 4.320
Preparing an Oracle Database
Preparing an Oracle Database
Creating an Oracle instance for
use as the Fuse HQ repository
Creating the user that will access
the database
Give the required permissions to
the user
Ideally, the Oracle server should run on a system where no other Fuse HQ
components are installed. Install Oracle on the machine you will use, and
create a database.
You can use SQL*Plus to create a user in Oracle. For example:
1. Log into the Oracle instance with SQL*Plus as the system user.
2. Use CREATE USER to create a user name and password.
For example, the following creates a user named HQUSER whose
password is HQPASSWORD:
SQL> CREATE USER HQUSER IDENTIFIED BY HQPASSWORD;
For example, use the SQL*Plus GRANT command as follows:
SQL> GRANT CONNECT, RESOURCE, CREATE VIEW TO HQUSER;
21Fuse HQ Installing Fuse HQ Version 4.3
Chapter 2. Preparing the Fuse HQ Repository
Preparing a PostgreSQL Database
Prerequisites Preparing a PostgreSQL database for the Fuse HQ repository is relatively
complicated and can vary depending on the operating system and other
factors. PostgreSQL usually requires a DBA or someone with DBA knowledge
for setup and maintenance. You can also find help by consulting the
PostgreSQL documentation1.
This section gives you an idea of the process, based on the following
prerequisites:
Redhat Enterprise Linux 4Operating system
PostgreSQL 8.3Database
192.168.1.4Database IP address
192.168.1.6HQ Server IP Address
/var/lib/pgsql/data/Install directory
/var/lib/pgsql/data/postgresql.confConfiguration file
/var/lib/pgsql/data/pg_hba.confHost-based authentication file
Note
Fuse HQ automatically creates a language in the PostgreSQL
database, but not in PostgreSQL 8.0. You must run the following
command on a PostgreSQL 8.0 database:
createlang plpgsql <DATABASE NAME>
The createlang executable is located in the bin directory of your
PostgreSQL installation.
Installing PostgreSQL Since the OS is Redhat Linux, you can use the Yellowdog Updater, Modified
(YUM) to install the PostgreSQL on the system where you want to create a
Fuse HQ Repository. For example:
yum install postgresql postgresql-server
1
http://www.postgresql.org/docs/
Fuse HQ Installing Fuse HQ Version 4.322
Preparing a PostgreSQL Database
PostgreSQL installs in the following directories:
/etc/init.d/
/usr/bin/
/usr/share/doc
/var/lib/pgsql/
Initializing PostgreSQL Use the following command to run the YUM initialization scripts that set up
some basic configuration files:
/etc/init.d/postgresql start
Creating a database and a user
account
To create a database and a user account:
1. Enter the following at a command prompt on the system where you
installed the PostgreSQL server:
su - postgres
Do not omit the dash.
The command prompt changes to psql to indicate that you have started
the PostgreSQL interactive shell.
2. Using the PostgreSQL shell, create a user with permission to log in and
create databases. The following, for example, creates a user named
admin whose password is hqadmin:
create role admin with login createdb password 'hqadmin';
3. Create the database that you will use as the Fuse HQ repository and
specify admin as the owner. For example:
create database "HQ" owner admin;
Note that the quotes around "HQ" cause the database name to be in
uppercase.
23Fuse HQ Installing Fuse HQ Version 4.3
Chapter 2. Preparing the Fuse HQ Repository
4. Enter \q to exit the PostgreSQL shell.
Configuring PostgreSQL to accept
To configure PostgreSQL to accept network connections:
network connections
1. In the PostgreSQL configuration file,
/var/lib/pgsql/data/postgresql.conf, change the default
commented listen address entry to:
listen_addresses = '*'
This causes PostgreSQL to listen to all network interfaces, not just the
local loopback address.
2. Add these lines to /var/lib/pgsql/data/pg_hba.conf, the Host-base
Authentication (HBA) file:
TYPE DATABASE USER CIDR-ADDRESS METHOD
local all all ident sameuser
host all all 192.168.1.6/32 password
See the PostgreSQL 8.2.12 Documentation2for more information.
Tuning PostgreSQL for Fuse HQ Now you need to tune your PostgreSQL installation for use with Fuse HQ.
1. In the postgresql.conf file, edit or add the following parameters:
fsync=false
shared_buffers=10000
work_mem=2048
statement_timeout=30000
2. (Optional) Configure the database so that Fuse HQ can monitor it by
adding the following parameters to the postgresql.conf file:
stats_start_collector = true
stats_block_level = true
stats_row_level = true
stats_reset_on_server_start = false
2
http://www.postgresql.org/docs/8.2/interactive/auth-pg-hba-conf.html
Fuse HQ Installing Fuse HQ Version 4.324
Preparing a PostgreSQL Database
Although database monitoring is not required, it is recommended.
25Fuse HQ Installing Fuse HQ Version 4.3
Chapter 2. Preparing the Fuse HQ Repository
Preparing a MySQL Database
Creating a database and a user
account
After you connect to a MySQL server, issue the following commands at the
mysql> prompt:
create user 'hqadmin'@'localhost' identified by 'passwd';
create database HQ;
grant all on HQ.* to 'hqadmin'@'localhost';
Note
The assumption here is that a MySQL server is installed and running
on the system that is hosting the Fuse HQ Repository.
Configuring MySQL To configure MySQL for use with Fuse HQ:
1. Edit the MySQL configuration file to match the settings that follow. The
configuration file is /etc/my.cnf on UNIX, and my.ini on Windows.
Note
Many of the settings mentioned in this section are based on the
assumption that you are using the InnoDB storage engine3for
MySQL. The values are suggestions. You can experiment with
other InnoDB and other parameter values in order to achieve
the best performance on your system.
2. (Optional) Enable the full query log so that every query (even ones with
incorrect syntax) that the Server receives is logged. This is useful for
debugging, but it is usually disabled in production use.
Be sure to change the paths given here to match your environment:
log-error = /home/mysql/log/mysqld.err
3
http://dev.mysql.com/doc/refman/4.1/en/innodb-parameters.html
Fuse HQ Installing Fuse HQ Version 4.326
Preparing a MySQL Database
log = /home/mysql/log/mysql_general.log
3. Enable the printing of warnings to the error log file, for example:
log_warnings
server-id = 1
If you have any problem with MySQL, you should enable logging of
warnings and examine the error log for possible explanations.
4. Set the default storage engine to InnoDB and set other parameter values:
default-storage_engine=innodb
bulk_insert_buffer_size = 32M
join_buffer_size = 8M
max_heap_table_size = 256M
tmp_table_size = 256M
max_tmp_tables = 48
myisam_sort_buffer_size = 256M
5. Set logging parameters:
innodb_flush_log_at_trx_commit = 0
innodb_log_buffer_size = 64M
innodb_log_file_size = 256M
Note that setting innodb_flush_log_at_trx_commit to 0 allows the
best performance but risks data loss if the server crashes. The log buffer
is written to the log file and flushed to disk approximately once per
second. If the value is 1, the log buffer is written to the log file and flushed
to disk at every transaction commit. If the value is 2, the log buffer is
written to the log file at every transaction commit, but the flush to disk
only occurs once per second.
6. Set the size of the buffer pool:
innodb_buffer_pool_size = 256M
If you have a large installation, you should probably increase this value.
If your have a system dedicated to the MySQL server, for example, you
might set this value to about 80% of total memory.
27Fuse HQ Installing Fuse HQ Version 4.3
Chapter 2. Preparing the Fuse HQ Repository
Backing Up Your Repository
You should back up your repository database on a regular basis. Note that
there is a backup script, db-archive.sh, in the Fuse HQ installer's bin directory.
However, you should consider implementing automatic backups. Consult with
your DBA for more information.
Fuse HQ Installing Fuse HQ Version 4.328
Chapter 3. Installing the Fuse HQ Server
You install the Fuse HQ Server on a system that you want to use to manage and monitor Fuse HQ. You download
and unpack the installation files. Then you run the installer (the setup script) to complete the installation.
Downloading a Fuse HQ Server Installation Package ....................................................................... 30
Running the Fuse HQ Server Installer .......................................................................................... 31
Fuse HQ Server Configuration Settings ........................................................................................ 35
Installing the Fuse HQ Server License ......................................................................................... 37
29Fuse HQ Installing Fuse HQ Version 4.3
Chapter 3. Installing the Fuse HQ Server
Downloading a Fuse HQ Server Installation Package
Download page Go to the Fuse HQ download web page1to obtain an installation package for
Fuse HQ Server. If you do not already have an account on the
fusesource.com Web site, you will be prompted to create an account before
you proceed with the download.
Selecting an installation package Select the installation package that matches the system where you intend to
install Fuse HQ Server. See "Hardware" on page 15 for details of supported
platforms.
Note
If you already have a JRE that you want to use, download the No
JRE package. However, be sure that your JAVA_HOME environment
variable is set to point to the particular JRE you want Fuse HQ to
run on.
Save the file (a .zip or a.tar.gz file) to a directory where you can unpack
it. Unpack the file using the appropriate utility ( WinZip, tar, gunzip, etc.).
Note
On some Solaris systems, the default version of tar is incompatible
with Fuse HQ installation packages. When tar is incompatible,
unpacking will be incomplete and you may see checksum errors.
The solution is to install GNU tar. See the instructions for installing
GNU tar2for more information.
1
http://fusesource.com/download_fuse_hq
2
http://sunsolarisadmin.blogspot.com/2007/03/how-to-install-gnu-tar-in-solaris.html
Fuse HQ Installing Fuse HQ Version 4.330
Running the Fuse HQ Server Installer
Running the Fuse HQ Server Installer
The installer script The Fuse HQ Server Installer is a script called setup.bat on Windows platforms
and setup.sh on non-Windows platforms. You run the installer on the system
that you want to use to manage and monitor Fuse HQ.
Choosing the install mode Before you begin, you should decide which install mode to run. You specify
the install mode as an argument to the setup command. The mode arguments
are listed in Table 3.1.
Table 3.1. Installation Mode Arguments for the setup Command
Installation ModeArgument
No argument
-postgresql
-oracle
-mysql
Quick install mode. It installs the Fuse
HQ components with default settings,
including the built-in repository.
Quick install mode when using a
PostgreSQL database as a repository,
which should be created prior to the
Server installation. See instructions
for preparing a PostgreSQL database.
This mode asks for database
connection information but uses
defaults for everything else.
Quick install mode when using an
Oracle database as a repository,
which should be created prior to the
Server installation. See instructions
for preparing an Oracle database. This
mode asks for database connection
information but uses defaults for
everything else.
Quick install mode when using a
MySQL database as a repository,
which should be created prior to the
Server installation. This mode asks for
MySQL database connection
information but uses defaults for
everything else. See instructions for
preparing a MySQL
31Fuse HQ Installing Fuse HQ Version 4.3
Chapter 3. Installing the Fuse HQ Server
-full
Installation ModeArgument
database on page 26 and copying the
MySQL JDBC driver.
Full install mode. The installer
prompts for almost everything: ports
to use, administrator user name and
password, repository to use, etc.
Copying the MySQL JDBC driver
to the installer bin directory
Running the installer After you unpack the Fuse HQ download, open a command line interpreter (
If you plan to use MySQL as a repository, you must copy the MySQL JDBC
driver JAR file to the fuse-hq-installer\installer-4.3.0.0-fuse\bin
directory.
cmd.exe on Windows) or a command shell (for example, /bin/sh on UNIX).
Navigate to the fuse-hq-installer directory and run setup on the command
line. For example, the following command would start the installer in full
install mode:
setup -full
When you run the installer, the first information you see is the Fuse HQ
Clickwrap License Agreement. If you accept the terms of the agreement, you
can proceed with the installation by selecting the components you want to
install.
Note
If you see a message stating that tools.jar cannot be found, ignore
it. This message occurs when the JAVA_HOME variable does not
reference a JRE that is part of a JDK. This condition does not affect
the installer.
Fuse HQ Installing Fuse HQ Version 4.332
Running the Fuse HQ Server Installer
Choosing components When you get past the license agreement, the installer asks which components
you wish to install. Select at least one of the following components:
DescriptionNumberComponent
1Fuse HQ Server
The central component
that controls agents,
manages data, and
provides a user interface.
2Fuse HQ Agent
A component that
monitors the system it is
installed on. It reports to
and is managed by the
Fuse HQ Server. The
Fuse HQ Agent is
installed on one or many
systems and can be
installed on the same
system that is running
the Fuse HQ Server.
You can select multiple components by entering component numbers separated
by commas. For example, the following shows how you would select the Fuse
HQ Server and Shell:
Choose which software to install:
1: Fuse HQ Server
2: Fuse HQ Agent
You may enter multiple choices, separated by commas.
1,2
Specifying the installation path Next, the installer prompts you to specify where to create the directories where
the components will be installed. Either press ENTER to accept the default
or type a path name. The following shows the path prompts on a Windows
system:
33Fuse HQ Installing Fuse HQ Version 4.3
Chapter 3. Installing the Fuse HQ Server
HQ server installation path [default 'C:\Program Files']:
HQ agent installation path [default 'C:\Program Files']:
Completing the installation What happens next, depends on which installation mode you chose:
• If you chose to do a quick install, the installation completes with all the
default configuration settings. You can view the installation log,
hq-install.log in
fuse-hq-installer/installer-4.3.0.0-fuse/logs/hq-install.log.
• If you chose to do a quick install with one of the external repository options
(-postgresql, -oracle, or -mysql), the installer will prompt you to enter a
JDBC connection URL, a user name, and a password. Then, the installation
completes with all the default configuration settings.
The installer offers a default JDBC connection URL, which you can use if
you installed the repository on the same system as the Fuse HQ Server.
The user name and password should refer to an account that has
administrative privileges. The instructions in "Preparing the Fuse HQ
Repository" on page 19 describe how to create administrative accounts in
all three types of repository.
• If you chose a full install, the installer prompts you for configuration
settings.
When the installation completes, you can install Fuse HQ Agents on the
systems you want to monitor, or you can start the Fuse HQ Server and Agents
that you already installed.
Fuse HQ Installing Fuse HQ Version 4.334
Fuse HQ Server Configuration Settings
Fuse HQ Server Configuration Settings
If you run the installer using the -full option, the installer prompts you for
configuration settings in the order shown in Table 3.2.
Table 3.2. Configuration Settings for the Fuse HQ Server
DescriptionDefaultSetting
7080HTTP port
7443HTTPS port
2099JNP port
9093Mbean port
http://hostname:_http_portGUI URL
hqadmin@hostnameFuse HQ Server's email address
The port the Fuse HQ Server's
web-based GUI uses for HTTP
communications.
The port the Fuse HQ Server's
web-based GUI uses for secure
HTTPS communications.
The port the Fuse HQ Server uses for
the JNP service.
The port the Fuse HQ Server uses for
the Mbean Server .
The URL Fuse HQ Agents will use to
send alert notifications to the
web-based GUI. (You can change this
value on the Fuse HQ Server
Administration screen.)
The From address on alert notification
emails sent by the Fuse HQ Server.
Note that most email servers will not
deliver mail without a valid domain
name in the From field.
HQ Built-in DatabaseBackend database
The type of database that the Fuse
HQ Server will use as a repository. If
you choose anything other than the
default built-in database, the installer
will prompt you for a JDBC
connection URL, a user name, and a
password. If you choose the built-in
database, the installer will prompt
you for a port number. The default is
9432.
35Fuse HQ Installing Fuse HQ Version 4.3
Chapter 3. Installing the Fuse HQ Server
DescriptionDefaultSetting
hqadminAdministrator's user name
The user name of the original Fuse
HQ administrator.
hqadminAdministrator's password
The password of the original Fuse HQ
administrator.
hqadmin@hostnameAdministrator's address
The email address assigned to the
initial Fuse HQ administrator. Alert
notifications are sent to this address
if the Administrator is configured to
receive alert notifications.
The installer saves your settings in a file named hq-server-install.conf
in the ServerInstallDir/data directory. You can open and view this file in
a text editor after the installation completes.
Fuse HQ Installing Fuse HQ Version 4.336
Installing the Fuse HQ Server License
Installing the Fuse HQ Server License
Obtaining an evaluation license After logging on to the fusesource.com Web site and downloading the Fuse
HQ Server software as described in "Downloading a Fuse HQ Server
Installation Package" on page 30, you should receive a 90-day evaluation
license by e-mail within 24 hours.
Obtaining a full license Full licenses for Fuse HQ are available to organizations that have purchased
Fuse support. For details, please contact Fuse Customer Support3.
Installing the license You will receive the license file as an e-mail attachment, license.xml. To
install the license, copy the license.xml file into the InstallDir/conf
directory of your server installation (over-writing the existing dummy license
file at that location).
Note
It is essential that the license file is spelled exactly as shown here,
all in lowercase letters. If your mail software changes the
capitalization of the file name, license.xml, make sure to correct
the spelling when you save it to the file system.
3
http://fusesource.com/contact
37Fuse HQ Installing Fuse HQ Version 4.3
Fuse HQ Installing Fuse HQ Version 4.338
Chapter 4. Installing Fuse HQ Agents
After installing the Fuse HQ Server, install Fuse HQ Agents on the systems that you want to monitor. Agent-only
installations are accomplished by unpacking downloads.
Downloading a Fuse HQ Agent Installation Package ........................................................................ 40
Fuse HQ Agent Installations ...................................................................................................... 41
39Fuse HQ Installing Fuse HQ Version 4.3
Chapter 4. Installing Fuse HQ Agents
Downloading a Fuse HQ Agent Installation Package
Download page Go to the Fuse HQ download web page1to obtain an installation package for
Fuse HQ Agent. If you do not already have an account on the
fusesource.com Web site, you will be prompted to create an account before
you proceed with the download.
Selecting an installation package If you intend to install both a Fuse HQ Server and Agent, choose a package
for one of the platforms described in "Fuse HQ Server Requirements"
on page 15 and follow the instructions in "Running the Fuse HQ Server
Installer" on page 31.
Select the installation package that matches the system where you intend to
install Fuse HQ Agent (see "Fuse HQ Agent Requirements" on page 17 for
details of supported platforms).
Note
If you already have a JRE that you want to use, download the No
JRE package. However, be sure that your JAVA_HOME environment
variable is set to point to the particular JRE you want Fuse HQ to
run on. If you have a particular JRE you want Fuse HQ to run on,
you can set the HQ_JAVA_HOME environment variable.
1
http://fusesource.com/download_fuse_hq
Save the file to the directory where you want to install the Fuse HQ Agent.
On Windows, for example, Agents are often installed in a folder created under
C:\Program Files, but there is no requirement to use any particular
installation directory. However, you must install the Fuse HQ Agent on the
system that you want to monitor. Agents cannot monitor remote systems.
Fuse HQ Installing Fuse HQ Version 4.340
Fuse HQ Agent Installations
Fuse HQ Agent Installations
Agent-only installations When the Fuse HQ Agent installation package is downloaded to a suitable
directory, unpack the file using the appropriate utility ( WinZip, tar, gunzip,
etc.). Unpacking completes the installation. It is not necessary to run an
installer.
Note
On some Solaris systems, the default version of tar is incompatible
with Fuse HQ installation packages. When tar is incompatible,
unpacking will be incomplete and you may see checksum errors.
The solution is to install GNU tar. See the instructions for installing
GNU tar2for more information.
After unpacking the installation package, you will see the following files and
folders:
log/bin/
wrapper/bundles/
README.txtconf/
jre/
Server and Agent installations You can also install a Fuse HQ Agent when you run the installer (setup) that
comes with Fuse HQ Server packages. See "Installing the Fuse HQ Server"
on page 29 for more details.
2
http://sunsolarisadmin.blogspot.com/2007/03/how-to-install-gnu-tar-in-solaris.html
41Fuse HQ Installing Fuse HQ Version 4.3
Fuse HQ Installing Fuse HQ Version 4.342
Chapter 5. Running the Fuse HQ Server and the Fuse HQ Agent
When installation is complete, start the Fuse HQ Server and Agents. The initial startup of the Fuse HQ Agent
prompts for configuration information.
Starting and Stopping the Fuse HQ Server .................................................................................... 44
Starting and Stopping the Fuse HQ Agent .................................................................................... 46
43Fuse HQ Installing Fuse HQ Version 4.3
Chapter 5. Running the Fuse HQ Server and the Fuse
HQ Agent
Starting and Stopping the Fuse HQ Server
Starting and stopping the Fuse
HQ Server on Windows systems
Starting and stopping the Fuse
HQ Server on non-Windows
systems
The Fuse HQ Server can be started on Windows after establishing it as a
service.
To establish the Fuse HQ Server as a service:
1. In a command prompt window, open the ServerInstallDir\bin
directory.
2. Run the following command:
hq-server.exe -i
When the command completes, you will be able start and stop the Fuse HQ
Server and the built-in database from the Services control panel
(Start>Programs>Administrative Tools>Services). From the Services control
panel, the Fuse HQ Server is identified as Hyperic HQ Server and the
built-in database is identified as Hyperic HQ Database.
Note
If you are using something other than the built-in database for the
Fuse HQ Repository, be sure to start the database before starting
the Fuse HQ Server.
To start the Fuse HQ Server on non-Windows systems:
1. In a terminal window, open the ServerInstallDir/bin directory.
2. Run the following command:
./hq-server.sh start
The script displays some startup information on stdout, and then runs in
the background. The web-based component of the Fuse HQ Server displays
startup progress information until it is completely started. For detailed startup
information, see the following log file:
ServerInstallDir/logs/server.log
Fuse HQ Installing Fuse HQ Version 4.344
Starting and Stopping the Fuse HQ Server
To stop the Fuse HQ Server on non-Windows systems:
1. In a terminal window, open the ServerInstallDir/bin directory.
2. Run the following command:
./hq-server.sh stop
45Fuse HQ Installing Fuse HQ Version 4.3
Chapter 5. Running the Fuse HQ Server and the Fuse
HQ Agent
Starting and Stopping the Fuse HQ Agent
Installing the Fuse HQ Agent as
a Windows service
Starting the Agent on Windows
for the first time
Table 5.1. Configuration Settings for the Fuse HQ Agent
communications
Server port
7443
To install the Agent as a Windows service:
1. In a command prompt window, open the AgentInstallDir\bin directory.
2. Run the following command:
hq-agent.bat install
To start the Fuse HQ Agent for the first time on Windows:
1. In a command prompt window, open the AgentInstallDir\bin directory.
2. Run the following command:
hq-agent.bat start
Do not run hq-agent.bat by double-clicking on it in Windows Explorer.
When you start a Fuse HQ Agent for the first time, the startup process prompts
you for the configuration settings shown in Table 5.1.
The IP address of the system running the Fuse HQ Server.noneServer IP Address
If the Fuse HQAgent is on the same host as the Server, you can use
127.0.0.1 which allows communication on the loopback interface. If the
Server is running on a remote host you can run ping to get the IP address.
noSecure
Specify if HTTPS should be used for secure communications between Fuse
HQ Server and Agent. Saying no improves performance. Secure
communication is not always necessary (for example, when the Fuse HQ
Agent and Server are on a private network).
The port the Fuse HQ Agent uses to communicate with the Server.7080 or
If secure communication was specified, an HTTPS port (default 7443) must
be supplied. Otherwise, an HTTP port (default 7080) must be supplied.
DescriptionDefaultSetting
Fuse HQ Installing Fuse HQ Version 4.346
Agent IP Address
hqadminHQ login
Address
Starting and Stopping the Fuse HQ Agent
DescriptionDefaultSetting
The username of an HQ user. The default, hqadmin, is based on the
assumption that you used that username for the administrative account
when you configured the Fuse HQ Server. However, the hqadmin account
has permissions to create platforms, servers, and services on the Server.
For security reasons, you may want to use a more restrictive account.
The password for the specified username.noneHQ password
The IP address of the system running the Fuse HQ Agent.Detected IP
If the Fuse HQAgent is on the same host as the Server, you can use
127.0.0.1 which allows communication on the loopback interface.
If there is a firewall between the Fuse HQ Server and Agent, use the IP
address of the firewall. Note that the firewall must be configured to forward
Fuse HQ Agent traffic to the correct location.
Also note that IP addresses must be static for systems running a Fuse HQ
Server or an Agent. In Fuse HQ, IP addresses are referenced in configuration
files. If the IP address was dynamic and it changed, the configuration file
would not be updated to reference the new address.
The port the Fuse HQ Server uses to communicate with the Agent.2144Agent Port
Note that this port number is the value of the agent.setup.agentPort
configuration parameter, which is passed to the Server at startup and which
the Server will use to communicate with the Agent. However, there is another
configuration parameter, agent.listenPort, which is not passed to the
Server. It is the port that the Agent actually uses to receive communications.
By default, the value of agentPort is identical to the value of listenPort
(2144). So the Server is sending to the same port that the Agent is using
to receive.
You might set agentPort and listenPort to different values if a firewall
or proxy intervenes between the Server and Agent. In that case, the firewall
or proxy must be configured to receive messages on agentPort and forward
them to listenPort.
You can set these Fuse HQ Agent configuration parameters in the
agent.properties file, which is located in the Agent's installation directory.
An alternative to configuring each Agent during initial startup is to create and
copy an agent.properties file to each install location. See "Automatic
Fuse HQ Agent configuration" on page 48 for more information.
47Fuse HQ Installing Fuse HQ Version 4.3
Chapter 5. Running the Fuse HQ Server and the Fuse
HQ Agent
Stopping the Fuse HQ Agent on
Windows
Starting the Fuse HQ Agent on
non-Windows systems
Checking Agent status on a
non-Windows system
Stopping the Fuse HQ Agent on
non-Windows systems
Stopping (and starting) the Fuse HQ Agent can be managed from the Windows
Service Manager, where the service is registered under the name, Hyperic
HQ Agent.
To start the Fuse HQ Agent on a non-Windows system:
1. In a terminal window, open the AgentInstallDir/bin directory.
2. Run the following command:
./hq-agent.sh start
When you start a Fuse HQ Agent for the first time, the startup process prompts
you for the configuration settings shown in Table 5.1 on page 46.
When a Fuse HQ Agent is running, use the following command to display
status information:
./hq-agent.sh status
To stop the Fuse HQ Agent on a non-Windows system:
1. In a terminal window, open the AgentInstallDir/bin directory.
2. Run the following command:
Automatic Fuse HQ Agent
configuration
./hq-agent.sh stop
If you enter connection configuration information in an agent.properties
file before initial startup, the Fuse HQ Agent starts without prompting you for
the information. If you are installing multiple Agents, it is useful to have an
agent.properties file that you can copy and paste to each installation
directory. You will avoid entering the same information during every initial
startup.
On Windows systems, an agent.properties file is in the conf sub-directory
of the Fuse HQ Agent installation. On non-Windows systems, you might find
an agent.properties file in a ~/.hq directory.
Fuse HQ Installing Fuse HQ Version 4.348
Starting and Stopping the Fuse HQ Agent
The following shows the startup entries that you must edit, along with their
default values:
agent.setup.camIP=localhost
agent.setup.camPort=7080
agent.setup.camSSLPort=7443
agent.setup.camSecure=no
agent.setup.camLogin=hqadmin
agent.setup.camPword=hqadmin
agent.setup.agentIP=*default*
agent.setup.agentPort=*default*
49Fuse HQ Installing Fuse HQ Version 4.3
Fuse HQ Installing Fuse HQ Version 4.350
Chapter 6. Upgrading Fuse HQ
You can upgrade to a more recent version of Fuse HQ without losing data or configuration information.
Upgrading the Fuse HQ Server .................................................................................................. 52
Upgrading the Fuse HQ Agent ................................................................................................... 54
51Fuse HQ Installing Fuse HQ Version 4.3
Chapter 6. Upgrading Fuse HQ
Upgrading the Fuse HQ Server
Running the Fuse HQ Server
installer
When you run the Fuse HQ Server installer in upgrade mode, you install a
new Fuse HQ Server and use the configuration information from the previously
installed Server.
To upgrade the Fuse HQ Server, perform the following steps:
1. Stop the existing Fuse HQ Server if it is running.
See "Starting and stopping the Fuse HQ Server on Windows systems"
on page 44 or "Starting and stopping the Fuse HQ Server on
non-Windows systems" on page 44 for more information.
2. Back up the repository
This step is not necessary if you are using the built-in database. See
"Backing up the repository" on page 53 ) for more information.
3. Stop the database server for the repository.
4. Download and unpack the installation package.
See "Downloading a Fuse HQ Server Installation Package" on page 30
for more information.
5. Run the installer in upgrade mode.
On Windows, you run setup.bat -upgrade. On non-Windows systems,
you run setup.sh -upgrade.
6. When prompted by the installer enter the full pathname of the current
Fuse HQ Server and the location where the new Server should be
installed. Note that you should not install the new Server in the same
directory that contains the old Server.
7. Archive the old Fuse HQ Server directory (using tar or zip), in case you
need to revert to the older version.
Fuse HQ Installing Fuse HQ Version 4.352
Upgrading the Fuse HQ Server
After successfully completing the upgrade, you should be able to start the
repository and run the new Fuse HQ Server.
Backing up the repository You are not required to back up the repository if you are using the built-in
database. The installer automatically creates a copy of the built-in database
and places the copy in the new install location.
If the repository is not the built-in database, it will be upgraded in place .
Therefore, you should back up the database before the upgrade so you can
restore the repository from the backup.
Working around Oracle update
problem
If you are running an Oracle database as a repository, you may see one of the
following errors:
Error updating EAM_SERVICE.SERVICE_TYPE_ID:
java.sql.SQLException: ORA-02296: cannot enable (HQDBUSER.)
- null values found
Error executing statement desc=[null] SQL=[ ALTER TABLE
eam_stat_errors DROP CONSTRAINT rt_errs_fk_rstat CASCADE ]
java.sql.SQLException: ORA-02443: Cannot drop constraint nonexistent constraint
Do the following to fix the problem:
1. Restore the repository from the backup.
2. Run the following SQL command:
DELETE FROM EAM_SERVICE WHERE SERVICE_TYPE_ID IS NULL;
3. Re-run the upgrade.
53Fuse HQ Installing Fuse HQ Version 4.3
Chapter 6. Upgrading Fuse HQ
Upgrading the Fuse HQ Agent
Preserving configuration
information
Upgrade procedure To upgrade a Fuse HQ Agent:
You can use configuration parameters from the previous installation of the
Fuse HQ Agent, as long as you log in as the same user and the upgraded
Agent has the same install path.
Many configuration parameters are stored in an agent.properties file. You
can copy this file from your previous Fuse HQ Agent installation to use the
same configuration for your upgraded Agent. See "Automatic Fuse HQ Agent
configuration" on page 48 for more information.
In addition, if you are using custom plugins, you can use the
existing../hq-plugins directory (one up from the installation directory) to
preserve your plugins.
1. Stop the Fuse HQ Agent service. See "Stopping the Fuse HQ Agent on
Windows" on page 48 or "Stopping the Fuse HQ Agent on non-Windows
systems" on page 48.
2. On Windows platforms, uninstall the Agent service by running the
following command:
hq-agent.bat remove
3. Back up the agent.properties file from the previous Agent installation.
4. Download and unpack the Agent-only package into its installation
directory. See "Downloading a Fuse HQ Agent Installation Package"
on page 40 for more information..
5. Restore the backed up properties from the agent.properties file.
• If upgrading between 4.x releases, you can just over-write the existing
AgentInstallDir/conf/agent.properties file with the backed up
agent.properties file.
• If upgrading from a 3.x to a 4.x release, however, you must edit the
new AgentInstallDir/conf/agent.properties file and manually
copy property settings from the backed up agent.properties file
Fuse HQ Installing Fuse HQ Version 4.354
Upgrading the Fuse HQ Agent
(this is because the 4.x agent.properties file contains some
properties not present in the older version).
6. On Windows, install the new Agent service by running the following
command:
hq-agent.bat install
7. Start the new Agent. See "Starting and Stopping the Fuse HQ Agent"
on page 46 for more information.
55Fuse HQ Installing Fuse HQ Version 4.3
Fuse HQ Installing Fuse HQ Version 4.356
Chapter 7. Uninstalling Fuse HQ Components
Uninstalling the Fuse HQ Server ................................................................................................ 58
Uninstalling a Fuse HQ Agent ................................................................................................... 59
57Fuse HQ Installing Fuse HQ Version 4.3
Chapter 7. Uninstalling Fuse HQ Components
Uninstalling the Fuse HQ Server
Removing the Fuse HQ Server
Windows service
Uninstalling To uninstall Fuse HQ Server, simply stop the running server process and
To remove the Fuse HQ Server service in Windows:
1. In a command prompt window, open the ServerInstallDir\bin
directory.
2. Run the following command:
hq-server.exe -u
delete the Fuse HQ Server directory on your hard drive.
Fuse HQ Installing Fuse HQ Version 4.358
Uninstalling a Fuse HQ Agent
Uninstalling a Fuse HQ Agent
Removing the agent Windows
service
Uninstalling To uninstall a Fuse HQ agent, simply stop the running agent process and
To remove the Fuse HQ agent service in Windows:
1. In a command prompt window, open the AgentInstallDir\bin directory.
2. Run the following command:
hq-agent.bat remove
delete the Fuse HQ agent directory on the host machine.
59Fuse HQ Installing Fuse HQ Version 4.3
Fuse HQ Installing Fuse HQ Version 4.360
Loading...