...
9. The Velocity Server Extensions Manager appears.
...
The Server Extensions Manager lists the service extensions that need to have update the computer’s name of the computer updated before they will work on the new computer. Make a note of which server extensions you are using.
...
Click Velocity's menu button, then select Extensions > Server Extensions.
The Velocity Server Extensions Manager appears.
Click Install.
The Find Server Extension dialog appears.Search for Identiv\Velocity root directory. Several HEX files are located here, as shown.
Select the extension you want to install and click Open.
The newly installed extension appears in the Server Extension list in the Velocity Server Extensions Manager. By default, the extension is enabled (checked,) and the word 'True' appears in the first column.
Repeat steps 3 to 5 to install more extensions.
When you are finished.
A message appears, prompting you to restart the Extension Service before the extension takes effect.Click OK.
For the service extension to take effect, right-click on the Velocity Service Control Manager (SCM) in Windows to try to stop stopping and restarting the extension service and restart it again.
Start the Velocity DIGI*TRAC Network Service.
...
In a larger facility with a lot of many activities taking place, the events and alarms table in the Velocity database can become quite large. It becomes critical for the older alarms and events to be archived.
...
On the old system, locate the ...\Program Files\Identiv\Velocity directory and find the velocitytmpxxxxx.dat files, where XXXX is the number of each encryption file.
There should be one data file for each SNIB2/SNIB3 installed in the system.Copy all relevant .dat files to a USB drive, removable media, or network-accessible location.
On your new computer, paste Paste the relevant .dat files into the ...\Program Files\Identiv\Velocity directory on your new computer.
These files will overwrite the existing files, and provide Velocity with the encryption information it needs to communicate with the connected SNIB2s/SNIB3s.
Open Velocity and resume communication between this Velocity server and the SNIB2/SNIB3 installed controller using the specified encryption.
...
Sometimes after importing the Velocity TLS certificate, permission for VelocityServices is not set correctly even though VelocityServices displays as having permission. When this occurs, you can fix this problem by deleting and re-granting permission to VelocityServices.
...