Application Server
The TrueSight Capacity Optimization Application Server hosts the TrueSight Capacity Optimization console. It runs several software components.
The Application Server has the following components:
- Data Hub: Provides TrueSight Capacity Optimization core services and supports data warehousing and data exchange activities (there can be only one instance of this type of Application Server).
- Primary Scheduler: Provides scheduling capabilities for maintenance and reporting systems tasks. You must have at least one Primary Scheduler. Also, all schedulers of type Primary must be able to interact with the shared repository, and can execute System tasks like Report Executor and Optimizer tasks.
- Web Application: Provides support for TrueSight Capacity Optimization presentation layer, that is the TrueSight Capacity Optimization console (there can be one or more of this type of Application Server)
- Service Container: Provides an additional container to run core services that have been relocated from the Data Hub.
- Dynservices: Provides backend services that can be scaled across all Application Server computers.
- Repository Folder: Provides a file system directory shared between all the Application Server computers, which contains artifacts like reports and charts produced by the Primary Scheduler and the Web Application.
The Application Server performs the following functions:
- Provides the communication bus for all other TrueSight Capacity Optimization components
- Supports all analytical, modeling, and reporting tasks
- Provides the primary scheduler for running TrueSight Capacity Optimization system tasks and connectors
- Supports the administration activities from the TrueSight Capacity Optimization console
The following capabilities and constraints apply to the Application Server:
- Multiple Application Server computers can be deployed in a TrueSight Capacity Optimization instance.
- You must run the TrueSight Capacity Optimization installation on each Application Server computer.
- You can select a subset of Application Server components in the installer’s custom screen.
- One Application Server computer can have only one Application Server component of each type.
For example, you cannot have two web server components on the same Application Server computer. - Most of the components can be replicated for scale-out, one on each Application Server computer. The only exception is the Data Hub, which cannot be replicated.
Consider the points in the following table before deploying the Application Server.
Component | Function | Deployment notes for multiple Application Server computers | Selection in installer |
|---|---|---|---|
Apache web server | Web server | Can be replicated and placed behind a load balancer to scale out automatically. | Web server |
Web application | All functions accessible through UI. | Can be replicated together with the Web server. | Web server |
Primary scheduler | Runs scheduled backend tasks. | Can be replicated to scale out manually. | Primary scheduler |
Data Hub | Runs data warehouse (DWH) service and backend services. Some backend services that run in the Data Hub component are relocatable, that is, they can run either in the Data Hub or in a Service Container. Whether or not to relocate services is a decision that must be made based on the expected workload for particular services. For more information about relocation guidelines, see Guidelines for relocating backend services to Service Containers. | Cannot be replicated. Exactly one Data Hub is required in any TrueSight Capacity Optimization installation. | Data Hub |
Dynservices | Runs the following dynamic services: Optimizer, Cost Prices, Cost Forecasting, Registry. The dynamic services for Cost Prices and Cost Forecasting are active only if TrueSight Cloud Cost Control is installed. | Can be replicated to scale out manually. | No selection on installer. When you install an Application Server component, Dynservices gets installed. The Registry dynamic service is installed only on the primary Application Server. |
Service Container | Runs backend services. You can use this component to isolate backend services and improve their resilience and workload balancing. Typically, it runs relocatable backend services (for example, Data API) that have been moved from the Data Hub. A Service Container is not active by default. Relocating a backend service to a Service Container automatically activates it. | Can be replicated to scale out manually. You can define more than one Service Containers. | No selection needed. When you install an Application Server component, Service Container gets installed. |
TrueSight Capacity Optimization architecture
Application Server components
Backend services on Containers
