This topic provides information about a single-server deployment.
BMC recommends this type of deployment when your deployment scaling and sizing requirements do not exceed the limits of a single server. This type of deployment enables simpler management of resources compared to multiple-server deployments.
Deployment diagram
The following diagram illustrates a high-level architecture for a single-server deployment:
The following table lists definitions of abbreviations and terminology used in the preceding diagram:
| Item | Description | Additional information |
|---|---|---|
| ITDA Server | BMC TrueSight IT Data Analytics server, a combination of the following components:
| |
| Configuration DB | Configuration Database component | |
| BPPM | BMC ProactiveNet Performance Management | |
| BPPM Cell | BMC ProactiveNet Performance Management cells | Integrating with BMC ProactiveNet Performance Management cells |
| SMTP | Simple Mail Transfer Protocol | |
| Collection Data Sources | Data sources (such as log files and Windows events) for monitoring using Collection Station or Collection Agents | |
| Ports | Port numbers used for communicating between components and external systems | Communication ports and protocols |
Recommendations
BMC recommends this type of deployment in the following scenarios:
- A single-server host (or virtual machine) is sufficient to handle the data volume and user load. For more information, see Hardware sizing recommendations.
- All product data is to be administered by the same team.
Related topic
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks