Common Configurations - syncsort_capacity_management - Latest

Syncsort™ Capacity Management Guide

Product type
Software
Portfolio
Integrate
Product family
Syncsort™ Software
Product
Syncsort™ Capacity Management
Version
Latest
Language
English
Product name
Syncsort™ Capacity Management
Title
Syncsort™ Capacity Management Guide
Copyright
2024
First publish date
1985
Last edition
2024-08-06
Last publish date
2024-08-06T15:42:28.602035

This section presents example configurations that you can use to implement a Syncsort™ Capacity Management configuration of differing sizes. Production con­figurations often differ somewhat from those described in this section, as each deployment must change to accommodate the following requirements:

  • Ingested data types
  • Data processing volume per data type
  • Data collection Frequency
 You can co-locate components if the size of the environment is sufficient to collect and process the volume of data required. For any production install, we recommend performing a sizing exercise to determine the hardware requirements and, if required, our Professional Services team can assist with this exercise.
Note:
  • Former terms for "Capacity Database" in Syncsort™ Capacity Management or Athene are "Capacity Management Information System" (or "CMIS") and "Performance Database" (or "PDB"). For this release "Capacity Database" also refers to any references in the product to "CMIS" and "PDB".

  • In each of these examples, users access Desktop applications (including the Control Center administration tool, known as System Manager) by connecting via RDP to one of the machines with a full set of Core software is installed. However, you can install the Desktop applications separately to manage the Control Center without RDP access. To use Desktop tools from a machine without Control Center installed, users need the same permissions as the Control Center Service user.

  • In larger configurations, the License Server only needs to be located on one of the Core machines but is not shown separately in the diagrams.

  • In an extra-large configuration, you can distribute the databases across any number of SQL Servers. Using a single SQL Server requires sufficient machine resources to support greater processing volume than other deployments.