Files Used in Examples

The examples in this section demonstrate the expected results when Universal Products Install Merge is executed using two configuration files with the contents identified in the following tables.

Note

Although these examples show Windows path names, the Universal Install Merge behavior demonstrated also applies to UNIX systems.

Universal Agent Configuration File Sample (infile.txt)

The following table identifies the contents of infile.txt, a sample file in the Universal Agent standard keyword / value configuration file format.

For the examples in this section, infile.txt could represent an existing or archived configuration file, or a work file used to introduce and distribute configuration values across one or more target systems.

Keyword	Value
installation_directory	"C:\Program Files\Universal\UCmdMgr"
message_level	info
#host	some.remote.host
port	7850
license_product	"UNIVERSAL COMMAND MANAGER"
license_customer	"STONEBRANCH, INC."
license_type	DEMO
license_expiration_date	2012.12.21
license_nt_servers	1
license_key	078B-E180-64E6-3016-EA20-0CF4-58F9-B301 *

* This license key is for demonstration purposes only. It is not a valid license key.

Universal Agent Configuration File Sample (outfile.txt)

The following table identifies the contents of outfile.txt, another sample file in Universal Agent standard keyword / value configuration file format.

For the examples in this section, outfile.txt might represent a default configuration file that is delivered during product installation, or an existing production configuration file that needs to be updated with values from infile.txt.

Keyword	Value
port	7887
activity_monitoring	yes
event_generation	*,x100

Browser not supported