You can use the
import_users
script to import user information from a
JSON format to your Workbench installation.
To import 11.3.1.5.0 Workbench users to Tools and Frameworks 11.3.2:
Configure the
import_users
script:Navigate to the
ToolsAndFrameworks\11.3.2.0.0\admin\conf
directory.Set the
dest.workbench.host
anddest.workbench.port
properties to the host and port of your Tools and Frameworks 11.3.2 Workbench.By default, these values are set to
localhost
and8006
, respectively.For example:
dest.workbench.host=myhost.mycompany.com dest.workbench.port=8006
Set the
abort.on.duplicate.users
Boolean property:For example:
abort.on.duplicate.users=false
Comment out the
tools.mapping.file
property#-------- 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.ldap
property totrue
if you wish to convert all users to LDAP users during import.For example:
convert.ldap=true
Navigate to the
ToolsAndFrameworks\11.3.2.0.0\admin\bin
directory.Run the
import_users
script with the following parameters:--input
— Required. The path to the user data file that you got from running theexport_users
script in 11.3.1.5.0.--config
— Required. The path to theimport_users.properties
file.--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.users
property 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
.