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

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swmodify(1M) swmodify(1M)
NAME
swmodify - modify software products in a target root or depot
SYNOPSIS
swmodify [-d|-r][-p][-u][-v][-V][-a attribute=[value]] [-c catalog ][-C session_file ]
[-f software_file][-P pathname_file][-s product_specification_file|[-S session_file ]
[-x option=value ][-X option_file][software_selections][@ target_selection]
Remarks
This command supports operation on remote systems. See Remote Operation below.
For an overview of all SD commands, see the sd(5) man page by typing man 5 sd on the com-
mand line.
DESCRIPTION
The swmodify command modifies the definitions of software objects installed into a primary or alternate
root, or availablefrom a software depot. It supports the following features:
adding new objects - The user can add new bundles, products, subproducts, filesets, control files,
and files to existing objects (which will contain them).
deleting existing objects - The user can delete existing bundles, products, subproducts, filesets, con-
trol files, and files from the objects which contain them.
modifying attribute values - The user can add an attribute, delete an attribute, or change the exist-
ing value of an attribute for any existing object. When adding a new object, the user can at the
same time define attributes for it.
committing software patches - The user can remove saved backup files, committing the software
patch.
With the exception of control files, swmodify does not manipulate the actual files that make up a product
(fileset). The command manipulates the catalog information which describes the files. However, swmo-
dify
can replace the contents of control files.
Common uses of swmodify include:
adding file definitions to the existing list of file definitions in a fileset. Example: If a fileset’s con-
trol scripts add new files to the installed file system, the scripts can call swmodify to "make a
record" of those new files.
changing the values of existing attributes. Example: If a product provides a more complex
configuration process (beyond the SD configure script), that script can set the fileset’s state to
CONFIGURED upon successful execution.
defining new objects. Example: to "import" the definition of an existing application that was not
installed by SD, construct a simple PSF describing the product. Then invoke
swmodify to load
the definition of the existing application into the IPD.
Remote Operation
You can enable SD to manage software on remote systems. To let the root user from a central SD con-
troller (also called the central management server or manager node) perform operations on a remote target
(also called the host or agent):
1) Install a special HP ServiceControl Manager fileset on the remote systems. This enables remote opera-
tions by automatically setting up the root, host, and template Access Control Lists (ACLs) on the
remote machines and permitting root access from the controller system. To install the fileset, run the
following command on each remote system:
swinstall -s controller:/var/opt/mx/depot11 AgentConfig.SD-CONFIG
NOTES:
controller is the name of the central management server.
If the target is running HP-UX 10.20, use the same command but substitute depot10 for
depot11.
Targets previously set up by SD/OV to be managed by this controller do not need this step.
HP-UX Release 11i: December 2000 1 Section 1M905
___
___