System-level administration overview
This page provides details on how to manage TrueSight Capacity Optimization at the operating system level.
Components of a TrueSight Capacity Optimization installation
The main components of a TrueSight Capacity Optimization deployment are:
- Application Server:
- Data Hub
- Service container
- Web server
- ETL Engine
- Presentation Server
- Gateway Server
- Database Server
Accessing the TrueSight Capacity Optimization machine
It is possible to access the TrueSight Capacity Optimization server via SSH (Secure Shell) using the account cpit.
To access the TrueSight Capacity Optimization database, ask the DBA for the TNS name configuration, then login as user CPIT_OWN (that is the owner of TrueSight Capacity Optimization schema).
The deployment is based on the user cpit. The entire TrueSight Capacity Optimization installation is contained in a single directory (usually
$CPITBASE directory contains one sub-folder for every TrueSight Capacity Optimization component installed on the system:
Web Console Application Server
If you install only the ETL engine or the Application Server a single machine only the sub-folders corresponding to the installed components will be present.
$CPITBASE directory there are also sub-folders shared between different components:
Common components and templates
Content Repository (i.e. charts and reports)
The Content Repository directory contains charts and reports and can be used to contain data (For example, csv files) to be processed by the ETL engine: it has to be accessed in read/write mode by the JSP Engine and Primary Scheduler and in read mode by the Web Server. In case of a split installation (one server as ETL engine, one as Application server) the Content Repository directory can be an NFS (Network File System) mount point that maps an external storage, reachable by both machines.
$CPITBASE also contains also some other sub-folders, used for installation and update purposes:
For installation packages
For update packages
For DB schema update packages
The start, stop, and restart procedures are managed with a single script,
cpit, located in the home directory of each Application server where TrueSight Capacity Optimization is installed.
Only the installed components in each server are managed by the script.
In order to stop,start,restart all services, execute the following command from the home directory
./cpit stop all: stop all services
./cpit start all: start all services
./cpit restart all: stop all services
Stopping and starting components
If you need to start, stop or restart a single component, execute the following command from the home directory:
./cpit stop <component>: stop the web service
./cpit start <component>: start the web service
./cpit restart <component>: stop the web service
where <component> can be one of the following:
TrueSight Capacity Optimization component
|httpd||Apache web server|
Web console Application Server
If you don't specify the component (i.e: you simply issue the command
./cpit start) this is intended as an all.
The standard out and standard error logs for TrueSight Capacity Optimization components can be found in the positions specified in the following table:
Log file location
|Auto forecasting services|
|Capacity Aware Placement (CAPA)||datahub/log/|
For information about the error codes, see Error codes.