SoftwareLoaderCMD.exe
Using the SoftwareLoaderCMD.exe program, you can import files into the One Identity Manager database. You can run the program from the command line.
Calling syntax
SoftwareLoaderCMD.exe /Conn="{Connection string}" /Auth="{Authentication String}" [/Root="{Path}"] [-I] /Files="{files|Targets}"
Calling example
Updating files that are known in the QBMFileRevision table.
SoftwareLoaderCMD.exe /Conn= "Data Source=<Database server>;Initial Catalog=<Database name>;User ID=<Database user>;Password=<Password>" /Auth="Module=DialogUser;User=<User name>;Password=<Password>" /Root="c:\source" -N
Importing customer-specific files
SoftwareLoaderCMD.exe /Conn= "Data Source=<Database server>;Initial Catalog=<Database name>;User ID=<Database user>;Password=<Password>" /Auth="Module=DialogUser;User=<User name>;Password=<Password>" /Root="c:\customsource" -I /Files="Custom.*.dll|Server|Client"
Table 63: Program parameters
|
/Conn |
Database connection parameter. Minimum access level Configuration user. |
|
/Auth |
Authentication data. The authentication data depends on the authentication module used.
For detailed information about the authentication modules, see the One Identity Manager Authorization and Authentication Guide. |
|
/Root |
Optional parameter. Directory for the files. |
|
-I |
Optional parameter. Only in combination with /Files. If this parameter is not set, only the files that are already known in the QBMFileRevision table are imported. If this parameter is set, unknown files are also imported into the databased and an entry is created in the QBMFileRevision table. |
|
/Files |
List of files with pipe-delimited (|) specification of machine roles that are imported into the database. The entry of wild cards (*) is permitted.
Example:
/Files="Custom.*.dll|Server|Client" |
|
-N |
Optional parameter. If this parameter is set, all files are updated which are known in the QBMFileRevision table and which are located in the directory specified under /Root. /Conn, /Auth and /Root are mandatory parameters in this mode. -I and /Files are not taken into account. |
|
-? |
Display program help. |
DBTransporterCMD.exe
Using the DBTransporterCMD.exe program, you can import transport packages into the One Identity Manager database. You can run the program from the command line.
Calling syntax
DBTransporterCMD.exe [-V] [-L] [-I|-P|-S] [-N] [-U] /File="{Transport file}" /Conn="{Connection string}" /Auth="{Authentication String}" [/MergeAction=Error|Transport|Database|Interactive]
Calling example
DBTransporterCMD.exe [-L] /File="c:\source\transport.zip" /Conn= "Data Source=<Database server>;Initial Catalog=<Database name>;User ID=<Database user>;Password=<Password>" /Auth="Module=DialogUser;User=<User name>;Password=<Password>"
Table 64: Program parameters
|
/Conn |
Database connection parameter. Minimum access level Configuration user. |
|
/Auth |
Authentication data. The authentication data depends on the authentication module used. For detailed information about the One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide. |
|
/File |
Transport file to be imported into the database. |
|
/MergeAction |
(Optional) Definition of conflict handling. Permitted values are:
- Error: An error occurred.
- Transport: (Default) Values are transferred from the transport package.
- Database: Database values are retained.
- Interactive: User entry for conflict handling expected for each object.
|
|
-V |
If this option is set, logging is performed automatically. |
|
-L |
If this option is set, a log file is generated for the data import. |
|
-I |
If this option is set, errors in insertion and saving are ignored. |
|
-P |
If this option is set, errors in insertion are ignored. |
|
-S |
If this option is set, saves during insertion are ignored. |
|
-N |
If this option is set, the database is not compiled. |
|
-U |
If this option is set, the database is not set to single user mode. |
|
-? |
Display program help. |
DataImporterCMD.exe
The DataImporterCMD.exe program provides support for importing data from CSV files into a One Identity Manager database. You can run the program from the command line. The program requires the import definition files for import. You create import definition files using the Data Import program.
Calling syntax
DataImporterCMD.exe /Conn="{Connection string}" /Auth="{Authentication String}" [/Prov="{Provider}"] [/Definition="{Path to import definition file}"] [/ImportFile="{path to import file}"] [/DefinitionPair="{Path to import definition file}|{path to import file}"] [/LogLevel=Off|Fatal|Error|Info|Warn|Debug|Trace] [/Culture="{Language code}"][-p]
Example call for importing a single file
/Prov=VI.DB.ViSqlFactory, VI.DB
/Conn= "Data Source=<Database server>;Initial Catalog=<Database name>;User ID=<Database user>;Password=<Password>"
/Auth=Module=DialogUserAccountBased
/Defintion=C:\Work\Import\Data\Def_DataImporter_Employee.xml
/ImportFile=C:\Work\Import\Data\1_Employees.csv
Example call for importing multiple files
/Prov=VI.DB.ViSqlFactory, VI.DB
/Conn= "Data Source=<Database server>;Initial Catalog=<Database name>;User ID=<Database user>;Password=<Password>"
/Auth=Module=DialogUserAccountBased
/DefinitionPair=C:\Work\Import\Data\Def_DataImporter_Employee.xml|C:\Work\Import\Data\1_Employees.csv
/DefinitionPair=C:\Work\Import\Data\Def_DataImporter_Department.xml|C:\Work\Import\Data\2_Departments.csv
/DefinitionPair=C:\Work\Import\Data\Def_DataImporter_Locality.xml|C:\Work\Import\Data\3_Localities.csv
/DefinitionPair=C:\Work\Import\Data\Def_DataImporter_CostCenter.xml|C:\Work\Import\Data\4_CostCenters.csv
Table 65: Program parameters
|
/Conn |
Database connection parameter. Minimum access level End user |
|
/Auth |
Authentication data. The authentication data depends on the authentication module used. For detailed information about the One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide. |
|
/Prov |
Optional parameter. Database provider. The following values are permitted: VI.DB.ViSqlFactory, VI.DB and QBM.AppServer.Client.ServiceClientFactory, QBM.AppServer.Client. |
| /Definition |
Path to the import definition file.
Example:
C:\Path\To\Definition.xml |
| /ImportFile |
Path to the import file. Multiple instances of this parameter are possible. The import definition file specified in the /Definition parameter is used.
Example:
C:\Path\To\Import.csv |
| /DefinitionPair |
Pair of the import definition file and the import file. The files are separated by a pipe character (|). Multiple instances of this parameter are possible.
Example:
C:\Path\To\Definition.xml|C:\Path\To\Import.csv |
| /LogLevel |
Optional parameter. Scope of output to be processed. Permitted values are:
-
Off: No logging.
-
Fatal: All critical error messages are logged.
-
Error: All error messages are logged.
-
Info: All information is logged.
-
Warn: All warnings are logged.
-
Debug: Debugger outputs are logged. This setting should only be used for testing.
-
Trace: Highly detailed information is logged. This setting should only be used for analysis purposes. The log file quickly becomes large and cumbersome. |
|
/Culture |
Optional parameter. Language used to create the file. The language is required in order to read local character formats correctly, for example, dates.
Example: en-US |
|
-p |
Optional parameter. If this parameter is used, the processing progress is shown. |
|
-? |
Display program help. |
Related topics
SchemaExtensionCmd.exe
The SchemaExtensionCmd.exe program provides support for importing custom schema extensions into a One Identity Manager database.
In databases with a Test environment or Development system staging level, you can use the program to delete custom schema extensions again.
You can run the program from the command line. The program requires a control file (XML file) for the import. To create control files, use the program. For more detailed information, see the One Identity Manager Configuration Guide.
Calling syntax
SchemaExtensionCmd.exe /Conn="{Connection string}" /Auth="{Authentication String}" [/Definition="{Path to import definition file}"] [-f] [/LogLevel=Off|Fatal|Error|Info|Warn|Debug|Trace]
Calling example
SchemaExtensionCmd.exe /Conn="Data Source=<Database server>;Initial Catalog=<Database name>;User ID=<Database user>;Password=<Password>" /Auth=Module=DialogUserAccountBased /Definition=CustomExtensions.xml
Table 66: Program parameters
|
/Conn |
Database connection parameter. Minimum access level Configuration user. |
|
/Auth |
Authentication data. The authentication data depends on the authentication module used. For detailed information about the One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide. |
| /Definition |
Path to the control file (XML file)
Example:
C:\Path\To\Definition.xml |
| /LogLevel |
Optional parameter. Scope of output to be processed. Permitted values are:
-
Off: No logging.
-
Fatal: All critical error messages are logged.
-
Error: All error messages are logged.
-
Info: All information is logged.
-
Warn: All warnings are logged.
-
Debug: Debugger outputs are logged. This setting should only be used for testing.
-
Trace: Highly detailed information is logged. This setting should only be used for analysis purposes. The log file quickly becomes large and cumbersome. |
|
-f |
Optional parameter. if this parameter is set, the system does not wait for the processing of DBQueue Processor tasks. This can lead to errors if schema extensions are expected that must previously be generated by the DBQueue Processor. |
|
-? |
Display program help. |
