CA Client Automation - 14.0

PDF
English

Frequently Asked Questions

Contents
cla140
Contents
The topics in this section provide answers to frequently asked questions.
Some Fonts are not Present on the Target Computer after Installing Word 97
Symptom:
I receive an error message stating that some fonts cannot be found on the target computer after installing an SXP product containing fonts.
Solution:
Use the Sxpfonts.exe to activate fonts on Windows NT/2000/XP and Windows 9x/Me when installing or uninstalling fonts with the Software Management Installer.
Follow these steps:
  1. Add an actions.sxp archive file and the sxpfonts.exe utility to the package.
  2. For each new font, enter three lines in the actions.sxp. See the description of the actions.sxp file for an example for sxpfonts.
    Use the sxpfonts.exe utility as follows:
    sxpfonts.exe command path
    • Command
      Enter an install or an uninstall command preceded by a hyphen:
      -i Install fonts
      -d Deinstall fonts
    • Path
      Absolute font path
    The exit codes of the sxpfonts.exe utility are as follows:
    0 = Ok
    1 = Invalid command line
    2 = Add font resource failed
    3 = Remove font resource failed
About Variables, Parameters, and Client Parameters
Symptom:
What are the purposes and differences of variables, parameters, and client parameters?
Solution:
Variables, parameters, and client parameters are all variables. Parameters and client parameters are simply more specific terms for describing the Packager-specific variables that you must know.
  • In general computing terminology, variables are frequently used in programs to represent a value that changes for different users, computers, or conditions. This value is used to control the operation of a particular function or program.
  • In packaging terminology, the variables that you should know are called parameters. There are two kinds of parameters: internal and external.
    Internal parameters are generated automatically by the Packager during the packaging process.
    The user defines external parameters usually called client parameters, after the initial packaging process is completed. These parameters customize installations. They are wildcards or placeholders for values that identify a specific target computer. Examples are the IP address and the installation path for a specific target computer. Client parameters serve as a substitute. During the installation on a target computer, they are replaced by the values defined in either internal or external parameters.
The general term parameter is used to identify both client parameters and variables, because the functionality discussed describes both terms.
Client Parameters and Packager Scripts are Required
Symptom:
Why Do I Require Client Parameters and Packager Scripts?
Solution:
You can use client parameters and scripts (written in the Packager script language) to enable flexible control of product installation or uninstallation on the target computers. Client parameters and scripts make possible both high-performance and a high degree of customization. You can use parameters for the following purposes:
  • To standardize different types of target computers, including consultant workstation, point-of-sale system, information system, and computer groups.
  • For system parameters, such as IP address, system name, and port names.
  • To control the Installer software within the archive files. For example, you can specify installation paths, dependency definitions, and registry entries.
  • For interactive control of scripts.
  • To make general product-specific files more flexible, for example, by using batch files and PERL scripts.
  • As a source of information to enable target computer-specific response files to be created from general product response files.
How Client Parameters are Stored
Symptom:
Tell me how and where client parameters are stored.
Solution:
On the Packaging Computer, all client parameters are stored in four INI files that are collectively known as the parameter archive. These files are default.ini, group.ini, pc.ini, and tree.ini. The information in these files is mirrored in the objects on the Parameter archive dialog. No client parameters are created automatically. You create and edit parameters by creating and editing the objects on that dialog. On the target computer, the parameters are stored in the param.ini file.
How the Installer Finds Parameters
Symptom:
How does the Installer find the parameters?
Solution:
On the target computer, the Installer evaluates the ParamFiles section of the Installer configuration file (sxpengxx.ini). This section specifies the file names and path names of the parameter files to be used by the Installer and the section where the Installer finds the parameters for the particular target computer. Ensure this section is filled in and processed automatically when you create, package, distribute, and install parameters using the Packager and Installer.
Sample sxpengxx.ini and param.ini files for a target computer follow:
  • Sxpeng32.ini
     
    [ParamFiles]
C:\installationpath_of_Installer\param.ini=APM10
    The param.ini file contains the names of the parameters to be used and their values. The values must not contain further variables or parameters, such as environment variables, because they cannot be resolved.
  • Param.ini
     
    [APM10]
ServerName=MyServer
How Parameters Reach the Target Computers
Symptom:
How do the parameters reach the target computers?
Solution:
The parameters are distributed to a target computer as a parameter product in the same way as a product (packaged software or data). That is, you package, register, and distribute the product, as described in Basic Steps for Packaging and Distributing Parameter Products.
How to Establish a Connection between Parameter Products and Regular Products
Symptom:
How must I proceed to establish a connection between parameter products and regular products?
Solution:
First, recall that a product means packaged software or data, while parameter product means packaged parameters.
You can optionally specify dependencies for and on the parameter product because the parameter files are packaged in a parameter product. Thus, you can specify that another product is dependent on the parameter product.
How to Discover the Version of a Parameter Set
Symptom:
How can I discover the version of a parameter set?
Solution:
When you create a new version of a parameter product, the Packager displays the current version number. The version number is incremented automatically each time you package a new version of the parameter product.
To create a new version, Select Edit, Parameter, Create parameter product from the Client parameters dialog. The Create Parameter Product dialog displays, enabling the file name to be entered. Accept the default name and version or enter new values.
Packager Scripts are Useful
Symptom:
What are Packager scripts and when do I use them?
Solution:
The Packager includes its own special script language to allow simple modifications to be performed in text files. Scripts are useful for performing the following tasks:
  • Making changes in configuration files at specific locations, such as autoexec.bat and config.sys
  • Adapting product response files
  • Modifying ASCII user files
How And Where Parameter Descriptions are Stored
Symptom:
How and where are the parameter descriptions stored?
Solution:
There are four files that store parameter settings:
  • tree.ini
    Describes the tree or hierarchy of computer groups and individual PCs. This file illustrates the PC groups and PC objects defined in the left pane of the Client parameters dialog.
  • default.ini
    Contains the default parameter names, values, types, and the ranges of values allowed. When you select the Default object on the left pane of the Client parameters dialog, these settings are displayed on the right pane.
  • groups.ini
    Contains nondefault parameter values you defined for PC groups. When you select a PC group object on the left pane of the Client parameters dialog, these settings are displayed on the right pane.
  • pc.ini
    Contains nondefault parameter values you defined for individual PCs. When you select an individual PC object on the left pane of the Client parameters dialog, these settings are displayed on the right pane.
Packager Scripts to use with ASCII Files
Symptom:
Should I use a Packager script to change ASCII files?
Solution:
To change ASCII files during installation of a product on the Packaging Computer you normally do not need a script. The Packager provides special scripts that make these changes. There are always two scripts for each ASCII file:
  • ascnnnn.ins for the installation of the file
  • ascnnnn.dei for the uninstallation of the file
However, if you want to adapt a product configuration file or change other files in addition to the changes already specified in the ascnnnn.sxp files, you can use the script language to specify these changes. For details, see Packager Scripts and Script Language.