Installing Fuse HQ

Install Oracle on the machine you will use following the Oracle installtion instructions.

Using Oracle Database Configuration Assistant, create a new database.

Create the TEMP_HQDB temporary tablespace making it 2 GB in size.

Create the TS_HQDB tablespace making it 25 GB in size.

Log into the Oracle instance with SQL*Plus as the system user.

Use CREATE USER to create a user name and password.

SQL> CREATE USER HQUSER IDENTIFIED BY HQPASSWORD;

Replace HQUSER and HQPASSWORD with your own values.

Use GRANT to give the new user permissions for accessing the database.

SQL> GRANT CONNECT, RESOURCE, CREATE VIEW TO HQUSER;

Replace HQUSER with the user's name.

Verify the permission setting:

SQL> SELECT GRANTED_ROLE, DEFAULT_ROLE FROM dba_role_privs WHERE grantee = 'HQUSER';

Make sure that you see the following rows for CONNECT and RESOURCE roles:

GRANTED_ROLE DEFAULT_ROLE
CONNECT YES
RESOURCE YES

If that is not the case, update the permissions:

ALTER USER HQUSER DEFAULT ROLE RESOURCE, CONNECT;

Go to http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html.

In the JDBC Driver Downloads section, select the link for your version of Oracle.

On the drivers download page, select the driver for your JDK version.

	Note
	JDeveloper 11g JDBC drivers support JDBC 4.0 features. Use ojdbc6.jar with JDK 6.0 for JDBC 4.0 features.

On the page that appears accept the licensing agreement.

Download the jar file.

Copy the driver jar file to hyperic-hq-installer/installer-4.x.y/lib.

Log into PostgreSQL interactive shell as a user with administrative privileges.

Create a user with permission to log in and create databases.

create role admin with login createdb password 'hqadmin';

Replace admin and hqadmin with your own values.

Create the database that you will use as the Fuse HQ repository and specify admin as the owner.

create database "HQ" owner admin;

	Note
	The quotes around "HQ" cause the database name to be in uppercase.

Exit the PostgreSQL shell.

In the PostgreSQL configuration file, postgreInstall/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.

Add these lines to postgreInstall/data/pg_hba.conf, the Host-base Authentication (HBA) file:

TYPE    DATABASE  USER  CIDR-ADDRESS    METHOD
local   all       all                   ident sameuser  
host    all       all   HQ Server IP address/32  password

See the PostgreSQL 8.2.12 Documentation for more information.

In the postgresql.conf file, edit or add the following parameters:

fsync=false
shared_buffers=10000
work_mem=2048
statement_timeout=30000

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

Although database monitoring is not required, it is recommended.

Connect to a MySQL server as root.

The mysql> prompt will appear.

Create a user called hqadmin.

mysql> create user 'hqadmin'@'localhost' identified by 'passwd';

Create a database called HQ.

mysql> create database HQ;

Grant the hqadmin user full access to the HQ database.

mysql> grant all on HQ.* to 'hqadmin'@'localhost';

Enable the full query log.

[mysqld]
log-error = /home/mysql/log/mysqld.err
log = /home/mysql/log/mysql_general.log

Every query (even ones with incorrect syntax) that the database server receives will be 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.

Print warnings to the error log file.

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.

Configure buffer pool size.

innodb_buffer_pool_size = 256M

The size of the MySQL buffer pool is has a significant impact on MySQL performance. If your database is on a dedicated machine, make the buffer pool about 80% of total memory.

Configure the frequency with which the log buffer is written to the log, and the log is flushed to the disk.

innodb_flush_log_at_trx_commit = 2
innodb_log_buffer_size = 64M
innodb_log_file_size = 256M

Setting this value to 0 dramatically increases MySQL performance, but with this setting, you are likely to lose data in the event of a server crash. If loss of data is unacceptable, use a value of 2 instead. We do not recommend setting the value to 1.

Configure innodb as the default storage engine.

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

Configure the sort buffer size.

sort_buffer_size = 64K

MySQL recommends a sort_buffer_size larger than 64K.

An article on experimenting with sort buffer size is available at http://www.mysqlperformanceblog.com/2007/08/18/how-fast-can-you-sort-data-with-mysql.

Configure the read buffer size.

read_buffer_size = 1M
read_rnd_buffer_size = 10M
table_cache = 2048
set-variable = max_connections=400
key_buffer_size = 256M
thread_cache_size = 32

Because Fuse HQ does a significant volume of sequential reads, a large read buffer improve performance.

Configure the number of threads that can run in the InnoDB kernel.

innodb_thread_concurrency = 8

A starting point for setting this value is to to set a value equal to twice the number of CPUs times the number of disks.

Set the method that is used to flush data and log files.

innodb_flush_method=O_DIRECT
innodb_rollback_on_timeout=1

For battery-backed-up storage with write-back cache mode on Linux, the O_DIRECT flush method is good.

Set the size of the query cache.

query_cache_size = 0

Generally, the higher this value, the better the performance. However, in MySQL versions older than 5.0.50, beware of setting this variable too high, as it may cause the database to pause. For more information, see the bug description at http://bugs.mysql.com/bug.php?id=21074.

Set the query cache limit.

The default value here is 1M. If the qcache_hits-to-qcache_inserts ratio is low, raise this value.

query_cache_limit = 8M

Set the character encoding to utf-8.

default-character-set=utf8
collation_server=utf8_bin

unpack the Fuse HQ download.

Open a command shell.

Navigate to the fusehq-installer directory.

Run setup.

For example, the following command would start the installer in full install mode:

setup -full

Read the HQ Clickwrap License Agreement.

Accept the terms of the agreement.

Read the VMWare License Agreement.

Accept the terms of the agreement.

Select the components you want to install.

Specify the installation path.

Complete the installation process.

In a command prompt window, open the ServerInstallDir\bin directory.

Run the following command:

hq-server.exe -i

In a terminal window, open the ServerInstallDir/bin directory.

Run the following command:

./hq-server.sh start

In a terminal window, open the ServerInstallDir/bin directory.

Run the following command:

./hq-server.sh stop

In a command prompt window, open the AgentInstallDir\bin directory.

Run the following command:

hq-agent.bat install

In a command prompt window, open the AgentInstallDir\bin directory.

Run the following command:

hq-agent.bat start

In a terminal window, open the AgentInstallDir/bin directory.

Run the following command:

./hq-agent.sh start

In a terminal window, open the AgentInstallDir/bin directory.

Run the following command:

./hq-agent.sh stop

Stop the existing Fuse HQ Server if it is running.

See Starting and stopping the Fuse HQ Server on Windows systems or Starting and stopping the Fuse HQ Server on non-Windows systems for more information.

Back up the repository

This step is not necessary if you are using the built-in database. See Backing up the repository ) for more information.

Stop the database server for the repository.

Download and unpack the installation package.

See Downloading a Fuse HQ Server Installation Package for more information.

Run the installer in upgrade mode.

On Windows, you run setup.bat -upgrade. On non-Windows systems, you run setup.sh -upgrade.

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.

Archive the old Fuse HQ Server directory (using tar or zip), in case you need to revert to the older version.

Restore the repository from the backup.

Run the following SQL command:

DELETE FROM EAM_SERVICE WHERE SERVICE_TYPE_ID IS NULL;

Re-run the upgrade.

Stop the Fuse HQ Agent service. See Stopping the Fuse HQ Agent on Windows or Stopping the Fuse HQ Agent on non-Windows systems.

On Windows platforms, uninstall the Agent service by running the following command:

hq-agent.bat remove

Back up the agent.properties file from the previous Agent installation.

Download and unpack the Agent-only package into its installation directory. See Downloading a Fuse HQ Agent Installation Package for more information..

Restore the backed up properties from the agent.properties file.

On Windows, install the new Agent service by running the following command:

hq-agent.bat install

Start the new Agent. See Starting and Stopping the Fuse HQ Agent for more information.

In a command prompt window, open the ServerInstallDir\bin directory.

Run the following command:

hq-server.exe -u

In a command prompt window, open the AgentInstallDir\bin directory.

Run the following command:

hq-agent.bat remove