You can use the
import_users script to import user information from a
JSON format to your Workbench installation.
To import 11.2 Workbench users to Tools and Frameworks 11.3:
Configure the
import_usersscript (Lei: Needed for 11.2 to 11.3 migration?):Navigate to the
ToolsAndFrameworks\11.3.0\admin\confdirectory.Set the
dest.workbench.hostanddest.workbench.portproperties to the host and port of your Tools and Frameworks 11.3 Workbench.By default, these values are set to
localhostand8006, respectively.For example:
dest.workbench.host=myhost.mycompany.com dest.workbench.port=8006
Set the
abort.on.duplicate.usersBoolean property:For example:
abort.on.duplicate.users=false
Comment out the
tools.mapping.fileproperty (Lei: Needed for 11.2 to 11.3 migration?)#-------- location of tools mapping (required if source.version 2.1.x & 3.1.0) #tools.mapping.file=<path-to-tools-mapping-json>
Optionally, set the
convert.ldapproperty totrueif you wish to convert all users to LDAP users during import.For example:
convert.ldap=true
Navigate to the
ToolsAndFrameworks\11.3.0\admin\bindirectory.Run the
import_usersscript with the following parameters:--input— Required. The path to the user data file that you got from running theexport_usersscript in 11.2.--config— Required. The path to theimport_users.propertiesfile.--default-user-password— The password value for any users that do not have a password set in the exported users file.--single-app— Optional. A single application for which to import users.
For example:
> import_users.bat --input user_20140514.json --config ..\conf\import_users.properties --default-user-password CHANGEME --single-app Discover
If a name matches an existing name but with characters in a different case (JOHN_Doe and John_Doe) and the
abort.on.duplicate.usersproperty is set totrue, the script stops. Invalid entries are logged toToolsAndFrameworks\<version>\admin\logs\import_validation_failed.log. The main log file is output toToolsAndFrameworks\<version>\admin\logs\import_users.log.
