Re-designed the whole tool in order to bring it to the standards of the rest of our command line tools

$ checkconsistency -h
usage: checkconsistency -a <action> -o <source> [-i <sourceId>] [-r
<policy> -y <policyAction>] [-l <jmxUser>] [-s
<jmxPassword>] [-t <jmxHost>] [-p <jmxPort>]
[--responsetimeout <responseTimeout>]
-a,--action <arg> Defines the action
Available actions are: [list_unassigned,
list_missing, repair, repair_configdb,
check_configdb]
-h,--help Prints a help text
-i,--source-id <arg> Defines the source identifier. If source is
set to 'all' then this option is simply
ignored
-l,--login <arg> The optional JMX login (if JMX
authentication is enabled)
-o,--source <arg> Defines the source that is going to be used
Available sources are: [database, context,
filestore, all]
-p,--port <arg> The optional JMX port (default:9999)
-r,--policy <arg> Defines the 'repair' policy
Available repair policies are:
[missing_entry_for_file,
missing_file_for_attachment,
missing_file_for_infoitem,
missing_file_for_snippet,
missing_file_for_vcard]
--responsetimeout <arg> The optional response timeout in seconds
when reading data from server (default: 0s;
infinite)
-s,--password <arg> The optional JMX password (if JMX
authentication is enabled)
-t,--host <arg> The optional JMX host (default:localhost)
-y,--policy-action <arg> Defines an action for the desired repair
policy
Available policy actions are: [delete,
create_dummy, create_admin_infoitem]
The OX check consistency tool