Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

This section details information about requirements that must be in place before beginning the installation, pre-installation tasks that you must perform, and other considerations. If you are upgrading from a previous BMC ProactiveNet or BMC Impact Solutions installation, see the BMC ProactiveNet Upgrade Guide.

High-level planning tasks

Planning item

Notes

Plan your BMC ProactiveNet deployment.

For details see BMC ProactiveNet Deployment.

Prepare host computers for installation

User and reports worksheet

Planning item

Value

Notes

Users

 

The expected number of concurrent BMC ProactiveNet users.

Daily reports

 

The expected number of daily BMC ProactiveNet reports.

Weekly reports

 

The expected number of weekly BMC ProactiveNet reports.

Monthly reports

 

The expected number of monthly BMC ProactiveNet reports.

Planning sizing and scalability

The sizing factor for BMC ProactiveNet is performance data and events being monitored. Read the information in Performance and scalability recommendations and then fill out the values in the table.

Planning item

Value

Notes

Types of devices

 

Determine the types of devices you want to monitor in your environment.

Types of monitors

 

Determine the types of monitors that are required to monitor your environment.

Total number of monitor instances per monitor type

 

Determine the number of monitor instances required to monitor your environment. A monitor instance is an object that is being monitored such as a file system, logical disk, and so on. If you are familiar with BMC PATROL, a monitor instance corresponds to an application instance.

Total number of attributes

 

Calculate the total number of attributes to be monitored based on the monitor type and the number of monitor instances per monitor type. An attribute is a property of a monitor instance. For example, attributes of a file system monitor instance are file size, file creation date and time, file modification date and time, file access date and time, and so on. If you are familiar with BMC PATROL, an attribute corresponds to a parameter.

Polling periods

 

Polling periods have an effect on the number of attributes. Performance and scalability details for common deployments specifies the number of attributes based on 5-minute polling. If polling is faster, the effective number of attributes will be higher by a factor of 2.5.