Teamwork Cloud (TWCloud) is equipped with a Data Manager for an administrative processprocesses. 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 DataManager tool from the same location you download the migration tools for the Cassandra database and UML meta-model.
Running the Data Manager
To run Data Manager
Stop the TWCloud serverStop the Teamwork Cloud server.
Make sure Cassandra is up and running.
Note
The ports through which Data Manager is connected to Cassandra are 9160 and 9042.
Download DataManager.zip.
Extract the zip file to the machine where you installed Cassandra.
On the command line, change the directory to the DataManager folder. Type the command , datamanager -help, to ./datamanager -help (or datamanager.bat -help on Windows) to display available commands like the following.
$
Code Block
language
bash
theme
DJango
linenumbers
true
./datamanager -help
Run your desired command to show the list of users like the following:
Code Block
language
bash
theme
DJango
linenumbers
true
./datamanager -lu
(On Windows, use datamanager.bat -lu)
Info
The log file of Data Manager appears in the following directory:
<user folder>/.twcloud/19.0/datamanager.log
Data Manager commands
The following table outlines the commands you can use in Data Manager to manage your data.
Delete the given revision(s) and all of its related information.
Specify multiple revision revisions using a comma as a separator.
The includeChildRevisionhave has two values: true and false.
When the includeChildRevision value is set to False, and the revision is not the latest, then it will not be deleted.
When the includeChildRevision value is set to True, thenrevisions upward and branches within it from the selected version will be deleted.
-du,--delete-user <username> <username> ...
Deletes a given username(s) and all of its related information.
If a 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:
--delete-user "dan smith"
or
-du "dan smith"
Specify multiple usernames using a space as a separator.
-lb,--list-branch <resourceID=value>
List all branches of the given resource.
-li,--list-index
List all available data that has an index.
-lr,--list-resources
Lists all available resources.
-lrd,--list-marked-deleted-resources
Lists all resources that were marked for deletion.
Lists all usernames and their information, sorted by name. You can add --no-info to show only the usernames.
-rap,--reset-administrator-password
Reset Administrator password to 'Administrator'.
If there is no account 'Administrator', it will be created.
If account 'Administrator' exists in the database:
If the account is for an external user, it will be reset to an internal user with a new password. This user will be shown in the TWCloud Teamwork Cloud Adminconsole.
If the account is an internal user, an only a new password will be generated and the user will be shown in the TWCloud Teamwork Cloud Adminconsole.
The default roles of the TWCloud Teamwork Cloud Admin will be restored to make sure that this account can fully operate as the default admin.
-rc,--recreate-cluster-id
Recreate a cluster ID or change it.
-ri,--rebuild-index <data=value1,value2>
Rebuild all indexes for the given data, use 'data=*' option to rebuild all indexes of all available data.
-urd,--unmark-deleted-resources <resource ID>
Unmark the given resource(s) that was previously marked as deleted.
- Specify multiple resource ID using space as separator
-version
Display Data Manager version.
-vi,--verify-index <data=value1,value2>
Verify all indexes for the given data, use 'data=*' option to verify all indexes of all available data.
The delete command to delete resources and users works as follows:.
The revision-related information which will be removed together with the revision includes:
Tags information of the revision
Object information created/modified at the revision
Commit information of the revision
Locking information of objects whose id's do not exist anymore in the branch that the revision belongs to
Branch information of the branch if the revision was the first revision of the branch
If a selected revision is not the latest, depending on the includeChildRevision valuevalue, the revision will be deleted or not:
When the includeChildRevision value is set to False, and the revision is not the latest, then it will not be deleted.
When the includeChildRevisionincludeChildRevision value is set to True, thenrevisions upward and branches within it from the selected version will be deleted.