Installing via the Command Line
Use the command line interface to expedite the installation process by suppressing some or all of the dialog boxes that appear during a GUI installation. This becomes particularly useful when installing multiple instances of the OSE Gateway.
When entering the command, use the following syntax:
packagename.exe -a --argument1=value --argument2=value where:
packagename.exe equals the name of the executable file (e.g., OSE_r188.8.131.52p27.exe).
-a identifies that arguments follow in the command.
--argument1 equals the arguments you wish to use from the table below.
Creating an Install Configuration File
For multiple installs, you can open a text editor, such as Notepad, and create an install configuration file that contains a list of arguments you wish to use. When creating an install configuration file, you must list each argument on a separate line.
Example Install Configuration File
Once created, you can give the file any name you want. You can then begin the installation by adding the filename to the --installcfg argument. The example below shows the command line argument to install OSE package 27 using a install configuration file named Install.txt located on the C: drive:
ose_r184.108.40.206p27.exe -a --installcfg=c:Install.txt
Installing the TT Gateway Software via the Command Line Interface
To begin the command line installation:
- Download the package executable file from the TT Customer Portal. To simplify the install, place the file on the server’s <root drive>.
- Open a command window by selecting Run on the Start menu and typing CMD.
- When the command window appears, use the cd <root drive>: command to navigate to the location of the executable.
- Enter the name of the executable file followed
by -a and
the arguments you wish to use.
Example Installation Arguments for the OSE Gateway:
ose_r220.127.116.11p27.exe -a --installroot=c:program filestt --exhangename=OSE-B --reboot=force
causes the OSE Gateway installation to perform the following:
- The Gateway installs into the c:program filestt directory
- The Exchange-Flavor equals OSE-B
- The server automatically reboots after the install completes
Suppresses the Browse for aconfig.xml dialog box and uses the provided network aconfig.xml file.
Using this argument causes the installation to update the revision count on the existing network aconfig.xml file.
Do not use the ovr command when supplying an existing network aconfig.xml file.
Suppresses the Available Exchange Names dialog and sets the Exchange-Flavor for the OSE Gateway.
Sets the server’s behavior following the installation. The --reboot command uses the following values:
If the --reboot command is not present, the installation exhibits the default behavior.
Sets the installation to not add desktop icons.
--ttmdcfg =ttmd.cfg, ovr
Sets the location of the ttmd.cfg file. You must set this value equal to ttmd.cfg.
In addition, you must add the ovr argument to overwrite an existing ttmd.cfg file.
Install Location Arguments
The following arguments only apply if this is the first TT product installed on the server. Subsequent installations automatically write to an existing TT folder, even if you supply the following arguments.
--installroot = [path]
Sets the directory path for all install files and folders and suppresses the prompt for installation path during first time installations.
--installconfig = [path]
Suppresses the Customize Destination Folders dialog and sets the location for the hostinfo.cfg, custommultipliers.cfg, ttchron.ini and ttclean.ini configuration files.
Also, this argument sets the location of additional TT component configuration files (i.e., ttmd.cfg, DNModifications.cfg).
--installdata = [path]
Sets the location for system data files.
--installuserdata = [path]
Sets the location for user data files.
--installlog = [path]
Sets the location for log files.
--installpathlist = [pathlist]
Sets the location for all files listed above (i.e., configuration, log, user, and system data files). The value of this parameter must equal a comma separated list of installation paths that must include the installroot and must appear in the following order: installroot,installconfig,installlog,installuserdata,installdata
Any omitted values causes those files to be written to the installroot location.
You can not add this argument to an installation configuration file.