On this page: Teamwork Cloud is equipped with a Data Manager for administrative processes. You need to download the data manager .zip file and extract it to the machine where you installed Cassandra. Before using Data Manager, we recommend that you backup your database in the same manner as you do before using the migration tool. You can download the Data Manager tool from the same location you download the migration tools for the Cassandra database and UML meta-model. To run Data Manager Stop the Teamwork Cloud server. If the command-line migration tool is running, it needs to be stopped as well. Make sure Cassandra is up and running. The ports through which Data Manager is connected to Cassandra are 9160 and 9042. Download DataManager.zip. Be sure to only use Data Manager distributed with version 2021x Refresh2 Hot Fix 5. On the command line, change the directory to the DataManager folder. Execute the following command on Linux to display all available commands: Run the desired command on Linux, for example, to show the user list: The Data Manager will connect to Cassandra on localhost using anonymous authentication. If your Cassandra node is configured to bind to a specific IP address (by default ports 9160 and 9042 bind to all interfaces), or if you have configured Cassandra to use an authenticator other than AllowAllAuthenticator, you will need to modify <installation_dir>/configuration/application.conf accordingly. The log file of Data Manager appears in the following directory: The following table outlines the commands you can use in Data Manager to manage your data. -help -dk, --drop-keyspace <keyspace=value> --silent-drop Drops the 19.0 keyspace to free up the storage space after the database migration from 19.0 to 2021x. You need to clear the removed keyspace snapshots using the nodetool utility command: -dr,--delete-resource <resource ID> Deletes the given resource(s) and all of its related information. Specify multiple resource IDs using space as a separator. If you delete a synchronized resource from the target server, the resource will be removed together with its remote resource configuration allowing you to create new configurations with the same resource from the source server. -drb,--delete-branch <resourceID=value branchID=<ID1>,<ID2> includeChildBranch=<true/false>> Deletes the given branch(es) and all of its related information. Specify multiple branch ID using a comma as a separator. includeChildBranch has two values: true and false. This command does not work for the branches of a synchronized resource. You can delete only the whole synchronized resource, but not its branches. -drd,--delete-marked-deleted-resources Deletes all resources that were marked as deleted. If you delete a synchronized resource from the target server, the resource will be removed together with its remote resource configuration allowing you to create new configurations with the same resource from the source server. -drr,--delete-revision <resourceID=value revision=<revision1,revision2> includeChildRevision=<true/false>> Deletes the given revision(s) and all of its related information. Specify multiple revisions using a comma as a separator. includeChildRevision has two values: true and false. This command does not work for the revisions of a synchronized resource. You can delete only the whole synchronized resource, but not its revisions. -du,--delete-user <username> Deletes the given username(s) and all of its related information. Specify multiple usernames using comma as a separator. If the username consists of two words (for example, dan smith) you must add double quotation marks (" ") before and after the username, as shown in the following example: Removes the read-only flag from a synchronized resource or category in the target server. Specify multiple resources or categories using a comma as a separator, for example: Do not remove the read-only flag from periodically synchronized resources or categories. This will cause version inconsistencies after subsequent synchronizations. The read-only flag removal is recommended only if resources or categories were moved to another server as a result of a one-time synchronization operation and you want to make them active again. -lb,--list-branch <resourceID=value> Lists all branches of the given resource. -lc,--list-cluster-ids -li,--list-index -lr,--list-resources -lrd,--list-marked-deleted-resources -lrv,--list-revision <resourceID=value branchID=value> -lu,--list-users <--no-info> Lists all usernames and their information, sorted by name. You can add --no-info to show only the usernames. -ram,--reset-administrator Resets admin password, status, and permissions. -rc,--recreate-cluster-id Recreates a cluster ID. -ri,--rebuild-index <data=value1,value2> Rebuilds all indexes for the given data and uses the data=* option to rebuild all indexes of all available data. -urd,--unmark-deleted-resources <resource ID> Unmarks the given resource(s) previously marked as deleted. Specify multiple resource ID using space as a separator. -vb,--validate-blob <savePath=value onlyInconsistent=value --readAllWithCQL --createCompareOfThriftAndCQL> -ve,--validate-eobject <resourceID=value1,value2 saveDir=value onlyInconsistent=value> -version -vi,--verify-index <data=value1,value2> Verifies all indexes for the given data and uses the data=* option to verify all indexes of all available data. -vr,--validate-rbac <savePath=value onlyInconsistent=value> -vrc,--validate-resource-commit <savePath=value onlyInconsistent=value> Removes released object locks (that are no longer used) from the database. How to safely execute this command: These commands delete a selected resource and all of the following resource-related information: This command deletes a selected user and all of the following user-related information: In the modeling tool's history panels, the word deleted will appear in brackets next to the deleted users. The branch-related information which will be removed together with the branch includes: The revision-related information which will be removed together with the revision includes: Related pagesRunning the Data Manager
./datamanager -help
./datamanager -lu
<user folder>/.twcloud/2021x/datamanager.log
Data Manager commands
Server tool command Function Displays Help information. nodetool clearsnapshot -- <keyspace>
--delete-user "dan smith"
-du "dan smith"
-rrof, --remove-read-only-flag <-resourceID=<value1>,<value2> --categoryID=<value1>,<value2>> datamanager -rrof --resourceID=a4c498c9-f125-453c-b9cb-3d5a6e675714 --categoryID=a1d569ea-fe6a-402f-8a25-aef6b932de48
Lists previous cluster IDs and the current one. Lists all available data that have indexes. Lists all available resources. Lists all resources that are marked as deleted. Lists all revisions in the given branch. Validates blob information. Validates the eObject information of a specific resource ID and uses the resourceID=* option to validate all resources. Displays the version of Data Manager. Validates a user, user group, role, and role assignment information. Validates a metamodel, branch, and committed information. -col,--cleanup-object-locks
The delete command to delete resources and users works as follows.Deleting selected resource
-dr,--delete-resource <resource ID> <resource ID> ...
Deleting selected user
-du,--delete-user <username>,<username> ...
Deleting selected branch
-drb,--delete-branch <resourceID=value branchID=<ID1>,<ID2> includeChildBranch=<true/false>>
Deleting revisions
-drr,--delete-revision <resourceID=value revision=<revision1,revision2> includeChildRevision=<true/false>>