HP-UX Reference (11i v2 07/12) - 1M System Administration Commands N-Z (vol 4)

s
swa-step(1M) swa-step(1M)
NAME
swa-step: swa - advanced control of Software Assistant execution steps
SYNOPSIS
swa step inventory [-s inventory_source]
[
-q[q[q
]]] [-v[v]] [[-option] -?][
-x option=[value|-?]] [-X option_file]
swa step catalog
[-q[q[q
]]] [-v[v]] [[-option] -?][
-x option=[value|-?]] [-X option_file]
swa step analyze [-a analyzer][
-s inventory_source]
[
-q[q[q]]] [
-v[v]] [[-option] -?
][-x option=[value|-?]] [-X option_file]
swa step report [-r stdout_report_type]
[
-q[q[q]]] [
-v[v]] [[-option] -?][
-x option=[value|-?]] [-X option_file]
swa step download [-p][
-t target_depot]
[
-q[q[q
]]] [-v[v]] [[-option] -?][
-x option=[value|-?]] [-X option_file]
swa step depot [-p]-ttarget_depot
[
-q[q[q]]] [-v[v]] [[
-option] -?][-x option=[value|-?]] [-X option_file]
DESCRIPTION
The
swa step command supports many advanced use cases. The swa report and swa get com-
mands are actually made up of multiple steps.
swa step allows a single step of these commands to be
executed. For example, swa report normally executes the following steps (in order): inventory, cata-
log, analyze, and report. The swa step report command can be used to create different standard out-
put reports, without having to redo analysis. Additional examples and use cases, are provided below.
swa step inventory
Create an inventory of the software installed on a system or resident in a depot. This inventory is
stored in the cache subdirectory of the directory specified by the user_dir extended option (the
filename is of the form "swa_inventory_<number>.xml"). Example use case: If the system-to-be-
analyzed and the analysis system are on isolated networks, run
swa step inventory on the to-
be-analyzed system to create an inventory file. Then copy that file (for example, burn a CD) to the
cache directory on the analysis system.
swa step catalog
Download a catalog of meta data about potential issues and their recommended resolutions. This
catalog is stored in the cache directory of the directory specified by the user_dir
extended
option (the default filename is
swa_catalog.xml
). Example use case: If the system to perform
analysis has no access to the Internet, manually download the catalog to a system with Internet
access. Then copy the catalog (for example, on a USB drive) to the cache directory on the analysis
system.
swa step analyze
Given the results of running swa step inventory and swa step catalog, analyze the
inventory and come up with recommended resolutions to the issues found (see the Security Considera-
tions section). The analysis results are stored in the cache directory of the directory specified by
the user_dir extended option (the default filename is swa_analysis.xml). Example use case:
Run swa step analyze at different times, each time specifying a different set of analyzers and a
different analysis file.
swa step report
Given the results of running swa step analyze, format a report. Example use case: Run swa
step report
at different times, each time specifying a different standard output report format.
Another example is running it at different times on each analysis file created by different runs of swa
step analyze
.
swa step download
Given the results of running swa step analyze, download software recommended by the
analysis (in the analysis file). The software is downloaded into a directory controlled by the
swcache extended option. Example use case: If the analysis system does not have Internet access,
copy the analysis file to a system with Internet access, and run the swa step download com-
mand on that system.
swa step depot
Given the results of running swa step analyze and swa step download, unpack and copy
HP-UX 11i Version 2: December 2007 Update − 1 − Hewlett-Packard Company 397