On demand People Productivity. Architecture - functional view

Transcription

1 Architecture - functional view Page 1 Architecture 2008

2 User On demand People Productivity Components and Architecture - functional Internet FireWall Quickr + Learning Requests (Internet User) Network Dispatcher Stand-By (Edge Comp.) User Intranet Could be a physical server or a virtual server instance or a part of a virtual server (e.g. VMWare) Network Dispatcher (Edge Comp.) SSL DMZ HTTP HTTP HTTP FireWall Portal Cluster Quickr + Learning Requests (Intranet User) SSL Quickr Cluster Learning Cluster Intranet Sametime LDAP (HA) Database (Daten im SAN o. HADR) Page 2 Architecture 2008

3 Components and Architecture - Components 1. User directory - LDAP.. 2. Repository Database IBM DB2 V9.1 FP4a 3. HTTP IBM HTTP V6.1.x 4. Network Dispatcher (Load Balancer) Edge Components of WebSphere Application Preferred Operating System: Suse Linux Enterprise (32 Bit) Red Hat Linux V4 Upd.4 for Lotus Quickr V8.1 J2EE required Page 3 Architecture 2008

4 Components and Architecture - Components 1. WebSphere Portal 6.1 incl. Web Content Management Two node Cluster Use of a database (DB) as Repository DB same DB installation for Portal, Quickr and Learning, but different instances, tables Use of a LDAP as User directory same LDAP for Portal, Quickr and Learning 2. Lotus Quickr 8.1 (based on WebSphere Portal 6.0) Two node Cluster Use of a database (DB) as Repository DB same DB installation for Portal, Quickr and Learning, but different instances, tables Use of a LDAP as User directory same LDAP for Portal, Quickr and Learning 3. Learning Accelerator (2.7) (based on WebSphere Portal 6.0) Two node Cluster Use of a database (DB) as Repository DB same DB installation for Portal, Quickr and Learning, but different instances, tables Use of a LDAP as User directory same LDAP for Portal, Quickr and Learning Each cluster is independent from each other, to prevent product version conflicts. Page 4 Architecture 2008

5 Components and Architecture functional: Authoring Option... User + Authors HTTP User Portal Cluster LDAP Authors Network Dispatcher (Edge Comp.) WCM Authoring System (Non-clustered) Syndication JCR Render JCR Author Database Page 5 Architecture 2008

6 Components and Architecture functional: Authoring Option Optional its possible to separate the authoring system from the WebSphere Portal cluster. This allows performance optimization if multiple content authors are active. Page 6 Architecture 2008

7 Architecture - view Page 7 Architecture 2008

8 Architecture View by Customer (The customers starting inspiration and starting point.) Network Dispatcher VM1 (Edge Comp.) IBM HTTP 1 IBM HTTP 2 Portal Cluster incl. WCM VM4 Node1 WCM Authoring- System Quickr Cluster 8.1 based on WP 6.0 Node1 VM6 Learning Accelerator (2.7) Cluster based on WP 6.0 Node1 VM8 VM2 VM3 VM5 VM12 VM7 VM9 ESX 1 ESX 2 LAN ESX 3 Database JCR VM10 Sametime VM11 SAN 1 VMware Consolidated Backup v 1.1 SAN 2 VMware Consolidated Backup v 1.1 Critical points: No hardware failover within a cluster. Only 1 node within a cluster. LDAP (HA) Page 8 Architecture 2008

9 Architecture View by IBM DM Deployment Manager Learning Acc 2.7 Node 1 Node 2 DM Network Dispatcher (Stand-by) Quickr 8.1 Node 1 Portal WCM Node 1 DM DM Node 2 Node 2 Network Dispatcher IBM HTTP 1 IBM HTTP 2 Database 1 Database 2 Sametime B 1 B 2 B 3 B 4 VM 1 VM 2 VM 3 VM 4 VM 5 VM 6 VM 7 VM 8 VM 9 VM 10 VM 11 VM 12 Blade Center ESX 1 ESX 2 LAN Challenge: Minimize number of VMs. Create DMZ for Network Dispatcher and HTTP s. Optional: Dedicated WCM Authoring environment (on ESX 1 or 3?). VMware Consolidated Backup v 1.1 SAN 1 SAN 2 VMware Consolidated Backup v 1.1 LDAP (HA) Page 9 Architecture 2008

10 Planned Hardware ESX Processor (CPU) 4xQuad-Core Intel Xeon Processor, > 2,8 GHz Memory 64GB DASD 4x73 GB Raid 1 Network 4 * Gigabit Ethernet - Integrated:10 MBit/s, 100 MBit/s, 1000Mbps This sample must be customized to solve the specific customer requirements and along with an official IBM Software Sizing. Page 10 Architecture 2008