Patterns: Pervasive Portals Patterns for E-Business Series

Chapter 1: Introduction

Figure 1-1: The Patterns for e-business layered asset model

Figure 1-2: The four primary Business patterns

Figure 1-3: Integration patterns

Figure 1-4: Patterns representing a Custom design

Figure 1-5: Custom design with Self-Service, Information Aggregation, Access Integration and Application Integration

Figure 1-6: Composite patterns

Figure 1-7: Self -ServiceDirectly Integrated Single Channel

Figure 1-8: Self-ServiceDecomposition

Figure 1-9: Directly Integrated Single Channel application patternRuntime pattern

Figure 1-10: Directly Integrated Single Channel application patternRuntime pattern Variation 1

Figure 1-11: Directly Integrated Single Channel application pattern Windows 2000 product mapping

Chapter 2: The Access Integration Pattern

Figure 2-1: Portal composite pattern showing mandatory patterns

Chapter 3: Selecting the Application Patterns

Figure 3-1: Access IntegrationPervasive Device Access

Figure 3-2: Access IntegrationWeb Single Sign-On

Figure 3-3: Access IntegrationPersonalized Delivery

Figure 3-4: Self-Service application patterns

Figure 3-5: Application patterns in a Portal composite pattern

Chapter 4: Selecting the Runtime Patterns

Figure 4-1: Stand-Alone Single Channel application patternRuntime pattern

Figure 4-2: Stand-Alone Single Channel application patternRuntime pattern Variation 1

Figure 4-3: Old Pervasive Device Access Runtime pattern

Figure 4-4: Pervasive Device Access Runtime pattern Variation 1

Figure 4-5: Portal composite pattern variation for Pervasive solution

Chapter 5: Selecting the Product Mapping

Figure 5-1: Pervasive Device Access Runtime pattern Variation 1 product mapping

Figure 5-2: Portal composite pattern runtime pattern variation for Pervasive

Figure 5-3: Protocol mapping

Figure 5-4: Pervasive Portal solution framework

Chapter 6: Technology Options

Figure 6-1: Web client technology model

Figure 6-2: Web application server technology model

Chapter 7: Application Design

Figure 7-1: Component diagram

Figure 7-2: Help desk use case diagram

Figure 7-3: Class diagram - persistent class

Figure 7-4: Class diagram - business class interaction with the entity bean

Figure 7-5: Sequence diagram - make order

Figure 7-6: Sequence diagram with MVC design

Figure 7-7: Model-View-Controller tiers

Figure 7-8: Class diagram for Singleton pattern

Figure 7-9: Class diagram for Facade

Figure 7-10: J2ME architecture tiers

Figure 7-11: Portability between the specifications

Chapter 8: Application Development

Figure 8-1: Development process overview

Figure 8-2: IDE for WebSphere Studio Application Developer

Figure 8-3: IDE for WebSphere Studio Device Developer

Figure 8-4: The Mobile Application Compiler form

Figure 8-5: The DEES Administration Database

Figure 8-6: The Mobile Notes client on a Palm OS device

Figure 8-7: Generating the portlet .war file

Figure 8-8: Enabling Transcoding Technology

Figure 8-9: Configuring Transcoding for a portlet

Figure 8-10: Portlet results on a WAP phone

Figure 8-11: Mobile Application Builder

Figure 8-12: The Mobile Devices Administration Center

Figure 8-13: DB2 Everyplace synchronization for JDBC subscriptions

Figure 8-14: Subscription Set

Figure 8-15: Subscription

Figure 8-16: Groups

Figure 8-17: Users

Figure 8-18: WAP device simulator

Figure 8-19: Palm device simulator

Figure 8-20: The Sametime Connect for Palm OS

Figure 8-21: Notification Services in WebSphere Portal

Chapter 9: Security

Figure 9-1: Security issues for the components of a Pervasive Portal solution

Figure 9-2: Security layers for a generic n- tier solution

Figure 9-3: WebSphere Everyplace Connection Manager security

Figure 9-4: Relationship between protected objects, ACLs and POPs

Figure 9-5: Tivoli Access Manager and Single Sign-On architecture

Chapter 10: System Management

Figure 10-1: n-tier model with System Management and Data Contingency

Figure 10-2: Mobile Devices Administration Center

Figure 10-3: Intelligent Notification Services Administration portlets

Figure 10-4: Intelligent Notification Services User portlets

Figure 10-5: Device Manager console

Figure 10-6: System Management and Data Contingency represented in the operational model

Figure 10-7: Generic n-tier Production environment

Figure 10-8: A generic staging environment

Figure 10-9: A generic development environment

Figure 10-10: Connection between environments

Chapter 11: Performance and Availability

Figure 11-1: Multi-tier model with high availability, performance and high availability

Figure 11-2: Availability chain

Figure 11-3: Active/standby configuration

Figure 11-4: Active/active configuration

Figure 11-5: Load balance configuration

Figure 11-6: Performance and Availability for Pervasive Portal Solution components

Figure 11-7: ISP and routers high availability

Figure 11-8: Wireless Gateway cluster solution

Figure 11-9: High Availability for the Tivoli Access Manager components

Figure 11-10: Web application server availability

Figure 11-11: Web application server and Authentication proxy availability

Figure 11-12: Choosing a pattern

Figure 11-13: Portal pattern

Figure 11-14: Setting Performance and capacity objectives

Figure 11-15: Software settings

Figure 11-16: Hardware choice

Figure 11-17: Performance results

Figure 11-18: Performance graphics

Figure 11-19: Performance graphics

Chapter 12: Technical Scenario

Figure 12-1: Install portlet

Figure 12-2: Create a place

Figure 12-3: Create a page

Figure 12-4: Page to define the lay out for portlets

Figure 12-5: Page for select the portlets

Figure 12-6: Page after selecting the portlets

Figure 12-7: ITSO Web Application