The automatic method creates most of the SXP archive files for a product, and the majority of required entries in those archive files, automatically. However, some features of the Packager and Installer can be used only if you create entries manually in the appropriate SXP archive files, after you generate the initial product. You can open and edit the archive files from the product archive window.
The following list contains a general description of the entries that you can create manually. More detailed information can be found in the descriptions of the individual SXP archive files.
The dependencies discussed here do not apply to updates (delta versions) or predecessors.
You must specify the dependency of an archive product on another archive product in the info.sxp file. There are two types of dependencies:
The product to be installed requires, that one or more other products must already be installed on the same target computer.
The product to be installed requires, that one or more other products are already installed on another computer.
To use the functions of pre- and post-install tasks, you must manually create the actions.sxp file. To create this file, right-click an empty place in the archive file window, in the Product archive. Choose the Create archive file option, and select actions.sxp from the displayed list of archive files.
To add the pre-and post-install tasks to the product, right-click an empty place in the archive file window, in the Product archive. Choose the Import archive file option, and browse for the file to import. See Importing Archive Files.
When you use the automatic method of packaging, the Packager creates an ascnnnn.sxp archive file for each ASCII file that was specially labeled during the configuration of the reference system, if the installation causes any changes in this file.
In addition, the Packager creates two scripts (ascnnnn.ins and ascnnnn.dei) to modify the ASCII file during the installation or removal of the product. Such scripts are created for each ASCII file specified during configuration of the reference system ASCII files tab), except for the autoexec.bat and config.sys files. These files are treated differently, as described in Structure of the Ascnnnn.sxp Archive File.
By default, all these modifications are appended to the ASCII file on the target computer.
When you use the manual method, you can manually create and fill in an SXP archive file, such as ascnnnn.sxp as follows. Right-click an empty place in the archive file window, in the Product archive. Choose the Create archive file option, and select the desired file from the displayed list of archive files. For important instructions, see ascnnnn.sxp.
When you are using the automatic method, and a product makes user- or group-specific entries in the registry, modifies the desktop, or adds user-specific files and directories, the following SXP Archive files are created automatically:
ureg.sxp, ulinks.sxp, ufiles.sxp, udirs.sxp, and uininnnn.sxp.
Default entries are created in these files, allowing the product to be accessed by all target computer users. To restrict one or more users from accessing the product, you must edit these files manually after the product has been packaged.
If you want to restrict the access rights for files and directories (NTFS only) or Registry keys for specific users or groups, you must manually create and fill in the permis.sxp archive file.
To specify values used for only a specific target computer or group of target computers, such as the product root directory, you can use parameters to specify variables for entries in all archive files.
Normally, you enter parameters manually in SXP archive files and scripts. However, you can also use parameters in other archive files within .cmp files, and in actions. If you do so, you must specify the path name of the file in the ReplaceParams section of the files.sxp or actions.sxp archive file. See How Client Parameters are Stored.
If you want to use environment variables, you need to reference them using the syntax as follows:
$(%environment_variable%)
You can also use registry entries, as described in Using Client Parameters to Access System-specific Registry Values.
| Copyright © 2014 CA Technologies. All rights reserved. |
|