Page tree
Skip to end of metadata
Go to start of metadata

Planning to deploy and configure Gateway Server and Agent involves planning for hardware as well as software. The hardware planning includes decisions about network connections, disk space requirements, and the computers that will be used. Configuration complexity varies depending on the unique requirements of your environment. The planning information in some of the following sections might not be appropriate for every situation.

For more information, refer to the following sections: 

Plan data repositories

During installation you are prompted to enter the directory paths or accept the default paths for the repositories of history data and collected data. The following sections describe each repository and help you plan for the appropriate directories before installation. 

History and collected data do not have to be on the same drive as the product software, and the data can exist on a network drive. On the Gateway Server computer the collected data can reside on a remote file system. However, BMC recommends that the history and collected data repositories be placed on a local file system to ensure better performance and to reduce the possibility of data corruption caused by network problems.

Collect data repository

The collect data repository stores the system performance data from distributed systems that the Collector gathers and summarizes. The data is stored in the repository for each computer on which data collection is requested. Performance analysis is based on this data. Specify the path names for the collect data repository or accept the default during installation.

History data repository

History data is used for the real-time charts in Investigate. You can enable or disable the collection of historical data during installation. If you do not specify a directory for the history data repository, you cannot see historical data on that particular computer. BMC recommends that the history data repository be placed on a local, non-root file system (not on a remote file system) to ensure better performance when using the history features. Specify the path names for the history data repository or accept the default during installation.

Back to top ↑

Configure email notification

You can configure email notifications to be sent from BMC TrueSight Capacity Optimization installed on both Microsoft Windows and UNIX platforms.

Email notification on Microsoft Windows

To receive email messages from BMC TrueSight Capacity Optimization on Windows for any notification that the product supports, you must specify the email settings during installation or as a post-installation activity. Specify the mail server, the port (the default is 25), and an email address to receive email notifications (SMTP or MAPI mail) from the Perform Agent. Email messages are sent to the specified email address for notification of failed message delivery and alerts. The mail server and port number are used for other notifications as well, such as when a data collection has successfully completed. The person who performs the daily monitoring of the product might be suitable for receiving the notifications.

Email notification on UNIX

Email notification on UNIX depends on the mail setting on that computer. Typically the account that executes BMC TrueSight Capacity Optimization receives the email notifications.

Back to top ↑

Configure the proxy host

The configuration of proxy hosts for proxy data collection is a post-installation activity. Take into consideration the following points:

Back to top ↑

Review the shared memory and semaphore settings on UNIX systems

On UNIX systems, the Perform Agent and Collector require semaphores and shared memory segments on all computers. The collectors require one semaphore and one shared memory segment for each metric group per instance and each collector per instance. If the installation warns about inadequate shared memory and semaphores, be prepared to reconfigure these values. For more information about reconfiguring these values, see Shared memory and semaphore resources requirements for collecting data on UNIX systems.


When setting up BMC TrueSight Capacity Optimization on a UNIX computer, configure the real-time antivirus software to exclude the udr and logs directories when it scans for viruses.

Configure the Visualizer database in the sample deployment scenario

Visualizer is the component for storing collected data and viewing graphs. It runs only in a Microsoft Windows environment.

Identify the database

If you intend to use Visualizer for viewing graphs, you must choose a database. Automator populates the data into the database and export graphs for Visualizer.

BMC strongly recommends that the database server be dedicated to running Visualizer and Automator, and that you use SQL Server or Oracle Database for large-scale implementations. For a small-scale implementation or for testing, you can use Microsoft Access. For more information, see The Visualizer database.

Configure the DSN

After you identify the database, configure the data source name (DSN). You configure the DSN from the Microsoft Windows Control Panel or the ODBC program group. 

For more information on identifying and configuring the database, refer to the Visualizer Getting Started guide.

Back to top ↑

Plan the policy and domain files

If computer domains have been identified, you can use this information to create the policy files on the Microsoft Windows console or the domain files on the UNIX console. The policy and domain files are used by the Manager component.

A Manager script file includes one or more policy or domain files. Note that the graphs and reports are generated on a per policy or domain basis. Configuring your Manager scripts with the appropriate policy and domain files provides more meaningful graphs and reports for performance analysis and capacity planning.

Back to top ↑

Schedule the scripts for Manager

You can schedule Manager scripts to run daily, weekly, or monthly. The scripts involve many automated tasks such as data collection, transfer, analysis, and population. Evaluate the overall network traffic of the infrastructure and identify an appropriate time frame for transferring data from a Perform Agent computer to the console computer. Use this time when configuring the Manager script. You should also identify the best time for daily monitoring (data collection).

For example, if network traffic is low at 5 A.M., then schedule the Manager script to run from midnight to midnight for a 24-hour run and set the data transfer at a delay of five hours, so that the data transfer begins at 5 A.M. when network traffic is low. The time needed for data analysis depends on the amount of data to be analyzed, which ultimately determines when graphs and reports can be viewed. 

Evaluate the need to identify the frequency for scheduling the Manager scripts. For complex environments, or large-scale data collection, consider consulting BMC Professional Services for assistance.

Back to top ↑