IIS Probe - Monitoring & Reporting - questions

book

Article ID: 196286

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

1. Pre-Requisites

a. "ISAPI Filters"
Is it necessary to add this Server Role through the Server Manager? Is it needed to be done at the IIS server level? As far as I understood by reviewing the documentation, that would be required to have ASP counters activated, right?

b. "ASP"
I have also seen that there is this ASP Server Role, although it is not identified as a pre-requisite to activate ASP counters. Should it also be checked as well, or not really?

* I have tried to add these roles on Pre-Prod environment, but only seeing this. Is it because this is not an IIS server? Would those Roles listed in a/b be visible on the IIS server?

c. "Metabase Compatibility component"
I have also seen that this component is mentioned to be installed. By looking into the documentation, it is not very clear to me how to do so though. Should it be installed on the IIS server? 

d. "Configure IISRequest.cfg"
Is this also a pre-requisite to be done at IIS server end after the IIS probe is deployed? As per the documentation, I believe that the default cfg file content should remain untouched and just confirmed to be "probemachine, iisservermachine, 999", right? 

Cause

- guidance

Environment

Release : 9.0.2

Component : UIM - IIS

Resolution

1. Pre-Requisites

a. "ISAPI Filters"
Is it necessary to add this Server Role through the Server Manager? Is it needed to be done at the IIS server level? As far as I understood by reviewing the documentation, that would be required to have ASP counters activated, right?

>>>Yes. You do it on the IIS server.

Activate the ASP Counters on IIS 7 or above
To use the element, you must install the ISAPI Filters module on version 7 and later.
For more information about installing the component, see http://www.iis.net/ConfigReference/system.webServer/isapiFilters

>>>Please refer to

>>>https://docs.microsoft.com/en-us/iis/configuration/system.webServer/isapiFilters/
and/or
>>>https://docs.microsoft.com/en-us/iis/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/classic-asp-not-installed-by-default-on-iis

>>>Server Roles apply to->Windows Server 2012 or Windows Server 2012 R2.

b. "ASP"
I have also seen that there is this ASP Server Role, although it is not identified as a pre-requisite to activate ASP counters. Should it also be checked as well, or not really?

>>>ASP Server Role-that depends on the version. see links above.

* I have tried to add these roles on Pre-Prod environment, but only seeing this. Is it because this is not an IIS server? Would those Roles listed in a/b be visible on the IIS server?

>>>Yes, done on the IIS server.

c. "Metabase Compatibility component"
I have also seen that this component is mentioned to be installed. By looking into the documentation, it is not very clear to me how to do so though. Should it be installed on the IIS server?

>>>Yes on the IIS server

Installing Metabase Compatibility Support
>>>You can find this component in setup under Internet Information Services->Web Management Tools -> IIS X.0 Management Capability Feature.

This component is not installed by default because IIS is not initially set up to use it. The legacy interfaces have some limitations and are not ideal for working with distributed configuration files (see Limitations section below); therefore it is recommended that over time, and especially when opening up the configuration system for more and more delegation (i.e. more and more web.config files with IIS settings in them are present on the system), customers will consider porting legacy scripts and applications over to the new system and its interfaces.

It is also recommended that new scripts and applications be developed using the new interfaces, so they work ideally with the new system, and can have access to the new properties, concepts and structure of the configuration system.

When all of the legacy scripts and applications are ported to the new interfaces, it is recommended to uninstall the Metabase Compatibility feature.

d. "Configure IISRequest.cfg"
Is this also a pre-requisite to be done at IIS server end after the IIS probe is deployed? As per the documentation, I believe that the default cfg file content should remain untouched and just confirmed to be "probemachine, iisservermachine, 999", right?

>>>Yes, correct.

Configure IISRequest.cfg
Follow these steps:
Navigate to ..\Nimsoft\probes\application\iis folder and edit the IISRequest.cfg file.
Ensure the following:
The first line is the host name of the computer where the IIS Server Monitoring probe is running (probe machine).
The second line is the host name of the IIS server computer (IIS server machine).
The host name that you define must match with the host name or IP address that you provide while creating the probe profile.
The port number is in the last line, by default it is 999. This port number is used for communication between the IIS Request filter on the IIS Server and the probe.
Save and close the file.
Restart the IIS server.