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 test and small setups. Such a deployment enables simpler management of resources compared to multiple-server deployments. For more information, see Recommendations.
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:
TrueSight IT Data Analytics server, a combination of the following components:
|Remedy Single Sign-On|
User-authentication mechanism necessary for integrating with TrueSight Presentation Server
|Deploying IT Data Analytics with Remedy Single Sign-On|
|Configuration DB||Configuration Database component|
ProactiveNet or TrueSight Infrastructure Management
ProactiveNet or TrueSight Infrastructure Management remote cells
TrueSight Presentation Server
|Integrating with TrueSight Presentation Server|
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|
TLS 1.2 is supported on all the communication channels marked in green. In some cases, TLS needs to be manually configured.
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 Sizing and scalability considerations.
- 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.