im putdbfile
puts a workflow and document configuration file into the database
Synopsis
im 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 creating and editing ViewSets and IPTs in the GUI, you can retrieve ViewSets and IPTs from the database for manual editing using the im getdbfile command. Once you are finished editing these files, you can store them in the database again using the im putdbfile command.
|
|
When updating an item presentation template (IPT) in the database from the CLI, the Integrity Lifecycle Manager Client GUI may not display the IPT change, even after restarting the client. This issue may also occur when promoting an IPT change from a staging server to a production server. This occurs when the IPT cache on the Integrity Lifecycle Manager Server is not updated correctly.
|
To clear and refresh the IPT cache on the server, use the following command:
im diag --diag=flushIPTCache
After using this command, PTC recommends restarting the Integrity Lifecycle Manager Client GUI to ensure updated IPTs display correctly.
|
|
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
im 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 im diag --diag=listdbfiles. For example, a valid file could be data\im\issue\templates\defect.xml, which is the IPT for the Defect type. For each IPT in Integrity Lifecycle Manager, there is an XML file under data\im\issue\templates\templatename.xml, for example, im putdbfile --input=c:/defect.xml data/im/issue/templates/defect.xml.
Diagnostics
See the
diagnostics reference page for possible exit status values.
See Also
