Configuring IIS Web Server to work with eG Agent on Windows Environments

Configuring eG Agent to Monitor Web Transactions to Web Sites on IIS Web Server Operating on Windows 2000/2003

To enable the eG agent to monitor an IIS web server on Windows 2000/2003, follow the steps below:

  • First, make sure 'logging' is enabled on these platforms;
  • Next, make sure that the eG agent configuration is modified to support web transaction monitoring.

The sub-sections that follow will discuss each of these steps elaborately.

Enabling Logging on IIS Web Server

Logging triggers the creation of log files that track the URLs accessed on the IIS web server. The eG Enterprise suite requires these log files for monitoring the transactions to the web sites hosted on the IIS web server. In the absence of these log files, an eG agent will not be able to monitor web site transactions for Microsoft IIS web servers. Therefore, in order to enable the eG Enterprise suite to perform effective web transaction monitoring, logging must be enabled for the managed web sites.

Enabling Logging for Web Sites on Windows 2003

In the case of an IIS web server on Windows 2003, logging can be enabled using the procedure discussed below:

  1. Open the Internet Information Services (IIS) Manager on the IIS web server host using the menu sequence Start -> Programs -> Administrative Tools -> Internet Information Services (IIS) Manager. Figure 1 will then appear.

    Figure 1 : The IIS console

  2. If all the web sites on the IIS web server are being monitored by eG, then you will have to enable logging for all. To achieve this, right-click on the Web Sites node in the tree structure on the left pane of Figure 1, and select Properties (see Figure 2) from the shortcut menu that appears.

    Figure 2 : Selecting the Properties option from the shortcut menu of the Web Sites node (Windows 2003)

  3. Next, click the Web Site tab of the Properties dialog box (see Figure 3) that appears, and ensure that the Enable logging check box is selected.

    Figure 3 : Enabling logging for all the web sites

  4. Finally, click on the Apply and ok buttons to register the changes.
  5. If only a few selected web sites on the IIS web server are being monitored by the eG Enterprise suite, then logging needs to be enabled for those specific sites only. To achieve this, right-click on the web site being monitored from the tree-structure in the left pane the IIS Manager, and select Properties from the shortcut menu (see Figure 4). 

    Figure 4 : Selecting the Properties option for the egurkha web site

  6. Next, select the Web Site tab from the Properties dialog box, and select the Enable Logging check box as depicted by Figure 5. Finally, click on the Apply button and then the ok button.

    Figure 5 : Enabling access logging for the egurkha web site

  7. Enabling Logging for Web Sites on Windows 2000

    In the case of an IIS web server on a Windows 2000 host, follow the steps below to enable logging for the web sites.

  8. Open the Internet Information Services console on the IIS host using the menu sequence Start -> Programs -> Administrative Tools -> Internet Services Manager.
  9. If all the web sites on the IIS web server are being monitored by eG, you will have to enable logging for all. To achieve this, right-click on the node representing the IIS host in the tree structure in the left pane of the IIS console (see Figure 6), and select Properties from the shortcut menu that appears.

    Figure 6 : Selecting the Properties option from the shortcut menu of the IIS host node

  10. Click on the Edit button in Figure 7 to modify the Properties of the IIS web server.

    Figure 7 : Clicking on the Edit button

  11. Next, click the Web Site tab of the Properties dialog box (see Figure 8) that appears, and ensure that the Enable Logging check box is selected.

    Figure 8 : Selecting the 'Enable Logging' checkbox

  12. Finally, click on the Apply and ok buttons to register the changes.
  13. If only a few selected web sites on the IIS web server are being monitored by the eG Enterprise suite, then logging needs to be enabled for those specific sites only. To achieve this, right-click on the web site being monitored from the tree-structure in the left pane of the IIS console, and select Properties from the shortcut menu (see Figure 9). 

    Figure 9 : Selecting the Properties option for the Default web site

  14. Next, select the Web Site tab from the Properties dialog box, and select the Enable Logging check box as depicted by Figure 10. Finally, click on the Apply button and then the ok button.

    Figure 10 : Enabling access logging for the Default web site

Modifying the eG Agent Configuration to Enable Web Transaction Monitoring

In order to monitor the web transactions to the web sites on an IIS web server, a specific filter needs to be installed on the IIS web server to track all requests to and from the web server. To achieve this, the eG agent on the IIS web server has to be modified. To do so, perform the steps given below:

  1. Select Uninstall Agent from the options available under the eG Monitoring Suite -> eG Agent menu. The screen depicted by Figure 11 will appear. Here, select the Modify option and click the Next  > button.

    Figure 11 : Modifying the agent configuration

  2. If the eG agent setup program identifies an IIS server in the user environment, it expects the user to state if he/she wants to monitor this IIS server as depicted by Figure 12. If the user chooses Yes, the Setup installs a specific filter that will be used to track all requests to and from a web server. The default option is No.

    Figure 12 : IIS web server monitoring

  3. Then, restart the World Wide Web Publishing Service.
  4. Configuring the eG Agent to Monitor an IIS Web Server Operating on Windows 2008

The eG agent can monitor an IIS web server operating on Windows 2008 only if the Web Server role is configured on the target Windows 2008 server.

Typically, for an IIS web server to function on a Windows 2008 server, a Web Server Role should be configured on the server. The Web Server role in Windows Server 2008 lets you share information with users on the Internet, an intranet, or an extranet. If such a role does not exist on a Windows 2008 server, then, you cannot monitor the transactions to the IIS web server on that host; this is because, the ISAPI filter required for transaction monitoring cannot be installed on a Windows 2008 server without the Web Server role. 

To configure this Web Server role on a Windows 2008 server, follow the steps detailed below:

  1. Login to the Windows 2008 server as a local/domain administrator.
  2. Open the Server Manager console by following the menu sequence, Start -> Programs -> Administrative Tools -> Server Manager (see Figure 13).

    Figure 13 : Opening the Server Manager

  3. The Server Manager console then appears (see Figure 14).

    Figure 14 : The Server Manager console

  4. In the Server Manager console, click on the Roles node in the tree-structure in the left panel of the console. The information in the right-panel will change to display a Roles Summary and related details. To add a new role, click on the Add Roles option in the right panel of Figure 15.

    Figure 15 : Clicking on the Roles node in the tree-structure

  5. This will invoke the Add Roles Wizard. Click on the Next button in the welcome screen of Figure 16 to proceed with the role creation.

    Figure 16 : Clicking on the Next button in the welcome screen of the Add Roles Wizard

  6. The next step of the wizard prompts you to pick one/more roles to install on the Windows 2008 server. Select the Web Server (IIS) role depicted by Figure 17 to install it. Then, click the Next button to proceed.

    Figure 17 : Selecting the Web Server (IIS) role

  7. Then, when Figure 18 appears, click on the Next button to switch to the next step of the role installation.

    Figure 18 : An introduction to the web server role

  8. The next step will prompt you to choose the role services. Select all the listed services and click the Next button to proceed. Make sure that the IIS Management Scripts and Tools feature in particular is installed and enabled for the 'Web Server' role.

    Figure 19 : Selecting the required role services

  9. The screen that appears subsequently provides a summary of your specifications. After reviewing your selections, you can confirm installation of the chosen web server role by clicking on the Install button in Figure 20.

    Figure 20 : Installing the web server role

  10. Once installation completes successfully, Figure 21 will appear confirming the success of the installation.

    Figure 21 : A message indicating that installation was successful

  11. Click on the Close button in Figure 21 to close the wizard. Figure 22 will then appear displaying the newly installed role.

Figure 22 : The Roles page in the right panel displaying the Web Server (IIS) role that was just installed