Introduction

For local operations, the target consists of the local host or depots on the local host. For remote operations, the target can be one or more remote systems. A target can also contain depots and act as a source to serve other targets.

The controller programs provide the user interface for SD-UX tasks and programs. The controller’s role collects and validates data it needs to start a task and to display information on the task’s status. The controller also distributes software to remote target machines.

On each target, the SD-UX daemon runs in the background, listening for requests coming from the controller. When a request is received, the daemon schedules the SD-UX agent to perform the task. The daemon also schedules the agent to answer requests from other agent programs that want to use one of the host’s depots as a source.

	NOTE: You must restart the SD-UX daemon if you change daemon options, or the system will not recognize the changes. See “Using Command Options” for more information.

With SD-UX remote operations, you can create jobs for immediately execution or schedule them for later execution. In addition, you can browse the scheduled, active, and completed jobs using either the command line interface (with the swjob command) or the interactive interface (with the sd command).

The swconfig, swinstall, and swverify commands let you detect and enforce the use of compatible software (i.e., ensure software products are compatible with system types and operating systems). When you select multiple targets for a remote operation, SD-UX lets you select only the software compatible with all targets.

As with local operations, the swask, swconfig, swcopy, swinstall, swremove,and swverify commands support dependencies between filesets and products. If you have a software selection that specifies a dependency on other filesets or products, the command automatically selects that software. (This step is executed on the local host. You can override this policy with the autoselect_dependencies default option.)

With remote operations, dependencies are analyzed on each target and a fileset will not install if dependencies are not met on that target. (You can override this policy using the enforce_dependencies default option.)

You can use the session file command options to build, save, and reuse sessions with most commands. With remote operations, target selections are saved along with options, source information, and software selections.

SD-UX adds extra components to the GUI programs when remote operations are enabled. Otherwise, the programs are almost identical to those used for local operations. (See “Using the Remote Operations GUI”.)

Most SD-UX commands let you read lists of software selections from separate input files. With remote operations, you can also read target lists from separate files. The local controller GUI also lets you use software and target lists.

You can use the SD-UX remote operations features for patch management. You can explicitly select patches for multiple remote systems at one time. Note, however, that the patch_match_target option works with only one remote system at a time.