Besides bumping DataVersion checking in PHC, VIFT also gains the ability to wipe and reset a 3.6.0 Administrator password
Tag Archives: vift
Revision 617 – Dump Existing Nicknames moved from VIFT; initial DCFM extraction
After some discussion, the query used for “–dump-config=nickname.csv” in VIFT was improved and added back into VICT. This allows a simple export of the existing Nicknames for use in the “-R” option to revision 615 so that a customer who wants to generate a Nickname Diff can do so using:
java -jar vict.jar -D nickname.csv
java -jar vict.jar -N bna://server/ -D nickname.csv -n diff-nicknames.csv
This ensures that diff-nicknames.csv includes only the NEW nicknames for import.
Additionally, notice how –nickname=bna://server/ is used; this is an abbreviation for bnapsql:// for which cmcne:// also applies:
java -jar vict.jar -N bna://server/ -N cmcne://otherserver/ -D nickname.csv -n diff-nicknames.csv
If you’re leveraging the PHC-based Suggested nicknames, you can still use the VICT as a copying entity:
java -jar vict.jar -D nickname.csv
java -jar phc.jar -A\some\path\bob
java -jar vict.jar -N bna://server/ -N \some\path\bob-Nicknames.csv -D nickname.csv -n diff-nicknames.csv
There’s some initial work for vict.jar -N dcfm://
but the schema is still up-in-the-air.
Now go keep those nicknames updated!
Revision 560 – move FixNicknameHistory to VIFT
Per the conversation at SKO, the “–fixnicknamehistory” is the only art of VIClientTool (vict) that is a writeable action; otherwise, vict is read-only. In order to be sure that vict cannot hurt the database, the writeable portion of vict is moved back into the VIFieldTool (vift). vift is never left with a customer.