Patterns : pervasive and rich device access solutions / [Peter Kovari ... et al.].

Format:

Book

Contributor:

Kovari, Peter.

International Business Machines Corporation. International Technical Support Organization.

Series:

WebSphere software.

IBM redbooks.

WebSphere software

IBM redbooks

Language:

English

Subjects (All):

Application software--Development.

Application software.

Software patterns.

Electronic commerce--Computer programs.

Electronic commerce.

WebSphere.

Physical Description:

xviii, 454 p. : ill.

Edition:

1st ed.

Place of Publication:

White Plains, NY : IBM, International Technical Support Organization, 2005.

Language Note:

English

Contents:

Front cover

Contents

Notices

Trademarks

Preface

The team that wrote this redbook

Become a published author

Comments welcome

Part 1 Pervasive solution patterns

Chapter 1. Patterns for e-business

1.1 The Patterns for e-business layered asset model

1.2 How to use the Patterns for e-business

1.2.1 Business, Integration, or Composite pattern, or a custom design

1.2.2 Selecting Application patterns

1.2.3 Review Runtime patterns

1.2.4 Review Product mappings

1.2.5 Review guidelines and related links

1.3 Summary

Chapter 2. Application patterns for pervasive solutions

2.1 Pervasive access applications

2.2 Pervasive Device Adapter application pattern

2.3 Rich Device application patterns

2.4 Other Access Integration patterns

2.4.1 Single sign-on

2.4.2 Extended Single Sign-On application patterns

2.4.3 Personalized Delivery application pattern

Chapter 3. Runtime pattern

3.1 An introduction to the node types

3.1.1 User node

3.1.2 Client node

3.1.3 Pervasive client services node

3.1.4 ISP Gateway (Pervasive services) node

3.1.5 Protocol firewall node

3.1.6 Connectivity and access for pervasive services node

3.1.7 Web server redirector node

3.1.8 Telephony connector

3.1.9 Voice gateway node

3.1.10 Presentation server node

3.1.11 Personalization server node

3.1.12 Directory and security services node

3.1.13 Application server node

3.1.14 Pervasive extension services node

3.1.15 Existing data and applications node

3.1.16 Database node

3.1.17 Collaboration server node

3.2 Runtime patterns for pervasive access

3.2.1 Pervasive Device Adapter::Runtime pattern (composed with Portal runtime pattern)

3.2.2 Pervasive Device Adapter=Voice::Runtime pattern

3.2.3 Rich Device::Runtime pattern.

3.2.4 Rich Device=Online::Runtime pattern

3.2.5 Rich Device=Store and forward::Runtime pattern

3.2.6 Rich Device=Store and forward::Runtime pattern variation 1

3.2.7 Composite Rich Device=Online and PDA=Voice::Runtime pattern

3.2.8 Pervasive Connectivity::Runtime pattern

3.2.9 Composite Pervasive and Rich Device solution::Runtime pattern

Chapter 4. Product mappings

4.1 Overview of IBM pervasive software products

4.1.1 WebSphere Everyplace Access V5.0

4.1.2 WebSphere Everyplace Connection Manager

4.1.3 WebSphere MQ Everyplace

4.1.4 WebSphere Client Technology, Micro Edition

4.1.5 Domino Server V6.5.1

4.1.6 WebSphere Voice Server

4.1.7 WebSphere Voice Application Access Server

4.1.8 Voice Response Server

4.2 Pervasive Device Adapter::Product mappings

4.3 Pervasive Device Adapter=Voice::Product mapping

4.4 Rich Device::Product mapping=Pervasive device OS

4.5 Rich Device=Online::Product mapping=Device Management

4.6 Rich Device=Store and forward::Product mapping

4.7 Rich Device=Store and forward::Runtime mapping=PIM and e-mail

4.8 Pervasive Connectivity runtime pattern::Product mapping

4.9 Pervasive Solutions composite pattern::Product mapping

Chapter 5. ITSO Railway sample overview

5.1 ITSO Railway

5.1.1 Business value to ITSO Railways

5.2 General requirements

5.3 Provide executive PIM and e-mail support

5.3.1 Key requirements

5.3.2 Example application scenario

5.4 Mobile customer access

5.4.1 Key requirements

5.4.2 Example application scenario

5.5 Mobile inventory management

5.5.1 Key requirements

5.5.2 Example application scenario

5.6 Monitor critical equipment

5.6.1 Key requirements

5.6.2 Example application scenario

5.7 Alerts to maintenance workers

5.7.1 Key requirements

5.7.2 Example application scenario.

5.8 Automated on-train ticketing

5.8.1 Key requirements

5.8.2 Example application scenario

5.9 Provide voice access to customers

5.9.1 Key requirements

5.9.2 Example application scenario

5.10 Maintain the mobile devices

5.10.1 Key requirements

5.10.2 Example application scenario

5.11 Secure mobile device

5.11.1 Key requirements

5.11.2 Example application scenario

Chapter 6. Pervasive application types

6.1 Application types

6.1.1 Solution space

6.1.2 Application types mapped to Runtime patterns

6.1.3 Scenario implementations using various pervasive technologies

Part 2 Guidelines

Chapter 7. Technology options

7.1 Client-side technologies

7.1.1 Devices

7.1.2 Operating systems

7.1.3 Device Platforms/Frameworks

7.2 Server-side technologies

7.2.1 Services

7.2.2 Java-based technologies

7.3 The mobile Web

7.3.1 HTML

7.3.2 cHTML

7.3.3 XML

7.3.4 XML Device-Independent Markup Extensions (XDIME)

7.3.5 XForms

7.3.6 XHTML 1.1 (HTML 4.01)

7.3.7 XSLT

7.3.8 WML

7.3.9 SyncML DS and DM

7.3.10 VoiceXML and X+V

7.4 Connectivity technologies

7.4.1 Wireless technologies

7.4.2 Wired technologies

7.4.3 Issues with connectivity

7.5 IBM-specific pevasive-related technologies

7.5.1 Service Management Framework (SMF)

7.5.2 Workplace Client Technology, Micro Edition (WCTME)

7.5.3 Extension Services for WebSphere Everyplace (ESWE)

Chapter 8. Application development toolkits

8.1 Pervasive tool strategy

8.1.1 WebSphere Studio and pervasive toolkits

8.2 Everyplace Toolkit

8.3 Multimodal Toolkit for WebSphere Studio

8.4 Voice Toolkit for WebSphere Studio

8.5 WebSphere Studio Device Developer

8.5.1 SMF Bundle Development Kit

8.5.2 Application Tools for Extension Services

Part 3 Scenario implementations.

Chapter 9. PIM and e-mail synchronization

9.1 Overview

9.1.1 Customer requirements

9.1.2 Functional requirements and use case model

9.1.3 Non-functional requirements

9.1.4 Solution approach

9.2 Architectural overview

9.3 System design overview

9.3.1 General considerations for synchronized enabled applications

9.4 Runtime configuration and deployment

9.4.1 Enable PIM and e-mail server to support synchronization server connection

9.4.2 Configure PIM and e-mail synchronization

9.4.3 Configure Everyplace Client and synchronization on client side

9.4.4 Using the PIM and e-mail synchronization

9.5 Summary

Chapter 10. Web access to ITSO Railway's timetables

10.1 Overview

10.1.1 Customer requirements

10.1.2 Use case model

10.1.3 Key requirements

10.2 Architectural overview

10.3 System design overview

10.3.1 Application flow diagram

10.3.2 Design considerations

10.4 Application development

10.4.1 Create the portlet application project framework

10.4.2 Add supporting files and business logic

10.4.3 Add connectivity to the existing train schedule database

10.4.4 Customize and add JSPs for specific markup languages

10.4.5 Test and debug the application

10.5 Summary

Chapter 11. Mobile Inventory Management with offline forms

11.1 Overview

11.1.1 Customer requirements

11.1.2 Functional requirements and use case model

11.1.3 Non-functional requirements

11.1.4 Solution approach

11.2 Architectural overview

11.3 System design overview

11.3.1 General considerations for intermittently connected applications

11.3.2 Mobile Supply Tracking System solution outline

11.3.3 Component model

11.3.4 Object model

11.4 Application development

11.4.1 Introduction to WebSphere Everyplace Toolkit.

11.4.2 Development of forms-based applications for mobile devices

11.5 Deployment and runtime configuration

11.5.1 Configuration for offline forms-based applications

11.5.2 Using the application

11.6 Summary

Chapter 12. Using Intelligent Notification Services

12.1 Business context

12.2 Architectural overview model

12.3 System design overview

12.3.1 Component model

12.3.2 Object model

12.4 Sample application development

Chapter 13. Using Workplace Client Technology, Micro Edition

13.1 Architectural overview model

13.2 System design overview

13.2.1 Component model

13.2.2 Object model

13.3 Application design

13.4 Sample application development

13.4.1 Creating the application

13.4.2 Creating the service interface

13.4.3 Create the servlet

13.4.4 Creating a user interface

13.4.5 Accessing the database

13.4.6 Creating messages

13.4.7 Setting up the launch configuration

13.4.8 Deploying the application

13.4.9 Launching the application

13.4.10 Using the ITSO Railways Ticketing application

13.5 Deploying the application

Chapter 14. Timetable information by Voice

14.1 Business requirements

14.2 High-level architectural overview

14.3 Activity diagram

14.4 Components

14.5 Interface for call flow

14.5.1 Dialogue design

14.5.2 Persona selection

14.5.3 Usability design

14.6 Development of timetable access

14.7 Voice portlet development

14.7.1 Setting up Voice Toolkit V5.0 for WebSphere Studio

14.7.2 Application grammar development

14.7.3 Creating a database for the application

14.7.4 Creating a call flow for the application

14.7.5 Creating speech output

14.7.6 Generating basic VoiceXML code structure from call flow

14.8 Testing the Timetable application

14.9 Preparing voice portlet for implementation.

14.9.1 Deploying the voice portlet in WebSphere Portal.

Notes:

"March 2005."

"SG24-6315-00."

Includes bibliographical references and index.

OCLC:

80247099