Portal Server System Communication Links
Figure 5-1 Portal Server Communication Links
| Browser |
| Gateway |
| |
|
| HTTP(s) |
|
| |
Authentication | Access Manager | Portal Desktop | Comm Channel | Search | |
Service | Admin Console | Service | |||
Service | Service | ||||
(servlet) | (servlet) | (servlet) | (servlet) | (servlet) | |
LDAP |
|
|
|
| |
Module |
|
|
|
| |
Access Manager | Access Manager |
| Access Manager | ||
SSOSDK |
| Logging SDK |
| Mgmt SDK | |
| Portal Server instance running on a web |
| |||
LDAP |
| LDAP |
| SMTP/IMAP | |
LDAP |
| User/Policy/Service | Messaging | ||
| Profile Database Server | ||||
Authentication |
| ||||
| Directory Server (LDAP) | Server | |||
Server |
| ||||
| Server |
|
| ||
In this figure, the box encloses the Portal Server instance running on Web Server technology. Within the instance are five servlets (Authentication, Access Manager administration console, Portal Desktop, Communication Channel, and Search), and the three SDKs (Access Manager SSO, Access Manager Logging, and Access Manager Management). The Authentication service servlet also makes use of an LDAP service provider module.
A user uses either a browser or the Gateway to communicate with Portal Server. This traffic is directed to the appropriate servlet. Communication occurs between the Authentication service’s LDAP module and the LDAP authentication server; between the Communications channel servlet and the SMTP/IMAP messaging server; between the Access Manager SSO SDK and the LDAP server; and between the Access Manager Management SDK and the LDAP server.
Chapter 5 Creating Your Portal Design 87
