Software Distributor Administration Guide (March 2009)

1. (Un)configure each product.
2. Run scripts for associated filesets, checking return values.
If an error occurs, the fileset is left in the installed state. If a warning occurs, the
fileset will still be configured.
3. Update the IPD to show the proper installed or configured state.
Configure scripts must also adhere to specific guidelines. For example, these scripts
are only executed in the context of the host that the software will be running on, so
they are not as restrictive as customized scripts. For more information on scripts, see
Chapter 11: “Using Control Scripts ” (page 265).
2.2.3 Using swconfig
Syntax
swconfig [-p] [-u] [-v] [-c catalog] [-C session_file]
[-f software_file] [-Q date] [-S session_file] [-t target_file] [-x option=value]
[-X option_file] [software_selections] [@ target_selections]
Options and Operands
-p
Preview a configuration task by running it through the
Analysis Phase and then exiting.
-u
Unconfigure the software instead of configuring it.
-v Turn on verbose output to stdout and display all
activity to the screen.
-c catalog
Store copy of a response file or files created by a request
script. See Chapter 11: “Using Control Scripts ”
(page 265).
-C session_file
Run the command and save the current option and
operand values to a session_file for re-use in another
session. See “Session Files” (page 51).
-f software_file
Read a list of software selections from a separate file
instead of (or in addition to) the command line. See
“Software Files” (page 49).
-Q date
Schedules a job for the given date when remote
operations are enabled. See “Scheduling Jobs from the
Command Line” (page 148) and Chapter 7: “Remote
Operations Overview” (page 151)
-S session_file
Run the command based on values saved from a
previous installation session, as defined in
session_file. See “Session Files” (page 51).
72 Installing Software