Sample file for bulk import of IIS monitors - Applications Manager User Guide

#1. Header should start with #Header: followed by the Input Field names. It is already coded for you. Note: Do not modify the header.

#2. From the second line onwards give the input values according to the column names in the header.

#3. You can remove the example entries in this file from the second line onwards and add your own monitor input information. You can add comments by including # symbol in the beginning of the line.

#4. Save the file in any computer but upload it to the Applications Manager webclient using bulk import monitor form.

#5. After uploading click Next. The entire monitor input information will be shown in a table format for your reference.

#6. If everything is OK click on Start Discovery. The monitors will be scheduled for discovery. It would take few minutes to complete the process. When the monitors are scheduled for discovery simultaneously the uploaded file will be deleted from Applications Manager (as this file contains security information)

#7. If you want to cancel the process in midway delete the uploaded file from Applications Manager machine.

#8. Fields MonitorGroupID and PollInterval are Optional. If PollInterval is not specified the default value will be 5 minutes.

#9. PollInterval should be given in Minutes.

#10. Enter the credentialID, if you wish to use preconfigured credentials details from Credentials Manager.

#11. ManagedServerID and ManagedServerGroupName can be specified only if bulk import is being performed from the Admin Server in the Enterprise Edition.If these field values are not specified, then the new monitor will be added in the in least loaded Managed Server.

#12. The existing MonitorGroupID have to be specified and it will not create new Monitor Group if the ID specified is not existing.

#13. Allowed values for 'SSL is enabled', 'Do not resolve DNS name.' and 'Response Header Check' are 'True' and 'False'.

#14. Set 'Do not resolve DNS name.' option to 'True' only when not to resolve the given IP Address else use 'False'.

#15. Set 'Response Header Check' to 'False' to disable the URL response header check. We check for 'IIS' keyword in the response header of IIS-server URL.

#16. Set 'Mode Of Monitoring' option to 'wmi' to use WMI mode of monitoring and 'winrm' to use WinRM mode of monitoring.

#17. Set 'WinRM Protocol' option to use the protocol with which the WinRM mode of data collection happen. Possible values are 'http' and 'https'. No value needed for WMI mode.

#18. Set 'Use Custom WinRM Port' as 'Yes' to enter a custom port for WinRM mode of data collection else use 'False' to use the default ports 5985 for http and 5986 for https portocols. No value needed for WMI mode.

#19. Set the value for 'Custom WinRM Port' with required port for WinRM only when the 'Use Custom WinRM Port' is set as 'Yes' else no value needed. No value needed for WMI mode.

#20. Set the value for 'Re-try URL check during data collection' as 'True' to re-try the basic URL check if failed during data collection. Else set as 'False'.

#Header:DisplayName,Host Name / IP Address,Port,SSL is enabled,Mode Of Monitoring,WinRM Protocol,Use Custom WinRM Port,Custom WinRM Port,credentialID,User Name,Password,Do not resolve DNS name.,Response Header Check,Re-try URL check during data collection,MonitorGroupID,PollInterval

Production,server1,80,False,winrm,http,False,,,domain\administrator,P@s$w0rd,False,False,False,,5

Staging,server2,443,True,winrm,https,True,5986,,domain\administrator,P@s$w0rd,False,True,False,,5

Development,server3,80,False,wmi,,,,1,,,False,True,False,,5

Testing,server4,80,False,wmi,,,,,,,False,True,True,,5