Setting Up Remote Operations

SD-UX uses Access Control Lists to authorize anyone who is attempting to create, modify, or read software products in a depot or to install software to a root file system. (ACLs are discussed in detail in Chapter 9: “SD-UX Security ”.)

You can enable SD to manage software on remote systems. To let the root user perform operations on a remote target (also called the host or agent) from a central SD controller (also called the central management server or manager node):

Set up the root, host, and template Access Control Lists (ACLs) on the remote machines to permit root access from the controller system. To do this, run the following command on each remote system:
# /usr/lib/sw/mx/setaccess controller
NOTES:
- 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.
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.

Setting Up Remote Operations

Technical documentation

» Table of Contents

» Glossary

» Index