Software Distributor Administration Guide (March 2009)

• controller is the name of the central management server.
• If the remote system is running HP-UX 11.00, make sure SD patch PHCO_22526
or a superseding patch is installed on the remote system before running
setaccess.
• If the remote system is older than HP-UX 11.00, or for some other reason does
not have setaccess in place, copy the setaccess script from an HP-UX
11.11 or higher system to the remote system.
2. swinstall, swcopy, and swremove have enhanced GUI interfaces for remote
operations. Enable the enhanced GUIs by creating the .sdkey file on the controller.
Use this command:
# touch /var/adm/sw/.sdkey
NOTE: You can also set up remote access by using swacl directly on the remote
machines to grant root or non-root access to users from the controller system.
7.4 Remote Operations Tutorial
This tutorial introduces you to the remote operations user interface and to the general
flow for distributing software to other systems. Also, you will learn how to preview,
schedule, and monitor your distribution jobs. Although this tutorial uses swinstall
for the example GUI, the swcopy and swremove GUI programs are almost identical.
You can apply the knowledge you gain from this tutorial to those tasks.
You may wish to go through this tutorial more than once to experiment with variations
in the basic operations.
7.4.1 Tutorial Set-Up
1. Set up remote operations on your controller system and a remote test system. (See
“Setting Up Remote Operations” (page 157).)
2. As root on the controller system, enable the remote operations GUI:
touch /var/adm/sw/.sdkey
3. Make sure your PATH variable contains /usr/sbin. To check, enter:
echo $PATH
4. Make sure your DISPLAY variable is properly set by typing:
echo $DISPLAY
5. Ensure that the examples are installed. Enter:
swlist SW-DIST.SD-EXAMPLES
6. Create the depot containing example package (i.e., SD-DATABASE):
cd /usr/lib/sw/examples/swpackage/depot_src
158 Remote Operations Overview