Architecture
This topic describes the product architecture and data flow. BMC Helix Capacity Optimization includes both the cloud and on-premises components. Some components of the architecture are mandatory, while others are optional, depending on how you want to collect data from your on-premises environment.
To view example configurations for the on-premises components and how they interact with BMC Helix Capacity Optimization, see Planning for data collection in the on-premises environment.
The following table provides information about each of the core functional components.
Component | Details |
|---|---|
Cloud components | |
Helix Single Sign-On | Tenant administrators use the Helix Single Sign-On (SSO) Admin console for setting up users and user groups. |
Helix Capacity Optimization Dashboard | You can access the capacity views, Investigate tool, and Cloud Cost Control from the Helix Capacity Optimization Dashboard. Access to this component is enabled through integrated system authentication with Single Sign-On. |
Helix Capacity Optimization Console | You can accomplish most of your capacity planning and administrative activities from the Helix Capacity Optimization Console. Access to this component is enabled through integrated system authentication with Single Sign-On. |
| Cloud ETL Engine | The Cloud ETL Engine, preconfigured in Helix, is required for collecting data from the resources of public cloud providers, such as AWS, Azure, and GCP. It supports all data integration tasks by using connectors that consist of extract, transform, and load (ETL) procedures. |
On-premises components | |
Remote ETL Engine | The Remote ETL Engine is required for collecting data from on-premises data center. It supports all data integration tasks by using connectors that consist of extract, transform, and load (ETL) procedures. |
BMC Helix Client Gateway | BMC Helix Client Gateway is a non-VPN solution and is required to securely connect to your BMC Helix services. For details, see
BMC Helix Client Gateway connectivity
|
Gateway Server | The Gateway Server is required for Agent-based operating system data collection from managed nodes. The Gateway Server supports all the commonly used UNIX operating system platforms. One Gateway Server can collect data from many managed nodes. You can schedule and create daily automation runs and list of nodes by using Gateway Manager. For more details, see Planning for data collection in the on-premises environment. |
Capacity Agents | The Capacity Agents provide lightweight, fault-tolerant data collection capabilities for managed computers running UNIX and Windows. You must install the Capacity Agents with a Gateway Server, and vice versa. One Capacity Agent is installed on each managed machine running UNIX or Windows. Agents transfer the collected data to the Gateway Server. This data is processed on the Gateway Server and then imported into BMC Helix Capacity Optimization. For the complete list of supported operating systems, see System requirements for the Capacity Agent. |
Comments
There is no description of the Cloud ETL Engine within the text above.
Thank you, Brandon!
I have added the description for the Cloud ETL Engine now.
Regards,
Manisha
Log in or register to comment.