Page tree

Use this topic to understand planning of a single-server deployment of the product.

In this type of deployment one instance of the product can handle the entire process of collecting data, indexing it, and finally making it available for search. Single-server deployments can be useful for nonproduction, small, and medium setups. Such a deployment enables simpler management of resources compared to multiple-server deployments. For more information, see Recommendations.

Related topics

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:

ItemDescription

Additional information

ITDA Server

BMC TrueSight IT Data Analytics server, a combination of the following components:

  • Console Server
  • Search

Managing components

Configuration DBConfiguration Database component

Managing components

BPPM

BMC ProactiveNet Performance Management

Integrating with BMC ProactiveNet Performance Management

BPPM CellBMC ProactiveNet Performance Management cells

Integrating with BMC ProactiveNet Performance Management cells

SMTP

Simple Mail Transfer Protocol

Setting up emails

Collection Data Sources

Data sources (such as log files and Windows events) for monitoring using Collection Station or Collection Agents

Agent types

PortsPort numbers used for communicating between components and external systemsCommunication 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.

Where to go from here

To perform a single-server deployment, you need to install the product. For more information, see Installing in a single-server environment.