ignite.1m (2012 03)

i
ignite(1M) ignite(1M)
NAME
ignite - manage an Ignite-UX server
SYNOPSIS
/opt/ignite/bin/ignite
[config|
version|client|ui][options ]
DESCRIPTION
The
ignite command is used to manage Ignite-UX server operation and control HP-UX client systems
managed by the Ignite-UX server.
The
ignite command may be used to start a user interface for interactive management of the server
and client systems. Normal interactive use of the ignite command is documented in the ignite-ui(1M)
manual page.
The
ignite command may also be used as a command line interface for programmatic control of the
Ignite-UX server. Use of the ignite command is recommended for Ignite-UX server programmatic con-
trol over use of other Ignite-UX server commands and direct file manipulation. XML formatted output is
provided to simplify program integration and allow future enhancements. Command line options are
used to simplify control.
The
ignite-* command manual pages provide details regarding options and data content for program-
matic control. You should also consult Ignite-UX White Papers and other manuals for best practice infor-
mation regarding use of the ignite command for programmatic control and Central Management
Server (CMS) integration.
The
ignite command supports the following major modes of operation:
version
Reports Ignite-UX server version information. See ignite-version (1M).
config
Reports configuration clauses available on a Ignite-UX server for use by client install. See
ignite-config(1M).
client
Provides client configuration details, controls client install, and reports client install
progress/status. See ignite-client (1M).
ui Runs Ignite-UX user interface. This mode is the default if no major mode is explicitly
specified. See ignite-ui (1M).
Minor modes are used to request variations of major mode operations. For example:
ignite config
list lists available Ignite-UX server configuration clauses.
If no major mode is specified, the Ignite-UX user interface will be run. See ignite-ui (1M).
Programs parsing XML output should be written to anticipate that new sections and attributes may be
added in the future. Programs should be written to expect that detailed formatting and line breaks may
also change. In general, programs should use XML parsing rather than string processing whenever possi-
ble.
Note that flat mode output is provided in some cases. This format is intended for interactive viewing of
output by users. In general, flat format output should not be used for programmatic control since future
enhancements may result in content and format changes which are incompatible with prior flat format
parsing.
RETURN VALUE
ignite returns the following values:
0 Success
1 Error
2 Warning
EXAMPLES
See the manual pages regarding major mode of operation for specific examples of command use.
AUTHOR
Ignite-UX was developed by the Hewlett-Packard Company.
HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1