are:
• cfgsa
• config
• distaa
• install
• install + +
• minst
• mrgri
The approach is structural, not task-oriented. The format used is
similar, but not identical, to the format used for UNIX man pages.
AA
Example
Tool Reference
cfgsa
cfgsa AA
The cfgsa tool (AAlinstaU/tools/cfgsa) is an interactive tool used to create selection and override files for a product in an Authorized Area.
The parameters are as follows:
Specify the pathname of the Authorized Area that contains the product(s) for which you want to create selection and/or override files.
To begin an interactive cfgsa session for the products in the Authorized Area Iiserver/aa,
Ilserver/aa/instaU/tools/cfgsa Iiserver/aa
With cfgsa, you can create a selection file and a corresponding override file for a product, or create just an override file. In both cases, the product or at least the product's release index must reside in the specified Authorized Area. The process is entirely optional. For some products, most notably Do-main/OS, HP supplies several predefined selection and override files (described in the product's release notes). You may find it easier and suffi-cient to use predefined files rather than create your own.
Creating a Selection-Override File Pair
With cfgsa's generate command, you can create a selection file and a corre-sponding override file in the current directory. The selection file defines a subset of a product of your choosing. The override file defines a set of config-uration options that are consistent with the reduced set of product
components.
After you remove the original product (or the product's release index) from the Authorized Area, you can supply the pathname of the selection file as a
Tool Reference
distribution media into the Authorized Area. This enables you to save disk space on the Authorized Area node by not loading components of a product that you don't need in your environment. You then make the corresponding override file active, by copying it or moving it to the Authorized Area's in-stall/overrides directory and naming it ri.apollo~roduct_name.v.version. This procedure is fully described in Chapter 7.
Creating an Override File Only
With cfgsa's save command, you can create just an override file for a product.
The override file restricts the product's configuration choices presented to users by the config (or install + + ) tool. Also, if a user installs a product with a configuration file created prior to the restrictions, the restrictions defined by the override file take precedence over any configuration choices specified in the configuration file but not allowed by the override file.
You can use override files to prevent users from installing certain product subcomponents or to force users to install subcomponents in a certain way -as a link to another node, for example, rather than a local copy. This enables you to precisely control how products are installed and to make the most effi-cient use of disk space throughout the network.
The save command creates override files with pathnames of the form
AA/in-stall/overrides/ri.apollo~roducC name.v.version. Placing an override file in the install/overrides directory and naming it this way makes it active, meaning the restrictions immediately take effect.
cfgsa Commands
When you invoke cfgsa, an interactive configuration session is started. A CFGSA> prompt appears, at which you enter cfgsa commands. A description of each of these commands follows. Although there are several commands, the basic process is one where you select a single product (using select), de-fine the configuration constraints for the selected product (using constrain), and then save these constraints (using save to create an active override file, or generate to create a selection file-override file pair). You can then repeat this process for other products in the Authorized Area.
The commands are shown here in lowercase, but you can enter them in up-per, lower, or mixed case. You can also abbreviate them to the point of uniqueness. For example, you can enter a instead of available.
Tool Reference
available Display a list of the products available in the Authorized Area specified on the command line. The name and version number of each prod-uct is listed. cfgsa automatically executes an available command when it starts up.
constrain Begin a constraint session for the currently selected product.
cfgsa displays the configuration questions that are shown to a user when a user runs config or install + + to configure the product, and the possible an-swers that a user can supply. The questions shown are those defined by the product's release index, as constrained by any active override file for the product (this can be a predefined override file or one you created previously with cfgsa).
cfgsa pauses after each configuration question and prompts you to enter one of three types of constraints: answer, limit, or user. Keep in mind that the meaning of each of these responses depends in part on whether you subse-quently use the save command (create an override file only) or the generate command (create a selection file and corresponding override file). If you use save, the constraints you define apply only to the configuration questions dis-played to a user. If you use generate, the constraints also define a product subset that you can load from media with distaa. Depending on the particular configuration question and your responses, the results may effect only the configuration process prior to installation and not what gets loaded into the Authorized Area.
answer Answer the question for the user; cfgsa prompts you to enter the answer of your choice. (If the question asks if a particular product subcom-ponent is to be installed as a link, versus a local copy or not at all, and you preanswer the question as link, cfgsa also prompts you for the name of the link node.) The answer you supply becomes the answer to the configuration question. When a user configures the product, the user does not see the question at all. If you preanswer a question concerning the installation of a product subcomponent as none or no, and you subsequently create and use a selection file that reflects the constraints, the subcomponent is not loaded from media. Similarly, if you specify that just one of a number of related objects is to be installed, use of the resultant selection file causes only that object to be loaded from media.