This section explains how the Sun Update Connection – Enterprise components communicate with each other to fulfill Sun Update Connection – Enterprise functionality. In the following table, wherever agent is mentioned, it is true also of the console, CLI, and API.
Table 6–1 Component Communication Details
Components |
Initiator |
Data Flow |
Connection Timing |
Port & Protocol |
---|---|---|---|---|
Sun Update Connection – Enterprise server - public server |
Sun Update Connection – Enterprise server |
pull from public server |
scheduled check for new updates; on demand for agent needs; closed when task done. |
443 and HTTPS (443 is saved for HTTPS only) |
Sun Update Connection – Enterprise server - agents |
agents |
pull from KB via server |
on demand; closed when done |
HTTPS 8002 (8000-8100) |
DM - agents |
agent - login DM - alive pings both - messages |
bi-directional |
constant |
TCP/TP 8100 (8100-8200) DM listening port 8200 (8200 - 8300) agent listening for reconnect |
Sun Update Connection – Enterprise server - DM |
none |
none |
none |
none |
Sun Update Connection – Enterprise server - KB |
server |
pull from KB to fulfill jobs push of local to KB |
on demand; closed when done |
cache-type pull |
server.cgi - LRL |
server.cgi |
execute LRL |
on schedule |
application execution |