|
|  以 PDF 格式下载本书 (964 KB)
| | | |
| Numbers and Symbols |
|
| 20\\ |
| | 80 deployments (  ) |
| | | implementation phase ( ) |
|
| 3-dimensional architecture ( ) |
|
| 80\\ |
| | 20 deployments ( ) ( ) |
| | | |
| A |
|
| Access Manager ( ) ( ) |
|
| access zones ( ) |
|
| Application Server ( ) |
|
| availability |
| | examples ( ) |
| | failover ( ) |
| | horizontally redundant systems ( ) |
| | load balancing ( ) |
| | N+1 failover system ( ) |
| | optimizing resources ( ) |
| | prioritizing ( ) |
| | quality of service requirement ( ) |
| | replication of services ( ) |
|
| availability strategies, determining ( ) |
| | | |
| B |
|
| budget limitations ( ) |
|
| business analysis phase ( ) |
| | about ( ) |
|
| business constraints ( ) |
| | budget limitations ( ) |
| | cost of ownership ( ) |
| | migration issues ( ) |
| | schedule mandates ( ) |
|
| business goals |
| | affecting deployment design ( ) |
| | defining ( ) |
|
| business requirements |
| | business goals ( ) |
| | corporate culture ( ) |
| | defining ( ) |
| | operational requirements ( ) |
| | regulatory requirements ( ) |
| | security goals ( ) |
| | service level agreements ( ) |
| | understanding users ( ) |
| | usage patterns ( ) |
|
| business service tier, multitiered architecture model ( ) |
| | | |
| C |
|
| Calendar Server ( ) ( ) |
|
| client tier, multitiered architecture model ( ) |
|
| Communications Express ( ) |
|
| component dependencies ( ) |
| | web container support ( ) |
|
| corporate culture ( ) |
|
| cost of ownership ( ) |
| | affecting deployment design ( ) |
| | | |
| D |
|
| data tier, multitiered architecture model ( ) |
|
| deployment architecture ( ) |
| | example ( ) |
|
| deployment design |
| | about ( ) |
| | factors ( ) |
| | methodology ( ) |
| | outputs ( ) |
| | project approval ( ) |
|
| deployment design phase ( ) |
|
| deployment planning |
| | about ( ) |
| | incremental approach ( ) |
| | solution life cycle ( ) |
|
| deployment scenario ( ) ( ) ( ) |
|
| Directory Proxy Server ( ) ( ) |
|
| Directory Server ( ) ( ) ( ) |
| | multi-master replication ( ) ( ) |
| | single master replication ( ) ( ) |
|
| disaster recovery plan ( ) |
|
| DMZ, external access zone ( ) |
|
| documentation |
| | Installation Guide ( ) ( ) |
| | Technical Overview ( ) ( ) ( ) |
| | | |
| E |
|
| estimating processor requirements ( ) ( ) |
| | example ( ) |
| | secure transactions ( ) |
| | use cases ( ) |
|
| examples |
| | access zones ( ) |
| | availability design ( ) |
| | deployment architecture ( ) |
| | Directory Server ( ) |
| | estimating processor requirements ( ) |
| | estimating processor requirements for secure transactions ( ) |
| | failover ( ) |
| | identity-based communications ( ) |
| | load balancing ( ) ( ) |
| | logical architecture ( ) |
| | Messaging Server logical architecture ( ) |
| | multi-master replication ( ) |
| | replication of services ( ) |
| | scalability ( ) |
| | single master replication ( ) |
|
| external access zone (DMZ) ( ) |
| | | |
| F |
|
| failover ( ) |
| | example ( ) |
| | Sun Cluster software ( ) |
|
| fault-tolerant systems ( ) |
|
| functional tests ( ) |
| | | |
| G |
|
| Glossary, link to ( ) |
| | | |
| H |
|
| horizontally redundant systems ( ) |
| | | |
| I |
|
| identifying bottlenecks, deployment design ( ) |
|
| identity-based communications example ( ) |
| | estimating processor requirements ( ) |
| | use cases ( ) |
|
| implementation phase ( ) ( ) |
| | about ( ) |
| | developing pilots and prototypes ( ) |
|
| implementation plans ( ) |
|
| implementation specifications ( ) |
|
| installation plan ( ) |
|
| installing Java Enterprise System ( ) |
|
| Instant Messaging ( ) |
|
| internal access zone (intranet) ( ) |
| | | |
| J |
|
| Java Enterprise System |
| | 20\\ |
| | | 80 deployments ( ) |
| | 80\\ |
| | | 20 deployments ( ) |
| | about ( ) |
| | access components ( ) |
| | component dependencies ( ) |
| | components ( ) |
| | custom services ( ) |
| | installing ( ) |
| | migration issues ( ) |
| | rolling out a production deployment ( ) |
| | services ( ) |
| | system services ( ) |
| | three dimensional architecture ( ) |
| | | |
| L |
|
| latent capacity ( ) |
| | scalability considerations ( ) |
|
| load balancing ( ) |
| | example ( ) |
|
| logical architecture |
| | affecting deployment design ( ) |
| | designing ( ) |
| | examples ( ) |
| | identity-based communications example ( ) |
|
| logical architectures ( ) |
|
| logical design, about ( ) |
|
| logical design phase ( ) |
|
| logical tiers, multitiered architecture model ( ) |
| | | |
| M |
|
| managing risks ( ) |
| | deployment design ( ) |
|
| Message Queue ( ) |
|
| Messaging Server ( ) |
| | example logical architecture ( ) |
| | load balancing example ( ) |
| | logically distinct services ( ) |
| | Message Multiplexor (MMP) ( ) ( ) ( ) ( ) |
| | Message Store (STR) ( ) ( ) ( ) |
| | Message Transfer Agent (MTA) ( ) ( ) |
| | Messenger Express Multiplexor (MEM) ( ) |
| | use cases ( ) |
|
| migration issues ( ) |
| | as business constraint ( ) |
|
| migration plan ( ) |
|
| multi-master replication ( ) |
| | example ( ) |
|
| multitiered architecture design ( ) |
| | | |
| N |
|
| N+1 failover system ( ) |
| | | |
| O |
|
| operational requirements ( ) |
|
| operations phase ( ) |
|
| operations plan (Run Book) ( ) |
|
| optimizing |
| | disk access ( ) |
| | resource usage ( ) |
|
| optimizing resources, deployment design ( ) |
| | | |
| P |
|
| performance |
| | identifying bottlenecks ( ) |
| | optimizing resources ( ) |
| | quality of service requirement ( ) |
|
| pilots ( ) |
| | testing ( ) |
|
| Portal Server ( ) ( ) |
| | Mobile Access ( ) |
| | Secure Remote Access ( ) ( ) |
|
| presentation tier, multitiered architecture model ( ) |
|
| processor requirements, estimating ( ) |
|
| project approval ( ) |
|
| prototypes ( ) |
| | testing ( ) |
| | | |
| Q |
|
| QoS (quality of service requirements) ( ) |
|
| quality of service requirements ( ) ( ) |
| | affecting deployment design ( ) |
| | role in deployment design ( ) |
| | | |
| R |
|
| regulatory requirements ( ) |
|
| replicating services ( ) |
|
| replication of services |
| | availability strategy ( ) |
| | Directory Server example ( ) |
|
| risk management ( ) |
|
| roll-out plan ( ) |
|
| Run Book ( ) |
| | | |
| S |
|
| scalability |
| | estimating growth ( ) |
| | example ( ) |
| | optimizing resources ( ) |
| | quality of service requirement ( ) |
| | strategies ( ) |
|
| schedule mandates ( ) |
|
| secure access zone ( ) |
|
| security |
| | estimating processor requirements ( ) |
| | optimizing resources ( ) |
| | quality of service requirement ( ) |
|
| service level agreements ( ) |
| | affecting deployment design ( ) |
| | requirements ( ) |
|
| service level requirements ( ) |
|
| serviceability |
| | optimizing resources ( ) |
| | quality of service requirement ( ) |
|
| single master replication ( ) |
| | example ( ) |
|
| SLA ( ) |
|
| solution life cycle ( ) |
| | business analysis phase ( ) ( ) |
| | deployment design phase ( ) ( ) |
| | implementation phase ( ) ( ) |
| | logical design phase ( ) ( ) |
| | operations phase ( ) |
| | technical requirements phase ( ) ( ) |
|
| stress tests ( ) |
|
| Sun Cluster software ( ) |
| | failover example ( ) |
| | | |
| T |
|
| technical requirements |
| | availability ( ) |
| | latent capacity ( ) |
| | performance ( ) |
| | scalability ( ) |
| | security ( ) |
| | service level requirements ( ) |
| | serviceability ( ) |
|
| technical requirements phase ( ) |
| | about ( ) |
| | quality of service requirements ( ) |
| | usage analysis ( ) |
| | use cases ( ) |
|
| test plan ( ) |
|
| testing |
| | functional tests ( ) |
| | pilots and prototypes ( ) |
| | stress tests ( ) |
|
| three dimensional architecture ( ) |
|
| training plan ( ) |
| | | |
| U |
|
| usage analysis ( ) |
| | affecting deployment design ( ) |
|
| usage patterns ( ) |
|
| use cases ( ) |
| | affecting deployment design ( ) |
| | estimating processor requirements ( ) |
| | identity-based communications example ( ) |
| | Messaging Server example ( ) |
|
| user management plan ( ) |
|
