Deploying multiple Collection Stations and Indexers

In large setups, with growing needs for indexing large volumes of data, the Collection Station and Indexer (and sometimes Search) might need to be deployed and scaled on separate servers. In these setups, you can separate the collection and indexing functions of the product. You can either deploy the Collection Station on one server and the Indexer on server host, or you can deploy both the Collection Station and Indexer on the same server. As you scale, you can continue adding these components on additional servers. For more information about when to scale, see Indicators for scaling.

When you scale Indexers, you need to provide details of the master Indexer installed on the primary node. Data collected and searched is distributed across all the Indexers available. For more information about how Indexers function in a multiple-server deployment, see Indexer redundancy.

This topic contains the following information:

Related topics

Deploying multiple Search components

Agent types

Sizing and scalability considerations

Deployment diagram

The following diagram illustrates the scale-out architecture for Collection Stations and Indexers.

Note

The following diagram shows the Collection Station and Indexer components deployed on the same server. Depending on your environment, you can either scale these components together on the same server or on separate servers.

 Click to view table of abbreviations used in the diagram

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

ItemDescription

Additional information

ITDA Server

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

  • Console Server
  • Search

Viewing component status and associated properties

Remedy Single Sign-On

User-authentication mechanism necessary for integrating with TrueSight Presentation Server.

Deploying IT Data Analytics with Remedy Single Sign-On
Configuration DBConfiguration Database component

Viewing component status and associated properties

PNet/TSIM

ProactiveNet or TrueSight Infrastructure Management.

Integrating with Infrastructure Management and ProactiveNet

PNet/TSIM Cell

ProactiveNet or TrueSight Infrastructure Management remote cells.

Integrating with Infrastructure Management and ProactiveNet cells

TSPS

TrueSight Presentation Server

Integrating with TrueSight Presentation Server

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
TLS 1.2

TLS 1.2 is supported on all the communication channels marked in green. In some cases, TLS needs to be manually configured.

TLS considerations for IT Data Analytics

Where to go from here

To deploy multiple Collection Stations and Indexers, you need to first install them. For more information, see Installing in a multiple-server environment.

If you initially installed the product by performing a typical installation and want to scale the product on additional servers, then you need to make certain configuration changes. For more information, see. Configurations required before scaling up

(Optional) You might want to move data collectors from one Collection Agent (or Collection Station) to another. For more information, see movecollectors CLI command

Was this page helpful? Yes No Submitting... Thank you

Comments