Data collection component configuration
On the Portal Server:
Create a Data Collector in the Portal to enable the Portal server to receive data from the Data Collector server. In the Portal, you must first create a Data Collector and then populate it with product-specific or host data collection policies. A single Data Collector can be installed for multiple capacity, fabric, virtualization, File Analytics, and backup products. This Data Collector configuration in the Portal contains the configuration details for communicating with the corresponding Data Collector Server.
Add subsystem-specific Data Collector Policies. A Data Collector Policy provides the configuration details required to communicate with a subsystem to retrieve data that will be stored in the database. These details are specific to the vendor of the enterprise object from which data is collected. Policies also allow you to set the schedule for data collection. Prior to creating Data Collector Policies, a Portal Data Collector must be created.
On the Data Collector Server:
Add the Portal IP address to the Local Hosts file on the Data Collector server or on any available client with web-browsing capabilities.
Note:
Only edit the local hosts file if a DNS entry hasn't already been set up in your enterprise to resolve both http://aptareportal.yourdomain.com and http://itanalyticsagent.yourdomain.com to the Portal IP address.
Install the Data Collector software. This software component, installed on the Data Collector Server, interfaces with each of the supported subsystems to extract meta-data about the underlying environment. For example, backup data can include job details and tape inventory information. In the case of Capacity Manager, the Data Collector communicates with the storage arrays in your SAN (Storage Area Network) to collect meta-data.