VICT — the VI Client Tool — was built to allow customers and VI personnel the same ability to check various data sources and repair issues without modifying the data in the VW3 database. Created when VirtualWisdom started with “Net”, it has evolved over time to be a “Swiss Army Knife” for VW3.

Vict was intended to fill the gap in determining which of various dependencies are met or unmet: we currently have a Deployment Checklist which asks for a lot of information but which customers may have challenges collecting (for example, SSL client certificates). Additionally, some issues have been problematic with customers, such as as successfully uploading in binary mode with a checksum, which tends to take a few days to troubleshoot back to the upload corruption; VICT handles this all so easily in a batch-able method. Finally, FAEs can leverage some of the post-install-check capabilities which are now path of the PortalHealthcheck (which leverages some common code).

Portions of this tool are closed-source because some was built with information that came from logging into the database and looking around. Where the source is not 100% open, I have kept the code closed, but “clean” parts are being moved to opensource.

The companion tool, vw4tool for VirtualWisdom4, is entirely opensource.

Updates related to VICT are under the VIClientTool tag

In order to use VICT, you’ll need:

• vict.bat
• vict.jar

These components are downloadable from a URL that your VI Field Application Engineer can provide.