si putdbfile
puts a configuration management file into the database
Synopsis
si putdbfile [--encoding=value] [--input=value] [--hostname=server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]] [(-F file|--selectionFile=file)] string...
Description
Although PTC recommends editing the si.properties file in the GUI, you can retrieve the si.properties file from the database for manual editing using the si getdbfile command. Once you are finished editing this file, you can store it in the database again using the si putdbfile command.
|
|
Access to configuration files is based on permissions. An administrator with the AdminServer or DebugServer permission for workflows and documents can edit workflow and document configuration files, an administrator with the AdminServer or DebugServer permission for configuration management can edit configuration management files, and an administrator with the Integrity Lifecycle Manager Server AdminServer or DebugServer permission can edit all configuration files.
|
Options
This command takes the universal options available to all
si commands, as well as some general options. See the
options reference page for descriptions.
• --encoding=value
specifies the code set the file is saved in, for example, en_US (English, United States) or ja_JP (Japanese, Japan).
• --input=value
specifies the name of the file on the local file system containing the input.
• string...
specifies the path and name of the file in the database. To display a list of files in the database, type si diag --diag=listdbfiles, for example, config\properties\si.properties.
Diagnostics
See the
diagnostics reference page for possible exit status values.
See Also
