Prepare Your Server Hardware

Your CA UIM environment can contain several different pieces of server hardware:
uim835
Your CA UIM environment can contain several different pieces of server hardware:
  • Database Server:
    The Database Server is the location of the UIM database. QoS data and other required system information is written to the database server.
  • Primary Hub Server:
     The Primary Hub Server is the location of robot that controls the UIM primary hub.
  • Secondary Hub Servers (Optional)
    : Your UIM environment can also have extra servers for load-balancing and failover capability.
  • Unified Management Portal (UMP) Server (Optional): 
    CA UIM features a Unified Management Portal (UMP) that presents the performance and availability data CA UIM collects. The UMP server contains all of the probes that are required for basic UMP functionality.
    If you have a small environment to monitor, you can install UMP on the Primary Hub Server.
This article details the deployment guidelines and hardware requirements for each component in your CA UIM environment.
Contents
Hardware Overview
For the best CA UIM performance, the physical or virtual servers that host your primary components must have:
  • Processing power and memory that are sufficient for the size of your deployment
  • Supported software that is installed and configured
Assessing the hardware requirements for any large and complex software system is a challenge. Over-sizing seems wasteful, but underestimating can create performance problems. Because each environment is unique, no fixed rules or formulas can ensure a minimum optimal configuration. Consider the following items:
  • Keep in mind that a hardware configuration that works today can require growth in the future. Take forecast growth into consideration when planning your hardware requirements.
  • Use the information in this article to begin planning your deployment. However, your situation can impose greater or lesser demands on the system.
  • If possible, obtain hardware of the most current generation to anticipate the longest useful life.
  • Consult your presales consultant if you have any doubts or concerns about your hardware needs.
  • For evaluations, you can install the database, CA UIM Server, and UMP on a single system. For production environments, distribute them across multiple virtual or physical servers. A distributed deployment gives each component sufficient computing power and memory to perform optimally.
  • If you are installing any components on a VMware ESX Server, review the Enterprise Java Applications on VMware -- Best Practices Guide.
While every situation is unique, the following deployment size categories give you a starting point for assessing your hardware requirements:
Example Use Case
Deployment Size
Recommended Number of Hubs
Recommended Number of Robots
A proof-of-concept for a small business
Small
1
100 or less
A small government agency
Medium
Up to 5
250 or less
A medium-sized company
Large
Up to 20
500 or less
A large company
Major
Up to 50
1000 or less
If you require a deployment with over 50 hubs and 1000 robots, consult CA professional services or a CA UIM certified partner.
Database Server Requirements
Minimum processor:
64-bit XEON-class, 2.0 GHz
Deployment size
Processor
Memory
Small
One dual-core
8 GB
Medium
One or two quad-cores
12 GB
Large
Two quad-cores
12 GB to 18 GB
Major
Two quad-cores or eight-cores
18 GB to 24 GB
Storage recommendations:
  • Obtain at least 1-TB storage for the database.
  • Use RAID 10 (for speed and reliability).
  • Spread database files across multiple disks to improve I/O.
  • Choose drive subsystems with low latency/seek times, high spindle speeds, high interconnect bandwidth.
  • Consider data redundancy, synchronization, and database growth.
Disk I/O performance and server bus bandwidth impact relational database server performance. Crowded VM hosts, clusters, or heavily shared storage in VM environments are not recommended for hosting the database. Selecting the right database storage solution is beyond the scope of this article. Consult your storage vendor if you need further assistance.
Primary Hub Server Requirements
Minimum processor:
64-bit XEON-class, 2.0 GHz
Deployment size
Processor
Memory
Small
One dual-core
4 GB to 8 GB
Medium
One or two quad-cores
12 GB
Large
Two quad-cores
12 GB
Major
 Two quad-cores or eight-cores
16 GB to 24 GB
On all systems:
  • 15-GB available disk space is recommended.
  • The installer requires 2.1 GB of temporary space to unpack the files.
On Linux and Solaris, the installer unpacks to /tmp/install.dir.
x
, where
x
is a random number. If /tmp does not have 2.1 GB available, the installer uses the home directory of the user running the installer (root).
Secondary Hub Server Requirements
The requirements for a secondary hub vary, depending on the load the hub carries. Consider the following items:
  • A secondary hub requires hardware equal to that of your primary hub if: 
    • It manages a large number of robots
    • It is configured for high availability and must take over the role of the primary hub.
  • If the secondary hub manages a small number of robots (for example, for a remote subnet with limited components to monitor), less powerful hardware can be used.
UMP Server Requirements
Minimum processor:
64-bit XEON-class, 2.0 GHz
Deployment
Processor
Memory
Small
Not required. Install UMP on the primary hub server.
Medium
One quad-core
4 GB to 8 GB
Large
Two quad-cores
8 GB to 12 GB
Major
Two quad-cores
16 GB