Foglight for DB2 (Cartridge) 5.9.3.20 - Deployment Guide

Deployment pre-requisites

Welcome to the Foglight for Databases Deployment Guide. This guide provides the pre-requisites for optimal deployment, to ensure the best user experience possible.

This section describes important deployment information required to monitor the leading RDBMS: Oracle®, SQL Server®, Sybase®, and DB2 for LUW. The information in this guide applies to all 5.7.5.x and 5.9.3.10 releases.

Architecture

There are three main components:

NOTE: The product components can be either distributed over different machines — preferable in large or growing environments — or centralized.

Hardware requirements

Identify your hardware requirements, which are determined by whether SQL PI is configured and by the number of monitoring agents.

NOTE: The Numbers of agent refers to DB agents. The IC agents resources are calculated within the DB agents. Sizing requirements are exclusively for Foglight components and these resources should not compete with any other resources required for the OS or applications installed on the same system.

SQL PI configured

SQL PI is available only for Oracle, SQL Server and SQL Server BI (Analysis services). These tables define the Hardware requirements for each server based on the number of monitoring agents

After locating your hardware requirements in the tables, ensure that you complete the manual JVM Setting configuration as described in:

CPUs (2.4GHz)* — for a virtual machine the CPU allocation must be reserved. The reservation is expressed in MHz

RAM*- for a virtual machine the memory allocation must be reserved.

IMPORTANT: If you are monitoring more than 70 agent running on Windows system, the monitored hosts should be configured to use WinRM. Monitoring Analysis services is supported only on Agent Managers running on Windows which must have a version of .NET 3.5 installed. One PI repository can only be attached by at most three Foglight Agent Managers at a time.

CPUs (2.4GHz)* — for a virtual machine the CPU allocation must be reserved. The reservation is expressed in MHz.

RAM*- for a virtual machine the memory allocation must be reserved.

WARNING: Linux® is the recommended platform for both Oracle and SQL Server monitoring. Exclude the SQL PI repository directory (named Infobright™) from real-time scanning (for example, Antivirus software). For a virtual machine the CPU and memory allocations must be reserved. Recommended configuration would be a separate FMS and fglAM where PI repository resides on and a separate fgIAM where DB Agents resides on the different host machine.

CPUs (2.4GHz)* — for a virtual machine the CPU allocation must be reserved. The reservation is expressed in MHz

RAM*- for a virtual machine the memory allocation must be reserved.