Start The Ignite-Ux Server - HP 9000 Manual

Configuring an Ignite-UX Server
Setting Up an Ignite-UX Server
2. The depot server name (in this example hpfcxxx.hp.com) should be
NOTE The make_config command will need to be re-run each time new
software is added or modified in the depots.
If the source is not an SD depot, the make_config command is not
For non-SD application
software:
applicable. You will need to create a unique config file that references the
non-SD software. A sample of a config file that does a non-core archive
can be found at the following location:
1. Copy this file first to /var/opt/ignite/data/Release/configx.
2. After copying and editing this file, you can use manage_index to

Start the Ignite-UX Server

• Run ignite to complete the configuration and to start the server
70
/opt/ignite/bin/make_config -s hpfcxxx.hp.com:/depots/compiler -
c \
/var/opt/ignite/data/Rel_B.10.20/compilers_cfg
/opt/ignite/bin/manage_index -a -f /var/opt/ignite/data/Rel_B.
10.20/compilers_cfg
replaced with the server you have the SD software on. Note that the
depot server can be a different system from the Ignite-UX server.
The make_config tool constructs Ignite-UX config files which
correspond to SD depots. When an SD depot is used as part of the
Ignite-UX process, it must have a config file which describes the
contents of the depot to Ignite-UX. This command can automatically
construct such a config file, when it is given the name of an SD depot
to operate on. This command should be run when adding or changing
a depot which will be used by Ignite-UX.
The manage_index tool is used to manipulate the
/var/opt/ignite/INDEX file. This utility is primarily called by
other Ignite-UX tools but can also be called directly.
/opt/ignite/data/examples/noncore.cfg
Then make the changes to the copy in that directory.
insert a reference the copy of the configuration in the following
location:
/var/opt/ignite/INDEX
process. Type the following:
/opt/ignite/bin/ignite
Chapter 4