EXAMPLE 1 FOR A T2U - CONFIGURATION FILE 
The Setup of the Java 2 run time version 1.4.2_05 consists of a EXE file j2re 
1_4_2_05-windows-i586-p.exe. Thus the installation program the user not also 
one torments, can unnecessary questions the Java Runtime Setup with the switch/s start. 
Then the Setup runs in "silent so mentioned" or "unattended" mode and places none 
Questions more. That applies generally also to other Setups, those by InstallShield 
were provided. If you start the Setup with the switch /?, see to the following dialogue 
The start of the Setups with the switch/L1031 /? brings a located version of this 
Dialogue: 
Additionally to/L and/S switches we will use still/V switch, there it us 
the possibility gives to hand arbitrary parameters over for msiexec.exe. More over those 
One knows switches of Setups, which were provided by InstallShield, under 
http://support.installshield.com/kb/view.asp?articleid=Q105473 look up. 
Thus Java Runtime Setup looks start about in such a way: 
j2re-1_4_2_05-windows-i586-p.exe/L1031/s/v"" 
One of the most important switches the msiexec.exe is/q switch. For all MSI Setups, those 
by T2U to be installed, we recommend him in the form/qb! or/qb -!. that means 
Basis UI without breaking switch off. More over the switch of msiexec.exe one can do 
under URL http://msdn.microsoft.com/library/default.asp?url=/library/enus/
look up msi/setup/command_line_options.asp. 
Each MSI file contains a Property table, which contains some important parameters 
of the Setups. During the expiration of set UP further Properties is set. Properties, of them 
Names only large letters contained, are Public so mentioned Properties. All Public 
Properties can be changed by parameters in the starting line. They can under 
http://msdn.microsoft.com/library/default.asp?url=/library/enus/
msi/setup/configuration_properties.asp some important configuration parameters 
look up. From general Public Properties we become ADD-LOCAL and REBOOT 
Parameters with the installation of the Java Runtime Setups use. The full 
Command line will look in such a way: 
j2re-1_4_2_05-windows-i586-p.exe/L1031/s/v"/qb!ADDLOCAL=ALL REBOOT=ReallySuppress 
IEXPLORER=1 NETSCAPE6=1 MOZILLA=1 WEBSTARTICON=0 JAVAUPDATE=0 " 
ADDLOCAL=ALL it means that all component are locally installed. Otherwise become 
installs not all character fonts. 
REBOOT=Supress or REBOOT=ReallySupress means that the Setup in no case 
the computer will again start. If the Setup will state that a restart necessarily 
is, the Setup will set only the exit code (ERROR LEVEL) to the value 3010. (see 
http://msdn.microsoft.com/library/default.asp?url=/library/en
us/msi/setup/errors_reference.asp). We recommend in principle with all Msi Setups 
To set Property REBOOT on ReallySupress. 
All other Public Properties, which we with the call of j2re-1_4_2_05-windows-i586 
p.exe or jre-1_5_0-windows-i586.exe use, are specific to the Setup and are 
under http://java.sun.com/j2se/1.4.2/docs/guide/plugin/developer_guide/silent.html and/or. 
http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/silent.html and 
http://java.com/en/download/help/silent_install.jsp documents. A selection becomes 
met, those in the dialogue 
to see is. 
For the Deinstallation of Java 2 run time we will use the following command line: 
j2re-1_4_2_05-windows-i586-p.exe/s/x/v"/qb!REBOOT=ReallySuppress " 
After the command line as well as for the installation and for the Deinstallation clarified 
is, we come to the description of the appropriate T2U-konfigurationsdatei. 
The first two lines 
< ?xml version="1.0" encoding="utf-8"? > 
< !DOCTYPE product SYSTEM "t2u.dtd" > 
form a pro log, which is usual for XML files. If it T2U configuration files by 
, do not forget you provide hand not to store the file in Utf-8 format. But e.g. in 
Note PAD must one in "memory under " in "coding " the field, coding of ANSI up 
Utf-8 change. 
The lines 3 and 17 define document element product. And its attributes name and 
version. 
The document element product two Subelemente with name start - one for those 
Installation and the other one for the Deinstallation of Java 2 run time. Each start element 
a unikales ID must have. If one the T2U-konfigurationsdatei with the help of the T2UAdmin 
Program marked, optionally also linkages for the program start can 
to be provided automatically. These are suggested in the form < product name > < version > < starting ID 
>. 
The attribute needsReboot start of the element can one of three values have "YES", 
"NO" or "DETECT". The value "YES" means that the user after that 
Product installation and/or Deinstallation is informed whether a restart is necessary. It 
it is left to the user whether he starts the computer again now or makes it later. That 
Worth "DETECT" serves to avoid unnecessary restarts. For Setups, those with the MSI 
Technology were provided, supply the Setup by exit code (ERROR LEVEL) those 
Information whether a restart is necessary. If the attribute needsReboot the value 
"DETECT" has and one the COMMAND Subelemente, the attribute 
testForSuccess="MSIERRORLEVEL", the user becomes the warning over those 
Necessity for a restart get only if it announces the Setup. 
There are still further cases, how T2U can detect the necessity for a restart. That 
first the existence of the PendingFileRenameOperations of value is in the registration 
Data base under the registration key 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session manager or one 
Worth under that 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce and/or. 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx 
Keys all these values mean some actions after the next restart of the computer. 
If the attribute has needsReboot thus the value "DETECT ", T2U examines the existence of these 
To determine values over whether a restart is necessary. We recommend with each installation 
or Deinstallation, the attribute needsReboot to the value "DETECT" to set. 
The attribute messages="INSTALLATION" or messages="UNINSTALLATION" leads to it, 
that before the installation or Deinstallationsstart a Message before the user 
it appears, in order to confirm still times that the Java used 2 run time in version 
1.4.2_05 to now install and/or deinstallieren want. 
Abb. 61 
Abb. 62 
If the administrator provides a package, where no messages are necessary, one sets that 
Attribute of messages on "NO". Two further permissible possibilities for the value of the 
messages attribute are "START" and "CUSTOM". The value "START" leads to one 
Standard dialogue over the program start. The value "CUSTOM" for the attribute of messages 
can be used if standard messages are to be changed. In this 
To case we recommend the block with customMessages, the 6 user-defined messages 
describes, by T?Admin to provide (see next chapter). 
The lines 5-9 and 12-15 define the element COMMAND. Several COMMANDS can do  
Elements follow one behind the other. Each COMMAND element describes a program, 
which starts the T2U-dienst. The element COMMAND has 4 attributes:   cmd, switches, 
COMMAND type and testForSuccess. The attribute cmd defines a relative path to that 
Program or the batch file, which is started. The attribute of switches defines those 
Parameter of the program. The attribute COMMAND type should be "EXE " or "CMD ". That 
Worth "CMD" leads to the fact that the window upon the expiration of batch is hidden. Third 
possible value "EXE16" is interpreted to time exactly the same as "EXE ". The attribute 
testForSuccess it defines the way over which the T2U-dienst can determine whether the expiration 
from the started program was successful. There is permissible four different values: 
ERROR LEVEL, NOINFO, MSIERRORLEVEL and CUSTOM. 
For the installation programs it is typical that the exit code (ERROR LEVEL) 0 with that 
successful installation one returns. Another value means an error, and 
the error code is returned as exit code. In this case is 
testForSuccess="ERRORLEVEL" to be used. 
There are well-known exceptions of the error level rules. For example Windows has 
Installer Setup (MSI Setup) three different exit codes, which interpret as successful 
will could: ERROR_SUCCESS (0), ERROR_SUCCESS_REBOOT_INITIATED (1641) 
and ERROR_SUCCESS_REBOOT_REQUIRED (3010) (see 
http://msdn.microsoft.com/library/default.asp?url=/library/enus/
msi/setup/errors_reference.asp). Considers testForSuccess="MSIERRORLEVEL".
The value testForSuccess="NOINFO" is to be used if no information 
over the way admits are, how one could determine the success of the program sequence. 
If none described above of the values of testForSuccess fits, around success 
the program to recognize, the value can be used testForSuccess="CUSTOM ", 
in order details to describe, when the program sequence was successful. Can 
several freely defined values for exit codes to be tested. Beyond that that could 
Success due to the existence of a character string in a file to be determined. As 
Special cases are treated the INI files and MIF files. The next chapter enters  
Example of it.  

Go to Help Contents