Single-server deployment

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

Where to find more information

Sizing-and-scalability-considerations

Agent-types

Multiple-server-deployment 

Deployment diagram

The following diagram illustrates a high-level architecture for a single-server deployment:

ITDA Single Server Architecture_PN_June5.png

Click to view table of abbreviations used in the diagram

The following table lists definitions of abbreviations and terminology used in the preceding diagram:

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.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*