In general, each Java ES system service component shown in Figure 2–3 depends on components below it in the infrastructure and supports components above it. These dependency and support relationships are a key factor in designing logical architectures.
Table 2–1 shows the specific relationships between the Java ES system service components, listed from top to bottom, as shown in Figure 2–3.
Table 2–1 Relationships Between Java ES System Service Components
Component |
Depends On |
Provides Support To |
---|---|---|
Portal Server |
Application Server or Web Server Access Manager Directory Server If configured to use corresponding Channels: Calendar Server Messaging Server Instant Messaging | |
Messaging Server |
Directory Server Access Manager (for single sign-on) |
Calendar Server (for email notifications) Portal Server (for messaging channel) |
Instant Messaging |
Directory Server Access Manager (for single sign-on) |
Portal Server (for instant messaging channel) |
Calendar Server |
Directory Server Messaging Server (for e-mail notification service) Access Manager (for single sign-on) |
Portal Server (for calendar channel) |
Access Manager |
Application Server or Web Server Directory Server |
Portal Server If configured for single sign-on: Calendar Server Messaging Server Instant Messaging |
Application Server |
Message Queue Directory Server (for administered objects) |
Portal Server Access Manager |
Message Queue |
Directory Server (for administered objects) |
Application Server |
Web Server |
Access Manager (for access control) |
Portal Server Access Manager |
Directory Server |
None |
Portal Server Calendar Server Messaging Server Instant Messaging Access Manager |
Service Registry |
None |
Applcation Server-based components |