Web Connector Setup

Prerequisite:

The Web Connector requires the complete Microsoft .NET Framework 4 to be installed. This means that both the Microsoft .NET Framework 4 Client Profile and the Microsoft .NET Framework 4 Extended must appear in the list of installed programs. If either of these is not installed, you must install it.

The Web Connector also requires Internet Information Services (IIS) version 6 (or higher) to be installed and turned on. If IIS is not turned on, it can be installed and / or turned on by accessing the Windows Features on your operating system. If you are turning on IIS for the first time, make sure that the Web Management Tools and World Wide Web Services are both turned on.

You must have completed and verified your Tracking Server installation before setting up the Web Connector.

If your system meets the minimum requirements for deploying the Web Connector (Tracking Server, IIS, and .NET Framework 4 installed), follow these steps. These steps are generalized to accomodate all operating systems, but be aware that slight differences exist between different operating systems.

Steps:
  1. Deploy the Web Connector to the appropriate IIS location.

    If you have already completed the Tracking Server post installation setup, you may have already completed this step.

    1. Open the Tracking Server Post Install dialog box through the Start menu (Start > Programs > ArcGIS Tracking Server > Post Install).
    2. Click "Run" next to Deploy Web Connector. The Deploy Web Connector dialog box appears.
    3. Click the Browse button and browse to the root directory of IIS. (typically "C:\Inetpub\wwwroot")
    4. Select the directory and click OK.
    5. The selected directory now appears in the text box on the Deploy Web Connector dialog box. Click Deploy to deploy Tracking Viewer.
    6. Click "Exit" to close the Tracking Server Post Install dialog box.
  2. Open a Windows Command Prompt and use the following command to install ASP.NET (v4.0.30319) Applications with IIS: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

    Make sure that you have administrative rights to do this.

    NoteNote:

    If you are using a 64-bit operating system, you will need to specify the Framework64 folder instead.

  3. It is recommended to add an IIS Application Pool specifically for Tracking Server Web Connector. Depending on your version of IIS, this can be done by opening IIS Manager (inetmgr), right-clicking on Application Pools, and selecting Add Application Pool. When you create the application pool, be sure to select .NET Framework 4.0 as the .NET Framework version.

    This will isolate Tracking Server Web Connector from other Web applications you may also have running on IIS, allowing you to stop and start Tracking Server Web Connector without disturbing the other Web Applications.

  4. In IIS Manager (inetmgr), convert the WebConnector folder to an application. Depending on your version of IIS, this can be done by right-clicking on WebConnector (or accessing the folder properties) and selecting an option to Create Application or Convert to Application.

    If you created an application pool specifically for Tracking Server Web Connector (as recommended above), be sure to select that application pool to be used by the application. If you choose to use a different application pool (such as the default application pool), make sure that the application pool is set to use .NET Framework 4.0.

  5. Make sure that ASP .NET is allowed for the Web Site. Open IIS Manager (inetmgr) and navigate to the Web Site Properties for WebConnector. Select the correct ASP .NET version.

    This may not be required for all operating systems and versions of IIS.

  6. In IIS Manager (inetmgr), make sure that Active Server Pages and ASP .NET are allowed in the Web Service Extensions folder.

    This may not be required for all operating systems and versions of IIS. The image below shows where this needs to be done if you are using IIS 6.

  7. Using a text editor, open the "Web.config" file, which is located in the WebConnector folder. Modify the host names within the trackingWebConnectorConfiguration tags to the appropriate machine names where the corresponding Tracking Server components are located. For example, modify the hostName property within the trackingGatewaySection to the name of the machine where the Tracking Gateway is located. In a similar way, modify the hostName properties in the trackingServerSection and WebConnectorSection to the names of the machines that are hosting those components.
    TipTip:

    You may need to modify the properties of the "Web.config" file so it isn't read-only before editing the file.

    In a standard installation, all three of these Tracking Server components will reside on your local machine. Regardless, it is always important to set these properties to the explicit name of the host machine for each component, or else some Web Connector features may not work when accessed externally. For example, Web Connector KML services will not be accessible from other machines if the Web Connector host name is not explicitly set.

  8. The Generic Input Datalink must be configured properly and turned on in order for the Web Connector to function properly. A connection must be configured using the correct settings.
    1. Start Tracking Server.
    2. Click on the Data Links tab.
    3. Double-click Generic Input to open the Generic Input Data Link Properties dialog box.
    4. Create a connection, or modify an existing connection, to use the input port specified for the Web Connector (default is 5555), the TCP Server transport protocol, and CSV text format (using default delimiters).

      The following screenshot shows the default configuration required.

    5. Click OK to close the dialog box.
    6. Make sure that the Generic Input Data Link is running. To do this, ensure that Generic Input is checked on the Data Links tab of Tracking Server Manager.
  9. The Tracking Server Connector Data Link must also be connected to the Tracking Gateway for Tracking Server Web Connector to function properly. Double-click Tracking Server Connector on the Data Links tab of Tracking Server Manager, and ensure that the Connection Status is "Connected".
  10. Tracking Server Web Connector is now configured for use.

    Depending on the exact sequence of steps you have followed, you may need to restart IIS or the Tracking Gateway before using the Web Connector.

  11. Occasionally, Tracking Server Web Connector may need to be restarted. To restart it, either restart IIS or restart the specific application pool being used by Tracking Server Web Connector.
8/21/2012