Sun Update Connection - Enterprise 1.0 Administration Guide

Servers in the Solution

When an agent registers with the dependency manager (DM), it downloads the rules and the components from the knowledge base. The system dependency server verifies that the knowledge base is updated from the universal server, and in turn, the DM updates the agents. The DM also updates the console, to give you an easy-to-read hierarchy of available components.

In a simplified explanation, the applications work together as follows:

  1. Agents and consoles download the rules and components from the knowledge base.

  2. After you create a job on the console, the dependency manager picks up the job and distributes it to the selected agents.

  3. Each selected agent runs the dependency resolver that uses the rules to find the most cost-efficient solution for its own managed host.

  4. The agents use certified components to complete the job.

  5. The job results are sent to the dependency manager, which updates the console and the log database.

Server Security

Sun Update Connection – Enterprise has a variety of security measures integrated into its solution.

Table 7–1 Integrated Server Security

Key Encryption 

Communications between the dependency manager and the agents and console are protected by a private/public key encryption algorithm.

Proxy Support 

Sun Update Connection – Enterprise supports HTTPS web proxy servers, enabling another level of security to updates from the universal server.

Internet Protection 

All Internet communications are protected by SSL and certificate verification.

All communications from the agents are proactive; the system dependency server pulls only from the universal server, never pushes data to it. 

Component Security 

Every component available for download from the universal server is certified. You cannot download Trojan horses or other exploits that are disguised as useful software.