This table shows the required monitor plug-in and the corresponding performance monitor types.

1. Download the monitor plug-in F5RealServerPlugin.dll from the BIG-IP^® system.
   The plug-in is located in the folder /usr/local/www/docs/agents.
2. Copy F5RealServerPlugin.dll to the RealServer plug-ins directory. (For example, C:\Program Files\RealServer\plug-ins.)
3. If the RealSystem Server process is running, restart it.

1. Using the .iso image, burn a CD-ROM of the BIG-IP^® system software.
2. On the CD, navigate to the directory /downloads/rsplug-ins.
3. Copy the file F5RealMon.src.tar.gz to the directory /var/tmp on the BIG-IP system.
4. On the BIG-IP system, change to the directory /var/tmp: cd /var/tmp
5. Use the UNIX tar command to uncompress the file F5RealMon.src.tar.gz:
   For example, you might enter tar -xvzf F5RealMon.src.tar.
6. Change to the F5RealMon.src directory: cd F5RealMon.src
7. Type the ls command to view the directory contents.
8. To compile the source, use the instructions in the file build_unix_note.
9. Start RealSystem Server.

The procedure for installing the Data Gathering Agent on an IIS server differs depending on which IIS version the server is running and whether the Data Gathering Agent is the file f5isapi.dll, f5isapi64.dll, or F5.IsHandler.dll. This table shows each of the Data Gathering Agent files and the IIS versions that support each file.

1. Download the Data Gathering Agent (f5Isapi.dll or f5isapi64.dll) from the BIG-IP^® system to the Windows platform.
   You can find this plug-in in either the /var/windlls or the /usr/local/www/docs/agents directory on the BIG-IP system.
2. Copy f5isapi.dll or f5isapi64.dll to the directory C:\Inetpub\scripts.
3. Open the Internet Services Manager.
4. In the left pane of the Internet Services Manager, open the folder machine_name\Default Web Site\Script, where machine_name is the name of the server you are configuring.
   The contents of Scripts folder opens in the right pane.
5. In the right pane, right-click f5isapi.dll or f5isapi64.dll, and select Properties.
   The Properties dialog box for f5isapi.dll or f5isapi64.dll opens.
6. Clear Logvisits. (Logging of each visit to the agent quickly fills up the log files.)
7. Click the File Security tab.
   The File Security options appears.
8. In the Anonymous access and authentication control group box, click Edit.
   The Authentication Methods dialog box opens.
9. In the dialog box, clear all check boxes, then select Basic Authentication.
10. In the Authentication Methods dialog box, click OK to accept the changes.
11. In the Properties dialog box, click Apply.
    The WMI Data Gathering Agent is now ready to be used.

1. Create a scripts directory under the web site document root (C:\InetPub\wwwroot for Default Website).
2. Set the properties of the scripts directory to scripts and executables.
3. Copy the file f5isapi.dll or f5isapi64.dll to the created scripts directory.
4. Start IIS manager (inetmgr) and navigate to the scripts directory.
5. On the right pane, select the file name f5isapi.dll or f5isapi64.dll.
6. Select Properties > File Security > Authentication and Access Control and ensure that the settings anonymous user and Basic Authentication are selected.
7. If you want to allow all unknown extensions, then in IIS Manager, navigate to Web Server Extensions > All Unknown ISAPI extensions and allow all unknown extensions. Otherwise, proceed to step 8.
8. If you want to allow the file f5isapi.dll or f5isapi64.dll only, navigate to Web Server Extensions > Tasks: Add a New Webserver Extension . Then:
   1. For the Name setting, select F5 ISAPI and click Add for the required files. This requests a path to the file.
   2. Browse to the file f5isapi.dll or f5isapi64.dll, using the path C:\InetPub\wwwroot\scripts\f5isapi.dll for Default Website, and click OK.
   3. Select the Set Extension Status to Allowed check box, and click OK.
      The value F5 ISAPI should now appear in the extensions list as Allowed.

1. Create a scriptsdirectory under the directory C:\Inetpub. (C:\Inetpub\scripts).
2. Create a \bin directory under the scripts directory (C:\Inetpub\scripts\bin).
3. Set the properties of the scripts directory to scripts and executables.
4. Copy the file F5.IsHandler.dll to the directory C:\Inetpub\scripts\bin.
   In the C:\Inetpub\scripts directory, create the file web.config. This example shows a web.config file on an IIS server running version 6.0.

   <?xml version="1.0" encoding="UTF-8"?>
   <configuration>
       <system.web>
           <httpHandlers>
               <clear />
               <add verb="*" path="f5isapi.dll" type="F5.IsHandler" />
           </httpHandlers>
       </system.web>
   </configuration>

   Important: In this example, the path value f5isapi.dll appears to be a mistake but is actually correct. It is the type value F5.IsHandler that directs the server to the correct file.
5. From the Start menu, choose Control Panel and double-click Administration Tools.
6. Double-click Internet Information Services.
   This opens the IIS Management Console.
7. Expand the name of the local computer.
8. Allow the file ASP.NET v2.0build_number :
   1. Select Web Server Extensions.
   2. Select ASP.NET v2.0build_number .
   3. Click Allow.
9. Create a new virtual directory named scripts:
   1. Expand Websites and Default Web Site.
   2. Right-click Default Web Site, choose New, and choose Virtual Directory.
   3. Click Next.
   4. Type scripts for the alias and click Next.
   5. Type the name of the directory you created in step 1 (C:\Inetpub\scripts\) and click Next.
   6. Click Next again.
   7. Click Finished.
10. Create an application pool for the file F5.IsHandler.dll:
    1. Right-click Application Pools, select New, and select Application Pool.
    2. Type F5 Application Pool in the Application Pool ID field and click OK.
11. Right click scripts and select properties.
12. Set up the application pool:
    1. Click Virtual Directory.
    2. From the Application Pool list, select F5 Application Pool.
13. Set up the mappings:
    1. Click the Configuration button.
    2. On the Mappings tab of the Application Configuration screen, click Add.
    3. For the executable, type the file name C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ aspnet_isapi.dll.
    4. For the file name extension, type .dll.
    5. Clear the check box for Check that file exists and click OK.
    6. On the Application Configuration screen, click OK.
14. Set up directory security:
    1. Click Directory Security.
    2. Click the Edit button.
    3. Disable authentication by clicking the Anonymous Access and Integrated Windows box.
    4. Select the Basic Authentication check box and click OK.
       Note: If you are not authenticating locally, you might need to set the default domain or realm.
15. Set up the ASP.NET program:
    1. Click the ASP.NET tab.
    2. From the ASP.NET version list, select 2.0.buildnumber (for example 2.0.50727).
16. On the scripts Properties page, click OK.
17. Set up access to the IIS metabase:
    1. Run the command aspnet_regiis –ga <ASP.NETUsername>.
    2. See the web site http://support.microsoft.com/?kbid=267904.

1. Create a scripts directory under the directory C:\Inetpub. (C:\Inetpub\scripts).
2. Create a \bin directory under the scripts directory (C:\Inetpub\scripts\bin).
3. Copy the file F5.IsHandler.dll to the directory C:\Inetpub\scripts\bin.
4. In the C:\Inetpub\scripts directory, create the file web.config. This figure shows an example of web.config file on an IIS server running version 7.0.

   <?xml version="1.0" encoding="UTF-8"?>
       <configuration>
           <system.webServer>
               <handlers>
                   <clear />
                       \<add name="F5IsHandler" 
                            path="f5isapi.dll" 
                            verb="*" 
                            type="F5.IsHandler" 
                            modules="ManagedPipelineHandler" 
                            scriptProcessor="" 
                            resourceType="Unspecified" 
                            requireAccess="Script" 
                            preCondition="" />
               </handlers>
               <security>
                   <authentication>
                       <anonymousAuthentication enabled="false" />
                   </authentication>
               </security>
            </system.webServer>
         </configuration>
                   

   Important: In this example, the path value f5isapi.dll appears to be a mistake but is actually correct. It is the type value F5.IsHandler that directs the server to the correct file.
5. Allow anonymous authentication to be overridden by using the appcmd command to set the override mode in the machine-level applicationHost.config file.

                           appcmd set config "Default Web Site/scripts" 
                           /section:anonymousAuthentication /overrideMode:Allow 
                           /commit:APPHOST

6. Set up a new application pool for the file F5.IsHandler.dll:
   1. From the Start menu, choose Control Panel.
   2. Choose Administrative Tools
   3. Choose Internet Information Services (IIS) Manager.
   4. From Connections, expand MachineName ( MachineName\UserName ).
   5. Right click the Application Pools menu and choose Add Application Pool.
   6. In the Name field, type F5 Application Pool.
   7. Click OK.
7. Create a new application named scripts:
   1. Expand Web Sites and MachineName .
   2. Right-click MachineName and choose Add Application.
   3. In the Alias field, type scripts.
   4. To change the application pool, click Select.
   5. For the physical path, type the directory you created in step 1 (C:\Inetpub\scripts\).
   6. Click OK.
8. Change the Authentication setting to Basic Authentication:
   1. Select scripts.
   2. In the center pane, double click Authentication.
   3. Verify that the status of all items under Authentication is Disabled, except for the Basic Authentication item. To enable or disable an authentication item, right click the name and choose Enable or Disable.

1. Create a scripts directory under the directory C:\Inetpub (C:\Inetpub\scripts).
2. Create a \bin directory under the scripts directory (C:\Inetpub\scripts\bin).
3. Copy the file F5.IsHandler.dll to the directory C:\Inetpub\scripts\bin.
4. In the C:\Inetpub\scripts directory, create the file web.config.

   <?xml version="1.0" encoding="UTF-8"?>
                       <configuration>
                           <system.webServer>
                               <handlers>
                                   <clear />
                                   <add name="F5IsHandler" path="f5isapi.dll" verb="*" type="F5.IsHandler"
                                       modules="ManagedPipelineHandler" scriptProcessor="" resourceType="Unspecified"
                                       requireAccess="Script" preCondition="" />
                               </handlers>
                               <security>
                                   <authentication>
                                       <anonymousAuthentication enabled="false" />
                                   </authentication>
                               </security>
                           </system.webServer>
                           </configuration>

   Important: In this example, the path value f5isapi.dll appears to be a mistake but is actually correct. It is the type value F5.IsHandler that directs the server to the correct file.
5. Allow anonymous authentication to be overridden by using the appcmd command to set the override mode in the machine-level applicationHost.config file.

   appcmd set config "Default Web Site/scripts"
   /section:anonymousAuthentication
   /overrideMode:Allow /commit:APPHOST

   Note: appcmd is located in \windows\system32\intesrv.
6. Set up a new application pool for the file F5.IsHandler.dll:
   1. From the Start menu, choose Control Panel.
   2. Choose Administrative Tools.
   3. Choose Internet Information Services (IIS) Manager.
   4. From Connections, expand MachineName ( MachineName\UserName ).
   5. Right click the Application Pools menu and choose Add Application Pool.
   6. In the Name field, type F5 Application Pool.
   7. Click OK.
   8. From the Application Pools list, right click F5 Application Pool and choose Advanced Settings.
   9. Under the Process Model List, click Identity, and then click the button to the right of ApplicationPoolIdentity.
   10. From Built-in account select NetworkService.
   11. Click OK.
   12. Click OK.
7. Create a new application named scripts:
   1. Expand Sites.
   2. Right click Default Web Site and choose Add Application.
   3. In the Alias field, type scripts.
   4. Change the application pool, click Select, select F5 Application Pool from the Application Pool list, and click OK.
   5. For the physical path, type the directory you created in step 1 (C:\Inetpub\scripts\).
   6. Click OK.
8. Change the Authentication setting to Basic Authentication:
   1. Select scripts.
   2. In the center pane, double click Authentication.
   3. Verify that the status of all items under Authentication is Disabled, except for the Basic Authentication item. To enable or disable an authentication item, right click the name and choose Enable or Disable.

1. Create a scripts directory under the directory C:\Inetpub (C:\Inetpub\scripts).
2. Create a \bin directory under the scripts directory (C:\Inetpub\scripts\bin).
3. Copy the file F5.IsHandler.dll to the directory C:\Inetpub\scripts\bin.
4. Allow anonymous authentication to be overridden by using the appcmd command to set the override mode in the machine-level applicationHost.config file.

   appcmd set config "Default Web Site/scripts"/section:anonymousAuthentication/overrideMode:Allow /commit:APPHOST

   Note: appcmd is located in \windows\system32\inetsrv.
5. Set up a new application pool for the file F5.IsHandler.dll:
   1. From the Start menu, choose Control Panel.
   2. Choose Administrative Tools.
   3. Choose Internet Information Services (IIS) Manager.
   4. From Connections, expand MachineName ( MachineName\UserName ).
   5. Right click the Application Pools menu and choose Add Application Pool.
   6. In the Name field, type F5 Application Pool.
   7. Click OK.
   8. From the Application Pools list, right click F5 Application Pool and choose Advanced Settings.
   9. Under the Process Model List, click Identity, and then click the button to the right of ApplicationPoolIdentity.
   10. From Built-in account select NetworkService.
   11. Click OK.
   12. Click OK.
6. Create a new application named scripts:
   1. Expand Sites.
   2. Right click Default Web Site and choose Add Application.
   3. In the Alias field, type scripts.
   4. Change the application pool, click Select, select F5 Application Pool from the Application Pool list, and click OK.
   5. For the physical path, type the directory you created in step 1 (C:\Inetpub\scripts\).
   6. Click OK.
7. Change the Authentication setting to Basic Authentication:
   1. Select scripts.
   2. In the center pane, double click Authentication.
   3. Verify that the status of all items under Authentication is Disabled, except for the Basic Authentication item. To enable or disable an authentication item, right click the name and choose Enable or Disable.
8. Add a handler mapping:
   1. Select scripts.
   2. Click Handler Mappings.
   3. In the Actions pane on the right side of the screen, click Add Managed Handler.
   4. In the Request Path field, type F5Isapi.dll.
      Important: The Request Path value f5isapi.dll appears to be a mistake but is actually correct. It is the Type value F5.IsHandler that directs the server to the correct file.
   5. From the Type list, select F5.IsHandler.
   6. Type a name, such as F5 IsHandler.
   7. Click the Requested Restrictions button.
   8. Clear the check box labeled Invoke handler only if request is mapped to:
   9. Click OK.
   10. Click OK again.