System-level administration overview
This page provides details on how to manage TrueSight Capacity Optimization at the operating system level.
Accessing TrueSight Capacity Optimization
You can access the TrueSight Capacity Optimization Application Server via Secure Shell (SSH) using the cpit account.
To access the TrueSight Capacity Optimization database, ask the DBA for the TNS name configuration, then log in as CPIT_OWN user (that is the owner of TrueSight Capacity Optimization schema).
The deployment is based on the cpit user. 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
1 - Services that are similar to the backend services in the Data Hub. Dynamic services are available for optimizer. If TrueSight Cloud Cost Control is installed, dynamic services are also available for cost pricing and cost forecasting.
If you install only the ETL Engine or the Application Server on a single computer, only the subfolders corresponding to the installed components will be present.
$CPITBASE directory also contains the subfolders that are shared between components:
Common components and templates
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. This data must be accessed in the read/write mode by the JSP Engine and Primary Scheduler and in the read-only 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 Network File System (NFS) mount point that maps an external storage that is reachable by both the servers.
$CPITBASE also contains some other subfolders that are 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.
To stop, start, or restart all services, run 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
To stop and start components
If you need to start, stop, or restart a single component, run 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:
Dynamic services (for cost prices)
|dynservices-costforecasting||Dynamic services (for cost forecasting)|
|dynservices-optimizer||Dynamic services (for optimizer)|
|dynservices-registry||Dynamic services (for registry)|
|httpd||Apache web server|
Web console Application Server
If you do not specify the component with the command, all components are started. For example, if you run the
./cpit start command without any <component>, all components are started.
To check logs
The following table lists the folder locations for the standard out and error logs for TrueSight Capacity Optimization components:
Log files folder