...
| Note | ||
|---|---|---|
| ||
UPIMERGE has no effect on a Universal Agent application's behavior if the local Universal Broker is in managed mode. In that environment, configurations and component definitions reside in a database file, not a text file. Use the I-Management Console application to manage configurations for managed installations. |
Command Line Syntax
| Panel |
|---|
upimerge -dest filename [-source filename ] [ -installdir dirname { -cfgtype type [-comptype type] | -comptype type [-cfgtype type] } ] [ -keep_nomatch {yes|no} ] [ -bkup_dest {yes|no} ] [ -file filename | -encryptedfile filename [-key key] [-keypath path] ] [ -level { trace|audit|info|warn|error }[,{ time|notime }] ] upimerge { -help | -version } |
The following figure illustrates the syntax - using the long form of command line options - of Universal Products Install Merge.
| Panel | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Html bobswift | upimerge
-dest Html bobswift | filename [ -source Html bobswift | filename ] [ -installdir Html bobswift | dirname { -cfgtype Html bobswift | type [ -comptype Html bobswift | type] | -comptype Html bobswift | type [ -cfgtype Html bobswift | type] } ] [ -keep_nomatch Html bobswift | {<b>yes</b>|<b>no</b>yes|no} ] [ -bkup_dest Html bobswift | {<b>yes</b>|<b>no</b>yes|no} ] [ -file Html bobswift | filename | -encryptedfile Html bobswift | filename [ -key Html bobswift | key] [ -keypath Html bobswift | path] ] [ -level Html bobswift | { <b>trace</b>|<b>audit</b>|<b>info</b>|<b>warn</b>|<b>error</b>trace|audit|info|warn|error }[,{<b>time</b>|<b>notime</b> time|notime }] ] upimerge { -help Html bobswift | | -version Html bobswift | }
</pre>
|
Examples
For examples of how to run Universal Products Install Merge, see Merging Configuration Options Examples.