Skip to main content

Create an ArcGIS Velocity site

An ArcGIS Velocity site is an individual deployment of Velocity. You must federate it with your ArcGIS Enterprise portal.

Note:

Only single-machine Velocity sites are supported.

To use the site configuration wizard to create a Velocity site, complete the following steps:

  1. Open a web browser and provide a URL in the following format: https://<your Velocity FQDN>:7143.

    For example, https://velocity-server-name.domain.com:7143

    Note:

    Accept the security warnings presented by your browser to begin the Velocity site configuration steps.

  2. In the ArcGIS Velocity for ArcGIS Enterprise Setup Wizard, click Create New Site.

  3. Provide a username and password for the Velocity primary site administrator account, and click Next.

    Tip:

    The password must be at least eight characters long.

    Note:

    The Velocity primary site administrator account is not an operating system account and is managed separately from other accounts in your user store. For more information, refer to accounts used by Velocity.

  4. Provide the paths for Log Root, Configuration Root, and Configuration Backup directories, and click Next.

    By default, the following locations are used:

    Directory Location Description
    Log Root <installation location>\Velocity\data\logs-root The storage location of logs generated by feeds, analytics, feed lifecycle orchestration, streams, and more.
    Configuration Root <installation location>\Velocity\data\config-root The location of Velocity site and configuration store content.
    Configuration Backups <installation location>\Velocity\config-backups The location of Velocity site backup configuration files that are automatically created every 24 hours.
    Directory Location Description
    Log Root <installation location>/Velocity/data/logs-root The storage location of logs generated by feeds, analytics, feed lifecycle orchestration, streams, and more.
    Configuration Root <installation location>/Velocity/data/config-root The location of Velocity site and configuration store content.
    Configuration Backups <installation location>/Velocity/config-backups The location of Velocity site backup configuration files that are automatically created every 24 hours.

  5. Choose Yes, this hostname is correct if the detected hostname is correct. Otherwise, choose No, I want to specify a different hostname and provide the hostname.

    Velocity automatically detects the hostname for your deployment. This hostname is the web address used to reach your Velocity site and serves as the primary access point for the system. Velocity also uses the hostname for other system functions, including the following:

    • Federation: Connect Velocity to your Enterprise portal.

    • Receiver feeds: External systems deliver data to Velocity through HTTP Receiver feeds or gRPC feeds and use this address.

    • Other integrations: Any service or system that needs to communicate with Velocity references this address.

    The Velocity machine must be able to resolve the hostname configured during site creation, not just external clients. If the hostname is a custom or internal domain not registered in public DNS, you must manually add an entry to the Velocity machine's hosts file.

    Edit /etc/hosts and add the following entry:

    Edit C:\Windows\System32\drivers\etc\hosts and add the following entry:

    127.0.0.1 <your_velocity_FQDN> <your_velocity_short_hostname>

    Note:

    Changing the hostname of the Velocity machine after installation is not supported and may result in unexpected behavior. If a hostname change is required, contact Esri Technical Support before continuing.

  6. Review the information in the Configuration Summary section, and click Finish.

    A confirmation message appears indicating that Velocity is installed and the site is created. The Velocity home page then opens.

    Note:

    At this step in the configuration process, the following warning message is expected: ArcGIS Velocity is not federated. Please ensure your instance of Velocity is federated to a portal.

  7. Continue to configure certificates for Velocity.