PRODUCTION A CONFIGURATION FILE FOR T2U - - PACKAGE ALSO  
T2UADMIN.EXE  
Trust to User offers the possibility, a XML Konfigurationsdatei comfortably over those 
To provide user surface. The structure of the user interface looks about in such a way: 
The T2U-konfigurationsdatei is a XML file, it has elements, the one 
Document structure form. The elements of the T2U-konfigurationsdatei become in the upper 
link part of the dialogue indicated (under "document structure:"). Each element has attributes, 
in the lower left part to be indicated. Some the attributes are not mandatory, others
. Trust to User uses two types of attributes: either a freely definable text 
or a selection between a few permissible values. If all attributes of an element 
are fulfilled, the appropriate element green one marks, on the other hand red. 
An element can by one clicks on the switching surface from the document structure 
are removed. In the right top of the dialogue window permissible become 
Unterelemente indicated, those as subordinated Subelemente of the selected element 
the document structure to be added can. For example knows start the element 
several COMMANDS Unterelemente or requirements contain. If that messages 
Attribute start of the element the value CUSTOM has, then has start the element still in 
customMessages Subelement, which is indicated as Custom of messages. 
Now we describe step for step, like one a T2U-konfigurationsdatei with the help of of the 
T2U-admin to provide can. We remain like before with the example Java 2 run time 
Version 1.4.2_05. 
Step 1:   With marking the package in the dialogue 
Abb. 63 
operate a producing switching surface. 
Step 2:   Fill product the name and product version of fields: 
Abb. 64 
Step 3:   Then you fill the attributes of the starting element, which the installation of 
the Java run time version 1.4.2_05 describes 2, out. But you must as 
first the starting element in the document structure tree select. 
Abb. 65 
The attribute permissionRequired="NO" is to be used if the start 
the package for all users to be made available is. On the other hand 
before the package start each mark the authorization of the users is examined. 
User authorizations are steered by the T2UPerms.xml file. Those 
Structure of this file is described later. 
Step 4:   Fill out all attributes of the COMMAND of element. The attribute COMMAND 
you leave type untouched on EXE. The value test of the For Success of attribute 
select as CUSTOM. Automatically the Unterelement produces 
customTestForSuccess as subordinated element of the COMMAND 
Element. In the next steps we become the element 
extend customTestForSuccess with Unterelementen. Cmd you fill the field  
with j2re-1_4_2_05-windows-i586-p.exe and the field Switches with / L1031/s 
/ v"/qb! REBOOT=ReallySuppress ADDLOCAL=ALL IEXPLORER=1 
NETSCAPE6=1 MOZILLA=1 WEBSTARTICON=0 JAVAUPDATE=0/mjr1420ï 
/ L*v %TEMP%\jr1420ï.log "out. The two form together the following 
Command line: 
j2re-1_4_2_05-windows-i586-p.exe/L1031/s/v"/qb!REBOOT=ReallySuppress ADDLOCAL=ALL 
IEXPLORER=1 NETSCAPE6=1 MOZILLA=1 WEBSTARTICON=0 JAVAUPDATE=0/mjr1420ï 
/ L*v %TEMP%\jr1420ï.log " 
Abb. 66 
In the comparison with the example 1 the parameters / mjr1420ï are new and 
/ L*v %TEMP%\jr1420ï.log. The parameter/L leads to the production the log 
File %TEMP%\jr1420ï.log. The Detailisierungsgrad of the log file becomes through 
the switch/L * v posed on the highest stage. In the event of an error requests the log 
File a quantity of information about the installation procedure. This information 
can help the administrator much with the Troubleshooting. It has also its 
disadvantages. First of all is the log file, which was provided with the parameter/L*v, 
relatively long and for a beginner in Windows Installer technology somewhat 
unclearly. The WiLogUtl.exe program from the free can 
Microsoft Platform SDK very helpfully its. Nevertheless one should note that 
the Windows Installer log file with some installation programs several 
Megabytes largely to be knows and so the total installation process substantially 
to slow down can. In such rare cases the Detailisierungsgrad leaves itself 
reduce parameters by another/L. 
A further disadvantage from log files is that they contain located stringers. 
If we the log file analyze and e.g. the result of the installation 
to determine want, then we should look at the last part of the log file. It 
looks about in such a way: 
...
=== Logging stopped: 14.09.2004 17:50:35 ===
MSI (s) (10:2C): Note: 1: 1707
MSI (s) (10:2C): Product: Java 2 Runtime Environment, SE v1.4.2_05 -- Installationsvorgang
erfolgreich abgeschlossen.
MSI (s) (10:2C): Attempting to delete file C:\WINDOWS\Installer\164c7de.mst
MSI (s) (10:2C): Unable to delete the file. LastError = 32
MSI (s) (10:2C): Cleaning up uninstalled install packages, if any exist
MSI (s) (10:2C): Post-install cleanup: removing installer file
'C:\WINDOWS\Installer\164c7de.mst'
MSI (s) (10:2C): MainEngineThread is returning 0
MSI (s) (10:94): Destroying RemoteAPI object.
MSI (s) (10:F0): Custom Action Manager thread ending.
MSI (c) (70:30): Decrementing counter to disable shutdown. If counter >= 0, shutdown will
be denied. Counter after decrement: -1
MSI (c) (70:30): MainEngineThread is returning 0
=== Verbose logging stopped: 14.09.2004 17:50:35 ===
We underlined the text, which describes the result of the installation. 
If the start of the program without the switch/L1031 would run or if 
on the computer no support for the German language would be, became we 
the log file with another text receive: 
...
=== Logging stopped: 14.09.2004 17:50:35 ===
MSI (s) (10:2C): Note: 1: 1707
MSI (s) (10:2C): Product: Java 2 Runtime Environment, SE v1.4.2_05 -- Installation
operation completed successfully.
MSI (s) (10:2C): Attempting to delete file C:\WINDOWS\Installer\164c7de.mst
MSI (s) (10:2C): Unable to delete the file. LastError = 32
MSI (s) (10:2C): Cleaning up uninstalled install packages, if any exist
MSI (s) (10:2C): Post-install cleanup: removing installer file
'C:\WINDOWS\Installer\164c7de.mst'
MSI (s) (10:2C): MainEngineThread is returning 0
MSI (s) (10:94): Destroying RemoteAPI object.
MSI (s) (10:F0): Custom Action Manager thread ending.
MSI (c) (70:30): Decrementing counter to disable shutdown. If counter >= 0, shutdown will
be denied. Counter after decrement: -1
MSI (c) (70:30): MainEngineThread is returning 0
=== Verbose logging stopped: 14.09.2004 17:50:35 ===
For each software distributing system the question is over the success of the Setups 
one of the most important questions. Before the introduction of the system management 
Server 1,0 has Microsoft as interface for the Setups status MIF files 
suggested. Each Setup is as required a text file in the certain 
Statuf MIF format in temp and/or.   WINDOWS listing provide. In ours 
Example we would have gotten the following MIF file: 
START COMPONENT
NAME = "WORKSTATION"
START GROUP
NAME = "ComponentID"
ID = 1
CLASS = "DMTF|ComponentID|1.0"
START ATTRIBUTE
NAME = "Manufacturer"
ID = 1
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(64)
VALUE = "Sun Microsystems, Inc."
END ATTRIBUTE
START ATTRIBUTE
NAME = "Product"
ID = 2
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(64)
T2U Dokumentation 60 OK softR GmbH
VALUE = "{7148F0A6-6813-11D6-A77B-00B0D0142050}"
END ATTRIBUTE
START ATTRIBUTE
NAME = "Version"
ID = 3
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(64)
VALUE = "J2RE v[ProductVersion]"
END ATTRIBUTE
START ATTRIBUTE
NAME = "Locale"
ID = 4
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(16)
VALUE = "Intel;0"
END ATTRIBUTE
START ATTRIBUTE
NAME = "Serial Number"
ID = 5
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(64)
VALUE = ""
END ATTRIBUTE
START ATTRIBUTE
NAME = "Installation"
ID = 6
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(64)
VALUE = "DateTime"
END ATTRIBUTE
END GROUP
START GROUP
NAME = "InstallStatus"
ID = 2
CLASS = "MICROSOFT|JOBSTATUS|1.0"
START ATTRIBUTE
NAME = "Status"
ID = 1
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(32)
VALUE = "Success"
END ATTRIBUTE
START ATTRIBUTE
NAME = "Description"
ID = 2
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(128)
VALUE = ""
END ATTRIBUTE
END GROUP
END COMPONENT
Abb. 67 
As one sees, the MIF file contains InstallStatus in the group as value of the 
Attribute status the character string Success or Failed. These stringers become 
always in not located form written. 
In order to facilitate the production of status MIF files for Setups, installs 
Microsoft of system management server on each SMS Client ISMIF32.DLL in 
Windows listing (%SystemRoot%). In the first version had 
ISMIF32.DLL only one function InstallStatusMIF exports. SMS 2003 leads one 
further function InstallStatusMIFEx. These functions become from all 
modern installation programs uses, around a success and/or a failure that 
To announce installation. More over this Microsoft interface can do you under 
http://msdn.microsoft.com/library/default.asp?url=/library/enus/
smssdk03/hh/sms/refsms10_4qnn.asp?frame=true look up. If thus 
on all computers, which use T2U, ISMIF32.DLL in the path to find is, offers 
itself the possibility of using during the success examination the status MIF. 
If one in its enterprise the Microsoft of system management server 
, knows the Setup of the T2U-service does not use substitution of the ISMIF32.DLL 
install. 
Step 5:   Select customTestForSuccess element in the document structure tree and 
add all Unterelement.   Now you have the selection over 
different tests, it as criterion for the success of the installation 
define. 
Abb. 68 
In this example we want to define three rules as success criterion: 
1. In the log file there is a text over the success of the installation. 
2. the Setup one terminates with an exit code (ERROR LEVEL), for one 
successful Windows Installer (MSI) installation speaks. 
3. The Setup provides a status MIF file, the one information about that 
Success of the installation gives. 
Step 6:   With the analysis of the log file we assume the installation up 
a deutsprachigen or a English-language operating system runs. There 
the information about the success of the installation is located, becomes we the log 
File on two success messages scan: up 
"Java 2 run time Environment, SE v1.4.2_05 -- installation operation completed 
successfully." 
and up 
"Java 2 run time Environment, SE v1.4.2_05 -- installation procedure successfully 
locked." 
If one of these success messages appears, we go from one 
successful installation out. 
In order to code this in a form, which understands T2U, we add any a block 
the document structure and under the block two test file of elements in addition: one 
for the test on the English character string and one for the Germans: 
Abb. 69 
Step 7:   Under that all you insert block an exit code Subelement. Then you set as 
Test criterion MSIERRORLEVEL. That corresponds to the test on 0, 1641 and 3010 
(ERROR_SUCCESS, ERROR_SUCCESS_REBOOT_INITIATED and 
ERROR_SUCCESS_REBOOT_REQUIRED). If you use a Setup, 
which can supply another exit code in case of success, you can do that 
illustrate block with different Custom test exit code by one any. 
Abb. 70 
Step 8:   Under all block you insert a MIF file ton test Subelement. 
Abb. 71 
The name of the status MIF file must be identical as in/m switch 
the MSI Setups. Contents of all other fields come of the Summary 
Information Stream of the MSI file. You can do this with Orca or into that 
Characteristics of the Java 2 run time Environment, SE v1.4.2_03.msi file 
see: 
Abb. 72 
Abb. 73 
We recommend urgently, this information from the status MIF file to you 
to take out, it with the test installation gotten (see Abb. 67.) 
Step 9:   Repeat the steps from 3 to 8 and arrange you a second starting 
Tree, which describes the Deinstallation of Java 2 run time. At the end 
operate memory the switch. 
Abb. 74 
Note please that the command line with the Deinstallation as follows 
looks: 
j2re-1_4_2_05-windows-i586-p.exe/L1031/s/x/v"/qb!REBOOT=Suppress/mjr1420ü 
/ L*v %TEMP%\jr1420ü.log " 
The name of the status MIF file is jr140ü.mif and that the log file is 
%TEMP%\jr1420ü.log. The text in the German log file, according to which searched 
will is, reads: "Java 2 run time Environment, SE v1.4.2_05 -- removing 
successfully one locked." and in English: "Java 2 run time 
Environment, SE v1.4.2_05 -- rem oval completed successfully. " 
The final file and the pertinent t2u.dtd file become t2u.config in 
Package listing provides: 
































 

Go to Help Contents