si getdbfile
retrieves a configuration management file from the database
Synopsis
si getdbfile [--encoding=value] [--output=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
si getdbfile retrieves a configuration management file from the database, such as the si.properties file. Although PTC recommends editing the si.properties file in the GUI, you can retrieve the si.properties file from the database for manual editing. Once you are finished editing this file, you can store it in the database 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 to save the file in, for example, en_US (English, United States) or ja_JP (Japanese, Japan).
• --output=value
specifies the name of the file to store the output to on the local file system.
• 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
