Job Management Partner 1/Software Distribution Automatic Installation Tool Description and Reference
The following shows how to customize a template, taking the template for Microsoft Office Project 2003 as an example. Note that the comment Change the following processing as required is written for the portions that must be changed for customization. Find this comment to locate the portions to be changed.
The following shows how to change the values of the four properties listed below.
In the template, the processing to set these properties is commented out in the MAIN section. To enable the properties, you must delete the comment symbols from the lines. The values of the enabled properties are set in global variables for JP1/Software Distribution by using the Package Information tool.
To set properties:
The template contains a definition to use the TransformList.mst file that exists in the same directory as MSI files as a transform. The following describes how to change the transform definition.
If you want to add or change the command line options and properties that are not covered in (1) and (2) above, modify the DEFINE and MAIN sections to define the command line that you want to execute.
To customize the template to create an AIT file for installing other software, specify the package information for the desired software in the PACKAGE_INFO section of the template. The Package Information tool is useful for changing the PACKAGE_INFO section. For details about how to use the tool, see 2.5 Generating the PACKAGE_INFO section.
For software that supports Windows Installer, specify the name of the MSI file as the installer name. Use the relative path from the packaging-target directory to specify the MSI file name.
The options and properties to be specified in the MSIEXEC command line differ depending on the software to be installed. Modify the DEFINE and MAIN sections according to the command line for the software. Also, change the file name and directory of the transform according to the command line for the software.
To use the MSIEXEC command in an AIT file, the MSIEXEC command line must be specified as an argument of the DMPWINIS command. The following figure gives an example of specifying the DMPWINIS command.
Figure E-5 Example of using the DMPWINIS command
The DMPWINIS command acquires the installation result (success or failure) and notifies the client of the result. If the installation was successful, the client is notified of 0, and if the installation was not successful, the client is notified of a value other than 0. You do not need to code the processing of result notification in the AIT file. However, result notification about whether the DMPWINIS command was successfully started must be coded in the AIT file.
When the DMPWINIS command is used in an AIT file, use a hexadecimal value from 01 to 29 or from D0 to FF as the result notification code sent using AIT_PostMessage in the AIT file. Other values have been reserved by JP1/Software Distribution.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.