A | |||
about | |||
Java ES ( ) ( ) | |||
SunWeb ( ) | |||
this case study ( ) | |||
Access Manager, about ( ) | |||
access zones, as part of architecture ( ) | |||
accessing SunWeb ( ) ( ) | |||
over the corporate network (SWAN) ( ) | |||
over the public Internet ( ) | |||
Application Server, about ( ) | |||
architecture | |||
described graphically ( ) | |||
process for developing ( ) | |||
availability requirements ( ) |
B | |||
blogs channel ( ) ( ) | |||
business and technical requirements ( ) | |||
business case for SunWeb ( ) | |||
business objectives achieved ( ) |
C | |||
calendar channel ( ) ( ) ( ) | |||
Calendar Server ( ) | |||
calendar service, components that provide ( ) | |||
capacity requirements ( ) | |||
classes of users ( ) | |||
comments about this document ( ) | |||
component instances | |||
in redundancy strategies ( ) | |||
multiple instances to satisfy quality of service requirements ( ) | |||
computer hardware | |||
assessing needs ( ) | |||
in SunWeb ( ) ( ) ( ) | |||
specifying ( ) | |||
configuring Java ES ( ) | |||
consolidation of services ( ) | |||
content delivery ( ) ( ) ( ) | |||
content management system (CMS) ( ) ( ) | |||
content providers ( ) |
D | |||
demilitarized zone (DMZ), in SunWeb deployment ( ) | |||
deployment | |||
benefits of ( ) | |||
overview ( ) | |||
planning ( ) | |||
requirements ( ) | |||
deployment architecture | |||
defined ( ) | |||
for the SunWeb deployment ( ) | |||
quality of service requirements are factored in ( ) | |||
use of redundancy strategies ( ) | |||
deployment scenario | |||
defined ( ) | |||
for the SunWeb deployment ( ) | |||
desktop, portal ( ) | |||
Directory Server, role in user login ( ) | |||
Directory Server, about ( ) | |||
Directory Server multimaster replication, in deployment architecture ( ) | |||
documentation, Java ES ( ) |
F | |||
features | |||
blogs channel ( ) ( ) | |||
calendar channel ( ) ( ) ( ) | |||
file access ( ) | |||
mail channel ( ) ( ) ( ) | |||
mobile access ( ) | |||
search ( ) ( ) | |||
secure remote access (SRA) ( ) | |||
feedback about this document ( ) | |||
file access, service requirements ( ) | |||
file access service, components that provide ( ) | |||
firewalls, and network topology ( ) |
G | |||
goals of SunWeb ( ) ( ) ( ) | |||
graphical view (screen capture) ( ) | |||
growth of user base ( ) |
H | |||
hardware, in SunWeb ( ) ( ) ( ) | |||
hardware, specifications for ( ) |
I | |||
installer, role in establishing LDAP schema ( ) | |||
installing Java ES ( ) | |||
integration of services ( ) | |||
IP addresses | |||
private ( ) | |||
to establish network topology ( ) |
J | |||
Java ES components, in SunWeb ( ) ( ) | |||
Java ES documentation and resources ( ) |
L | |||
LDAP directory tree, specification for ( ) | |||
LDAP framework ( ) | |||
LDAP schema | |||
specifications for ( ) | |||
to support Access Manager single sign-on ( ) | |||
to support portal services ( ) | |||
load balancers, used to bridge subnets ( ) | |||
load balancing | |||
as part of security strategy ( ) ( ) | |||
in deployment architecture ( ) ( ) | |||
logical architecture | |||
defined ( ) | |||
for the SunWeb deployment example ( ) |
M | |||
mail and calendar services, Portal Server channels ( ) | |||
mail channel ( ) ( ) ( ) | |||
Messaging Server ( ) | |||
messaging service, components that provide ( ) | |||
mobile access ( ) ( ) | |||
multitier architecture ( ) | |||
MySales and MyMarketing portals ( ) ( ) |
N | |||
need for SunWeb ( ) | |||
NetFile ( ) | |||
Non-Java ES software, in deployment ( ) ( ) ( ) | |||
number of users, SunWeb ( ) ( ) |
O | |||
operating system, specifications for ( ) | |||
Opteron hardware ( ) ( ) ( ) ( ) | |||
overview, of deployment ( ) |
P | |||
performance requirements ( ) | |||
planning a deployment ( ) | |||
platform, SunWeb ( ) | |||
portal desktop, service requirements ( ) | |||
Portal Server, about ( ) | |||
Portal Server channels, mail and calendar services ( ) | |||
Portal Server Secure Remote Access, role in security strategy ( ) | |||
Portal Server Secure Remote Access, services provided ( ) |
Q | |||
quality of service requirements, factored into deployment architecture ( ) | |||
quality of service requirements, described ( ) |
R | |||
redundancy strategies, used to satisfy quality of service requirements ( ) | |||
reliability, achieved through component redundancy ( ) | |||
remote file systems, operating on ( ) | |||
requirements | |||
Access Manager ( ) | |||
availability (uptime) ( ) | |||
blogs channel ( ) | |||
business and technical ( ) | |||
calendar channel ( ) | |||
capacity ( ) | |||
detailed service ( ) | |||
employee usage ( ) | |||
file access ( ) | |||
mail channel ( ) | |||
mobile access ( ) | |||
performance ( ) | |||
portal desktop ( ) | |||
remote access ( ) | |||
scalability ( ) | |||
search ( ) | |||
security ( ) | |||
single sign-on ( ) ( ) | |||
role-based access ( ) ( ) ( ) ( ) | |||
RSS provider ( ) |
S | |||
scalability requirements ( ) | |||
satisfied in the architecture ( ) | |||
screen capture, SunWeb main page ( ) | |||
search engine ( ) ( ) | |||
secure remote access (SRA) ( ) ( ) ( ) ( ) | |||
security | |||
authentication ( ) | |||
firewalls in architecture ( ) | |||
use of hardened computers ( ) | |||
use of load balancers ( ) ( ) | |||
use of network topology ( ) ( ) | |||
use of Portal Server Secure Remote Access ( ) | |||
use of private IP addresses ( ) | |||
use of subnets ( ) | |||
security requirements ( ) | |||
implementing with network topology ( ) | |||
strategies for satisfying ( ) | |||
service requirements, detailed ( ) | |||
services, integration and consolidation of ( ) | |||
services, overview ( ) | |||
single sign-on ( ) ( ) ( ) | |||
software, in SunWeb ( ) ( ) | |||
software, non-Java ES ( ) | |||
Solaris 10 OS ( ) ( ) ( ) ( ) | |||
specifications | |||
for computer hardware ( ) | |||
for LDAP directory tree ( ) | |||
for operating system ( ) | |||
user management ( ) | |||
Sun Fire x64 servers ( ) ( ) | |||
SunWeb | |||
about ( ) | |||
benefits of ( ) | |||
Collaboration service ( ) | |||
content ( ) ( ) ( ) | |||
graphical view (screen capture) ( ) | |||
number of users ( ) ( ) | |||
platform ( ) | |||
swAM1–swAM2, hardware specifications ( ) | |||
swAM3 — swAM8, hardware specifications ( ) | |||
swPS1–PS8, hardware specifications ( ) | |||
swSRA1–6, hardware specifications ( ) |
T | |||
technical and business requirements ( ) |
U | |||
uptime requirement ( ) | |||
usage patterns ( ) | |||
for the SunWeb deployment ( ) | |||
user base growth ( ) | |||
user management, specifications for ( ) | |||
users | |||
classes of ( ) | |||
login interactions ( ) | |||
number of ( ) ( ) |
X | |||
x64 servers ( ) ( ) |
Z | |||
zones, access ( ) ( ) ( ) | |||
zones, Solaris ( ) ( ) ( ) ( ) |