VW4Tool — the command line tools for VirtualWisdom4 — was initially built to allow customers and VI personnel to create a JSON Entity-import for VirtualWisdom4. Although few customers liked CSV or had used XML, fewer still know what “a Jason is”, so there have been some challenges. Notably, JSON being somewhat immature, there are fewer globally-available simple processing tools for JSON content.
VirtualWisdom4 is fully expected to replace this desire for the most part: there will always be long-tail issues and corner-cases, but I do welcome the time when VirtualWisdom4 fully supports the needs met by VW4Tool.
VW4Tool tries to use the same formats (i.e. patterns) that VirtualWisdom4 uses to emphasize the formats and to help support a common skillset. Rather than confuse users by creating a new format for regular expressions and such, “accidental compatibility” is offered by using a similar format. In this way, whatever a user figures out in VW4Tool can hopefully help them after VW4Tool is no longer required.
VW4Tool is entirely opensource, and uses entirely opensource components:
- VW4Tools builds vw4tool.jar
- FibreChannel Parsers provides the parsing of text files from zone files, alias exports, etc;
- source code is at https://github.com/chickenandpork/fibrechannel-parsers
- WWNDesc provides some nickname/WWPN mapping and breakdowns;
- source code is at https://github.com/chickenandpork/wwndesc
- FibreChannel Parsers provides the parsing of text files from zone files, alias exports, etc;
Updates related to VW4Tool are under the VW4Tool tag
In order to use VW4Tool, you’ll need:
- vw4tool.bat
- vict.jar
(yes, the code is rolled into this project)
These components are downloadable from a URL that your VI Field Application Engineer can provide.
Alternatively, you can directly download vw4tool.jar from http://chickenandpork.github.io/vw4tools/vw4tools.jar