Planning to deploy Gateway Server and Agent

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 ↑

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.

Note

When setting up 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.

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. For more information, see Managing the Gateway Server agent list.

Back to top ↑

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

Comments