Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Open Control Panel.

  2. Locate and click on the ‘Turn Windows Features on or off link.

  3. In the resulting Server Manager window, click the Features item (in the left pane) and click the Add Features link.

  4. In the resulting Add Roles and Features Wizard, provide the necessary information and click Next on each of the first few pages.

  5. On the Select server roles page of the wizard, check [√]the Web Server (IIS) role, and click Next.

  6. In the resulting dialog that asks ‘Add features that are required for Web Server (IIS)?’, check[√] the option to ‘Include management tools (if applicable),’ and click the Add Features button.

  7. On the Select features page of the wizard, check [√]the following options (as shown in the screen capture), and click Next.

    • .NET Framework 3.5 Features

    • .NET Framework 3.5 Features > .NET Framework 3.5 (includes .NET 2.0 and 3.0)

    • .NET Framework 4.6 Features > ASP.NET 4.6

    • .NET Framework 4.6 Features > WCF Services > TCP Port Sharing

  8. Read the displayed information on the wizard's resulting Web Server Role (IIS) page and click Next.

  9. On the wizard's resulting Select role services page, check [√] the following options (as shown in the following subsequent screen capture), and click Next.

    • Web Server

    • Web Server > Common HTTP Features

    • Web Server > Common HTTP Features > Default Document

    • Web Server > Common HTTP Features > Directory Browsing

    • Web Server > Common HTTP Features > HTTP Errors

    • Web Server > Common HTTP Features > Static Content

    • Web Server > Common HTTP Features > HTTP Redirection

    • Web Server > Health and Diagnostics

    • Web Server > Health and Diagnostics > HTTP Logging

    • Web Server > Performance

    • Web Server > Performance > Static Content Compression

    • Web Server > Security

    • Web Server > Security > Request Filtering

    • Web Server > Application Development

    • Web Server > Application Development > .NET Extensibility 3.5

    • Web Server > Application Development > .NET Extensibility 4.6

    • Web Server > Application Development > ASP.NET 3.5

    • Web Server > Application Development > ASP.NET 4.6

    • Web Server > Application Development > ISAPI Extensions

    • Web Server > Application Development > ISAPI Filters

    • Management Tools

    • Management Tools > IIS Management Console

    • Management Tools > IIS 6 Management Compatibility

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Management Console

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Scripting Tools

    • Management Tools > IIS 6 Management Compatibility > IIS 6 WMI Compatibility

    • Management Tools > IIS Management Scripts and Tools

  10. On the wizard's resulting Confirm installation selections page, check [√] the option to ‘Restart the destination server automatically if required, and review the displayed information to determine whether it is correct.

    • If something is not correct, click Previous to return to the previous page and make the necessary changes.

    • If everything is correct, click Install.

      Progress messages on the Installation progress page of the wizard are displayed until the installation is complete.

  11. Verify that the Web Server (IIS) role was installed in the Server Manager window. You can then close the Server Manager window and the Control Panel.

...

  1. Open Control Panel.

  2. Locate and click on the ‘Programs and Features' link.

  3. Once in the Programs and Features window, click on the 'Turn Windows Features on or off link.

  4. In the resulting Server Manager window, click the Dashboard item (in the left pane), and click the Add roles and features link.

  5. In the resulting Add Roles and Features Wizard | Before you Begin, click Next.In the resulting

  6. Select Role-based or feature-based installation in the Add Roles and Features Wizard | Installation Type, select Role-based or feature-based installation, and click Next.

  7. In the resulting Add Roles and Features Wizard | Server Selection, select a server from the server pool, and click Next.

  8. In the resulting Add Roles and Features Wizard | Server Roles, select Web Server (IIS).

  9. In the resulting dialog that asks ‘Add features that are required for Web Server (IIS)?’, check[√] the option to ‘Include management tools (if applicable),, and click the Add Features button, then click Next.

  10. On the Select features page of the wizard, check [√]the following options (as shown in the next screen capture), and click Next.

    • .NET Framework 3.5 Features

    • .NET Framework 3.5 Features > .NET Framework 3.5 (includes .NET 2.0 and 3.0)

    • .NET Framework 4.7 Features

    • .NET Framework 4.7 Features > .NET Framework 4.7 (Installed)

    • .NET Framework 4.7 Features > WCF Services > TCP Port Sharing (Installed)

  11. In the resulting Add Roles and Features Wizard | Web Server Role (IIS), read the displayed information, and click Next.

  12. On the wizard's resulting Select role services page of the wizard, check [√] the following options (as shown in the next subsequent screen capture), and click Next.

    • Web Server

    • Web Server > Common HTTP Features

    • Web Server > Common HTTP Features > Default Document

    • Web Server > Common HTTP Features > Directory Browsing

    • Web Server > Common HTTP Features > HTTP Errors

    • Web Server > Common HTTP Features > Static Content

    • Web Server > Common HTTP Features > HTTP Redirection

    • Web Server > Health and Diagnostics

    • Web Server > Health and Diagnostics > HTTP Logging

    • Web Server > Performance

    • Web Server > Performance > Static Content Compression

    • Web Server > Security

    • Web Server > Security > Request Filtering

    • Web Server > Application Development

    • Web Server > Application Development > .NET Extensibility 3.5

    • Web Server > Application Development > .NET Extensibility 4.7

    • Web Server > Application Development > ASP.NET 3.5

    • Web Server > Application Development > ASP.NET 4.7

    • Web Server > Application Development > ISAPI Extensions

    • Web Server > Application Development > ISAPI Filters

    • Management Tools

    • Management Tools > IIS Management Console

    • Management Tools > IIS 6 Management Compatibility

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Management Console

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Scripting Tools

    • Management Tools > IIS 6 Management Compatibility > IIS 6 WMI Compatibility

    • Management Tools > IIS Management Scripts and Tools

  13. On the wizard's resulting Confirm installation selections page of the wizard, check [√] the option to ‘Restart the destination server automatically if required, and review the displayed information to determine whether it is correct.

    • If something is not correct, click Previous to return to the previous page and make the necessary changes.

    • If everything is correct, click Install.

  14. On Progress messages on the Installation progress page of the wizard , progress messages are displayed until the installation is complete.

  15. In the Server Manager window, verify Verify that the Web Server (IIS) role was installedinstalled in the Server Manager window. You can then close the Server Manager window and the Control Panel.

...

The Velocity Web Services Client works like a typical Web page and connects to Microsoft’s IIS using the HTTP protocol. The default network port is 80, which some other programs might already be used by some other programusing.

If you want to use a network port other than the default of 80, you can perform the following steps to configure the network port used by the default IIS Web site to communicate with the Velocity Web Services Client.

  1. From your Windows Server Start menu (on the computer where IIS and the Velocity Server are installed), select Administrative ToolsInternet Information Services (IIS) Manager.

  2. In the Connections pane of the Internet Information Services (IIS) Manager window, expand the computer name, expand Sites, and then click on Default Web Site.

  3. In the Actions pane (under Edit Site), click on Bindings.

  4. In the resulting Site Bindings dialog, click the HTTP entry, and then click on Edit.

  5. In the resulting Edit Site Bindings dialog, enter the desired value (such as 8080) for the Port, and click OK.

  6. Close the Site Bindings dialog.

  7. In the Actions pane of the Internet Information Services (IIS) Manager window (under Manage Web Site), click Stop, and then click Start.

Ensuring that the Network Port used by the Default IIS Web Site is Allowed Through Your Firewalls

Because the Velocity Web Services Client communicates across a shared network (instead of a dedicated physical security network), you will have to work with your network administrator to ensure that the network port used by the default IIS Web site is allowed through your firewalls. Some networks use the software firewall provided with Microsoft Windows, other networks others use a software firewall provided by a different vendor (as shown in the following image), and high-security networks include hardware firewalls.

...

  1. Open the Windows 10 Control Panel, and click on the Windows Firewall link.

  2. Click on the Advanced settings link (in the left column).

  3. In the resulting Windows Firewall with Advanced Security window, click on Inbound Rules (in the left pane), and then click on New Rule… in the Actions pane.

  4. On Select the Port option on the Rule Type page of the resulting New Inbound Rule Wizard, select the Port option, and then click Next.

  5. On the Protocol and Ports page, select the TCP option, select the Specific local ports option and enter the desired value (such as 8080), and then click Next.

  6. On the Action page, click Next to accept the defaults.

  7. On the Profile page, click Next to accept the defaults.

  8. On the Name page, enter the required Name, optionally enter a Description, and click Finish.
    This allows the Network Port used by the Default IIS Web Site through your Firewalls.

...

Quick Tour of the Velocity Web Services Client

This guide section of the guide provides a quick high-level quick tour of the functionality available in the Velocity Web Services Client.

Logging into the Velocity Web Services Client

The Login page is used to log for logging in to this client.  Enter the Operator Name and Password of an existing Velocity operator, and click the Login button.  If either the Operator Name or the Password is incorrect, the following error message is displayed:

...

After you successfully log in to the Velocity Web Services Client, there is an Operator drop-down menu (in the upper right corner) that includes commands to:

  • display Display an About dialog which shows version information for Velocity and the Velocity Web Services Client

  • open Open the Settings page where you can specify some options for the Velocity Web Services Client (including the “Landing Page” Page which is the default page displayed after you log in)

  • Open the Enrollment tab to set the Query Size which will determine the Enrollment Manager Search results (between 5 - 50).  The default value is 10.

  • Open the Alarms tab to view the default fields:

  • Open the Events tab to view the default fields:

  • Select the Status Dashboard to view the default fields.

  • Click the Security Settings tab to view and modify the available fields.

  • logout , from your current session (and return to the Login page)

...

  • Access Summary (Today)

  • People/Credentials

  • Live Events

  • Queued Downloads on your controllers

  • Live Events

  • Performance Status

  • Door Status

  • Status Viewer by Controllers/Ports/Xboxes

    Image RemovedImage Added

Status Bar

The status bar at the bottom of the Velocity Web Services Client shows the Status of the DIGI*TRAC Service running on the Velocity Server.

...