Configuring Vista Bridge

💡: Vista Bridge is an API server for Viewpoint’s Vista on-premise application. It serves to give Aclaimant integrations access to our customers Vista instance by adding an API layer. It interacts directly with Vista’s underlying MSSQL database.


This Article Has the Following Sections:

Setting Up Docker on Windows:


Set Up Notes:

  • Docker is required in order to run the vista bridge, Docker can be run on a Linux server or Windows server.
  • A minimum Windows Server version of 1709 is required.
  • The following instructions were tested on Windows Server 2019.
  • Running Linux Containers on Windows (LCOW) is still considered experimental
  • Docker requires Hyper-V to run on Windows. On a physical machine, this may require enabling virtualization in the BIOS. If running on a cloud provider like AWS/Azure, this will require specific instance types. On AWS, it requires a bare metal instance like i3.metal. On Azure look for HyperThreaded instances like D_v3, Ds_v3, E_v3, Es_v3, F2s_v2 - F72s_v2, M (subject to change, has more info)



  1. Log into your Windows instance with administrator credentials.

  2. Launch Powershell.

  3. Install Docker EE using DockerMsftProvider.

    Install-Module "DockerMsftProvider" -Force Update-Module "DockerMsftProvider" Install-Package Docker -ProviderName "DockerMsftProvider" -Update -Force
  4. Select Yes if prompted to install the NuGet Provider.

  5. If needed, restart.

  6. Launch Powershell.

  7. Enable Windows Containers Feature.

    Install-WindowsFeature Containers
  8. If needed, restart.

  9. Launch Powershell.

  10. Enable Experimental Features.

    Set-Content -Value "`{`"experimental`":true`}" -Path C:\\ProgramData\\docker\\config\\daemon.json
  11. Restart Docker.

    Restart-Service docker
  12. Check Docker Info and verify Experimental is set to true.

    docker info
  13. LCOW Setup:

  14. Create Folder C:\Program Files\Linux Containers

    cd 'C:\\Program Files\\' mkdir "Linux Containers"
  15. Download the latest release from

    cd '.\\Linux Containers\\' curl -OutFile <>
  16. Expand Archive

    Expand-Archive -DestinationPath . .\\
  17. Delete

  18. Make sure Hyper-V is installed

    Install-WindowsFeature Hyper-V –IncludeManagementTools –Restart
  19. You may need to restart after Hyper-V installs. If so, log back in and launch Powershell.

  20. Test docker on Linux.

    docker run --rm -it --platform=linux busybox echo "LCOW on a Windows Server!"---
  21. You should see LCOW on a Windows Server! If the above command is successful, you’re ready to install the Vista Bridge. If not, some docker troubleshooting will be required.



Environment Variables
Variable name Required? Default Description




The secret API Token that will be used by the Aclaimant system for authentication when making API calls




Instance name, used for tagging of logs in LogDNA




The database username used to access the Vista MSSQL instance




Vista database password for given user




Vista database host




Vista database port




Vista database dbname


Loading and Running the Docker Image (Loading the Tar):

  • docker load -i aclaimant-vista-bridge-<version>.tar

Initial Run of the Docker Image:

  1. To set the necessary environment variables you can put them in a file or instead use -e ACL_VB_<env>=<value> -e ACL_VB_<env>=<value

  2. Argument -v sets where on disk the search index is stored, useful for restarting and maintaining the index.

docker run -itd -p 80:80 -p 443:443 -v <folder-for-data-on-windows-server>:/usr/vista-bridge/data --name=aclaimant-bridge-<version> --env-file=<envfile> --restart unless-stopped aclaimant/vista-bridge:<version>

An example env-file minimally should look like:


Docker Image Notes:

  • -d Runs this as a daemon

  • --restart=unless-stopped Will cause the container to start whenever docker restarts on the machines, unless the container had been stopped with docker stop aclaimant-bridge-<version>

  • --name is optional and can be anything; it's becomes useful for working with the instance

  • sudo may be required before all docker commands; especially if running on linux

  • -p 443:443 Binds the docker image's port 443 to your local port 443

  • -p 80:80 Binds the docker image's port 80 to your local port 80


Updating Vista-Bridge Version:

  1. Stop the previous version. Note: this uses the name from the currently running instance; you can see this with docker ps

    docker stop aclaimant-bridge-<old-version>
  2. Start the new version


Working with the Docker Container:

  1. Viewing logs

    docker logs -t aclaimant-bridge
  2. Stopping instance

    docker stop aclaimant-bridge
  3. Re-starting the instance

    docker start aclaimant-bridge

Note: The aclaimant-bridge is the --name from the initial run command above. Feel free to change it in all places.

Post Setup:

  1. Aclaimant and customer will both need the API token in order for the servers to communicate.

  2. Aclaimant will need the IP of the customer's server.

    • Aclaimant will create a DNS record on our side in order to communicate with this server.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.