This topic provides an overview of the functional architecture of TrueSight Capacity Optimization. Some components of the architecture are mandatory, while others are optional, depending on the specific deployment scenarios or use cases to be supported. 

Basic functional architecture

The following illustration depicts the basic functional architecture of TrueSight Capacity Optimization. The table that follows the diagram provides additional information about each of the core functional components.


You can download this presentation and view it as a slide show for an interactive experience.

Capacity Agents ≥ 0

The Capacity Agents provide lightweight, fault-tolerant data collection capabilities for managed computers running UNIX and Windows. You must install the Capacity Agents with a Gateway Server, and vice versa.

For the complete list of supported operating systems, see Capacity Agents in Software requirements.

If you do not use the Gateway Server and Capacity Agents to collect operating system data, then you must configure ETLs to collect this data.

Gateway Server≥ 0

The Gateway Server is required for Agent-based or Agent-based operating system data collection from managed nodes. The Gateway Server supports all the commonly used UNIX and Windows operating system platforms.

For more information, see Capacity Agents.

One Gateway Server can collect data from many managed nodes.

For details and applicable constraints, see Sizing and scalability considerations

If you do not use the Gateway Server and Capacity Agents to collect operating system data, then you must configure ETLs to collect this data.

Database Server1

This server can be either a supported Oracle server or a supported PostgreSQL database server. One Database Server is required for each TrueSight Capacity Optimization instance. The database can be implemented on a cluster of computers where supported, however, such an implementation is also considered as a single database.

ETL Engine Server≥ 1

This server is required for collecting data from third-party data sources or from the Gateway Server. In a demo or proof-of-concept environment, you can run the ETL Engine software components on the Application Server computer. Each ETL Engine Server must have access to the database server, unless it is deployed as a Remote ETL Engine Server.

For more information, see Guidelines for using a remote ETL engine.
Application Server≥ 1

Each Application Server runs several software components. Each Application Server must have access to the database server. If there is more than one Application Server computer, each computer must have access to a single shared network file system, called the repository.

Presentation Server1

You can access the Capacity Views and the Investigate tool from the TrueSight console, which is hosted on the TrueSight Presentation Server. Access to this component is enabled through integrated system authentication with Remedy Single Sign-On.

Remedy SSO Server


System administrators use the Remedy Single Sign-On (SSO) Admin console to manage users and user groups. You must install Remedy Single Sign-On before you install the TrueSight Presentation Server.

For more information, see Configuring user authentication.

Best Practice

In development, test, and production environments, do not install the TrueSight Presentation Server or a combination of the TrueSight Presentation Server and the Remedy SSO Server on the same computer on which the Application Server is installed.

In a production environment, ensure that you install each of the server components (including the Presentation Server and the Remedy SSO Server) on separate computers.

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