Pre-installation Planning

Proper configuration of the host computers and database ensures a successful installation. Before you install CA UIM: 
uim82
Proper configuration of the host computers and database ensures a successful installation. Before you install CA UIM: 
  • Determine where to install CA UIM components
  • Account for database performance
  • Allocate sufficient hardware
  • Verify that you meet the operating system and database prerequisites
Pre-installation information for each supported operating system/database pairing is organized into its own particular section. Refer to the section that applies to your choice of OS and database. 
  • Microsoft Windows and MS-SQL Server
  • Microsoft Windows and MySQL Server
  • Microsoft Windows and Oracle
  • Linux and MySQL Server
  • Linux and Oracle
  • Solaris and MySQL Server
  • Solaris and Oracle
Contents
Planning Considerations
You need to make two decisions about distributing CA UIM components: where to install the primary components and where to install the hubs
The CA UIM solution has three primary components:
  • CA UIM Server, which contains (and is often referred to as) the primary hub
  • The UIM database
  • Unified Management Portal (UMP)
When installing for an evaluation environment, you can install everything on a single system. However, for production environments, we recommend that you distribute these components across multiple virtual or physical servers. Using multiple systems gives each component sufficient computing power and memory to perform optimally. 
The size of your deployment determines how you distribute each component. For a definition of small, medium, and large deployments, refer to Hardware Recommendations. 
The optional UMP DMZ proxy server component must be installed on an additional system.
Hubs are deployed depending on the overall size of the managed environment and the number of sub-domains into which the environment is divided. 
  • You can install two hubs on the same domain. Two hubs provide replication for user and security data (user definitions and ACLs). 
  • CA UIM also provides a High Availability probe to provide hub failover capability. The High Availability probe ensures that the CA UIM infrastructure can forward alarm and quality of service (QoS) information to the secondary hub. When the primary hub is again available, fail-back synchronizes the two hubs, ensuring your management data history remains intact. 
Required Ports
The ports that are required for a successful infrastructure installation depend on how hubs are set up. If we assume the default first port of 48000 is used, port assignments are as follows:
  • Single-hub infrastructure or multiple-hub infrastructure that does NOT use tunnels:
    • 48000
      for robot controller probe
    • 48001
      for robot spooler probe
    • 48002
      to allow robot-to-hub and manager-to-hub communications
    • A port for each probe you install; these ports start at
      48004
      and are assigned to each probe as the probe is activated
  • Multiple-hub infrastructure that uses tunnels that are NOT SLL tunnels:
    • All ports that are used in a single-hub installation
    • 48003
      for the tunnel server (can also be set to 443)
  • Multiple-hub infrastructure that uses SSL tunnels:
    • 48000
      (controller) and
      48002
      (hub)
    • 48003
      to allow the tunnel client to access the tunnel server
    • 8443
      and
      8080
      (service_host) to allow the tunnel client to access Admin Console and CA UIM web page
  • The udm_manager probe uses port 
    4334
     by default to communicate with udm clients (datomic peers).
  • The snmpcollector probe uses port 
    161
     by default to communicate with the SNMP port on a device.
  • The automated_deployment engine probe uses port 
    22 
    to deploy robots using ssh file transfer to the target system.
Database Performance Requirements
Your disk input/output (I/O) performance and server bus bandwidth impacts relational database server performance. Crowded VM hosts, clusters, or heavily shared storage in VM environments are not recommended for hosting the UIM database.
We recommend that you:
  • Start with at least 1 TB of storage for the UIM database
  • Use RAID 10 for speed and reliability
  • Consider spreading the database files across multiple disks to improve I/O performance
  • Choose drive subsystems with low latency and seek times, high spindle speeds, and high interconnect bandwidth
  • Consider data redundancy and synchronization on an on-going basis, accounting for the growth of the database
Selecting the right database storage solution is beyond the scope of this document. We recommend discussing storage requirements with your storage vendor or consultant.
Hardware Considerations
While every situation is unique, the following deployment size categories give you a starting point for assessing your hardware requirements:
  • Small
    (One hub, fewer than 100 robots)
    - Modest deployment, such as a proof-of-concept for a small business
  • Medium
    (Up to five hubs, fewer than 250 robots
    )
    - Medium-scale deployment, such as a small government agency
  • Large
    (Up to twenty hubs, fewer than 500 robots)
  • Major
    (Up to fifty hubs, fewer than 1000 robots)
  • Over 50 hubs or over 1000 robots
    - Consult with CA professional services or a CA UIM certified partner.
See Obtain Sufficient Hardware for specific hardware requirements.