WebSphere Everyplace Deployment V6 Handbook for Developers and Administrators Volume One

7/28/2019 WebSphere Everyplace Deployment V6 Handbook for Developers and Administrators Volume One

1/431

ibm.com/redbooks

IBM WebSphere Everyplace Deployment V6Handbook for Developers and AdministratorsVolume I: Installation and Administration

Juan R. Rodriguez

Siva Aremanda

Yogesh P. Kamat

Leo Kuo

Matthew Perrins

Rafael SanchezPedro Siena Neto

Jeff Simon

Guillermo Villavicencio

Extend existing enterprise applications

to mobile devices

Deploy solutions using open

industry standards

Set up an end-to-end

deployment topology

Front cover
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


2/431


3/431

WebSphere Everyplace Deployment V6 Installationand Administration

June 2006

International Technical Support Organization

SG24-7141-00


4/431

Copyright International Business Machines Corporation 2006. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP

Schedule Contract with IBM Corp.

First Edition (June 2006)

This edition applies to Version 6, Release 0 of IBM WebSphere Everyplace Deployment, productnumber D558QLL.

Note: Before using this information and the product it supports, read the information inNotices on page ix.


5/431

Copyright IBM Corp. 2006. All rights reserved. iii

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi

The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. WebSphere Everyplace Deployment overview . . . . . . . . . . . . . 3

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.1 Enterprise and Starter Editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.4 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.5 WebSphere Everyplace Client Toolkit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.5.1 Sample applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Part 2. Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 2. Software prerequisites installation . . . . . . . . . . . . . . . . . . . . . . 192.1 WebSphere Application Server installation . . . . . . . . . . . . . . . . . . . . . . . . 20

2.2 Installation verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.3 HTTP Server and Web server plug-in installation . . . . . . . . . . . . . . . . . . . 26

2.4 Installing fix packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.5 Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.6 DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

2.7 Installing DB2 fix pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 3. WebSphere Everyplace Deployment v6 server installation . . 533.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2 Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.2 Software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.2.3 Database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.2.4 WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.2.5 IBM HTTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.2.6 Messaging infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56


6/431

iv WebSphere Everyplace Deployment V6 Installation and Administration

3.2.7 Supported browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.3 Supported environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.4 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.4.1 Handling higher software level requirements . . . . . . . . . . . . . . . . . . 57

3.4.2 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.5 WebSphere Everyplace Deployment installation . . . . . . . . . . . . . . . . . . . 58

3.6 Starting and stopping the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.6.1 Required privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.6.2 Starting the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.6.3 Stopping the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3.7 Administering users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3.8 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 4. User Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.1 Administration and user ID requirements . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.2 Required user groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.3 User Management console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.3.1 Launching the User Management console . . . . . . . . . . . . . . . . . . . . 75

4.3.2 Create an Everyplace Deployment user . . . . . . . . . . . . . . . . . . . . . . 76

4.3.3 Create an Everyplace Deployment group . . . . . . . . . . . . . . . . . . . . . 78

4.3.4 Assigning a user to a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4.3.5 Changing a user password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

4.3.6 Remove a user from a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.3.7 Delete a WebSphere Everyplace Deployment user . . . . . . . . . . . . . 83

4.3.8 Delete a WebSphere Everyplace Deployment group . . . . . . . . . . . . 83

4.3.9 User Management console considerations . . . . . . . . . . . . . . . . . . . . 84

Chapter 5. Migrating to Lightweight Directory Access Protocol . . . . . . . 85

5.1 Installation of Active Directory 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5.1.1 Pre-installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5.1.2 Sample installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5.2 Setting up users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

5.3 WebSphere Everyplace Deployment configuration. . . . . . . . . . . . . . . . . . 95

5.3.1 Directory requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

5.3.2 Directory organization requirements . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.3.3 Required users and groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.3.4 Pre-migration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

5.3.5 Existing user data considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

5.3.6 Upgrading the server configuration. . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 6. DB2 Everyplace Synchronization Server . . . . . . . . . . . . . . . . 1056.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

6.1.1 DB2 Everyplace as part of WebSphere Everyplace Deployment . . 107

6.1.2 Synchronization object description and hierarchy. . . . . . . . . . . . . . 108


7/431


8/431

vi WebSphere Everyplace Deployment V6 Installation and Administration

9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

9.2 Client prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

9.3 Step-by-step installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Chapter 10. Deploying rich client applications on Windows. . . . . . . . . . 215

10.1 Setting up the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

10.2 Setting up the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

10.3 Importing the application project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

10.4 Creating a feature project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

10.5 Creating an update site project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

10.6 Exporting and installing the feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

10.7 Running the application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Chapter 11. Deploying rich client applications on Linux. . . . . . . . . . . . . 22911.1 Client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

11.2 Exporting a rich client application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

11.3 Deploying the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Chapter 12. WebSphere Everyplace Deployment client secure connections

25312.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

12.2 Enabling SSL on IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

12.2.1 Verifying if security is enabled in IBM HTTP Server . . . . . . . . . . . 25412.3 Enabling SSL on WebSphere Application Server . . . . . . . . . . . . . . . . . 255

12.3.1 Verifying enabled security on WebSphere Application Server . . . 255

12.4 Configure the client to support SSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

12.4.1 Configuring SSL for Web Services . . . . . . . . . . . . . . . . . . . . . . . . 255

Chapter 13. Branding applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26113.1 Branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

13.2 WebSphere Everyplace Deployment branding . . . . . . . . . . . . . . . . . . . 263

13.2.1 Branding elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26413.2.2 Creating a branding plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

13.2.3 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

13.2.4 Building and packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

13.2.5 Installation and Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Part 4. Additional topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Chapter 14. WebSphere Client Technology Micro Edition application

support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29714.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

14.1.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

14.1.2 Mobile device setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302


9/431

Contents vii

14.2 DB2 Everyplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

14.2.1 Prepare source and mirror databases. . . . . . . . . . . . . . . . . . . . . . 307

14.2.2 Creating users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

14.2.3 Configuring subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

14.2.4 Testing synchronization with mobile devices . . . . . . . . . . . . . . . . 321

14.3 Web services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

14.3.1 Deploying Web service on server . . . . . . . . . . . . . . . . . . . . . . . . . 324

14.3.2 Testing Web services with the mobile device . . . . . . . . . . . . . . . . 331

14.4 MQ Everyplace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

14.4.1 Deploying MQ Everyplace on the server. . . . . . . . . . . . . . . . . . . . 331

14.4.2 Testing messaging with mobile devices . . . . . . . . . . . . . . . . . . . . 332

14.5 Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

14.5.1 Registering the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

14.5.2 Configuring a software distribution job . . . . . . . . . . . . . . . . . . . . . 33814.5.3 Testing software distribution with mobile device . . . . . . . . . . . . . . 342

Chapter 15. Connecting Applications through WebSphere Everyplace

Connection Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34715.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

15.1.1 Features and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

15.2 Connection Manager software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

15.3 Connection Manager functions and components . . . . . . . . . . . . . . . . . 352

15.4 TCP traffic optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35715.5 Mobility clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

15.5.1 Mobility client applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

15.5.2 WebSphere Everyplace Deployment applications . . . . . . . . . . . . 359

15.6 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

15.7 Everyplace Connection Manager on Linux . . . . . . . . . . . . . . . . . . . . . . 363

15.7.1 Network basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

15.7.2 Persistent data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

15.7.3 WebSphere Everyplace Connection Manager server . . . . . . . . . . 372

15.7.4 WebSphere Connection Manager Gatekeeper . . . . . . . . . . . . . . . 377

15.8 Connection Manager Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

15.8.1 Create a login profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

15.9 Connection Manager Client on Windows . . . . . . . . . . . . . . . . . . . . . . . 381

15.9.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

15.9.2 Creating a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

15.10 WebSphere Everyplace Deployment server setup . . . . . . . . . . . . . . . 383

15.11 Executing the scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

15.12 Running the scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39015.12.1 Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Part 5. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393


10/431

viii WebSphere Everyplace Deployment V6 Installation and Administration

Appendix A. Creating a bundle distribution package . . . . . . . . . . . . . . . 395Importing the project to deploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Creating the bundle package for software distribution . . . . . . . . . . . . . . . . . . 396

Appendix B. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

System requirements for downloading the Web material . . . . . . . . . . . . . 400

How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405


11/431

Copyright IBM Corp. 2006. All rights reserved. ix

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area.Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send license

inquiries, in writing, to:IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisionsare inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof express or implied warranties in cer tain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may

make improvements and/or changes in the product(s) and/or the program(s) described in this publication atany time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm

the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating platform for which thesample programs are written. These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment to IBM for the purposes ofdeveloping, using, marketing, or distributing application programs conforming to IBM's applicationprogramming interfaces.


12/431

x WebSphere Everyplace Deployment V6 Installation and Administration

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

EserverRedbooks (logo)

z/OS

AIX

Cloudscape

DataPropagator

DB2 Universal DatabaseDB2

Everyplace

Informix

IBM

Rational

RedbooksTivoli

WebSphere

Workplace

Workplace Client Technology

The following terms are trademarks of other companies:

Enterprise JavaBeans, EJB, Java, JavaBeans, JavaServer, JDBC, JDK, JRE, JSP, JVM, J2EE, J2ME,Solaris, Sun, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States,

other countries, or both.

Active Directory, Internet Explorer, Microsoft, Windows Mobile, Windows Server, Windows, and theWindows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarksof Intel Corporation or its subsidiaries in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.


13/431

Copyright IBM Corp. 2006. All rights reserved. xi

Preface

This IBM Redbook will help you plan, install, and administer mobile applications

to run in a WebSphere Everyplace Deployment Version 6 environment. Theinformation provided in this redbook targets business-to-employee (B2E)

enterprise applications, but most of the scenarios presented will apply tobusiness-to-consumer (B2C) applications as well. In this redbook, you will find

step-by-step examples and scenarios showing ways to integrate your enterpriseapplications into a WebSphere Everyplace Deployment environment byextending your online and offline application capabilities to use advanced

functions, such as Web services, messaging, database synchronization, devicemanagement, and security.

In this redbook, you will also find step-by-step sample installation and

administration procedures to help you get online, access, and synchronize yourenterprise application data from rich client devices. The redbook includes topicssuch as product installation, administration, database synchronization, device

management, and how to establish secure connections.

The redbook includes information about how to integrate WebSphere Everyplace

Deployment with WebSphere Everyplace Connection Manager as well assupporting WebSphere Client Technology Micro Edition (WCTME) clientapplications.

A basic knowledge of Java technologies such as servlets, JavaBeans, andEnterprise JavaBeans, as well as database, device management, XML

applications, and terminology used in Web publishing, is assumed.

The team that wrote this redbook

This redbook was produced by a team of specialists from around the world

working at the International Technical Support Organization, Raleigh Center.

Juan R. Rodriguez is a Consulting IT professional at theIBM ITSO Center, Raleigh. He has an M.S. degree inComputer Science from Iowa State University. He writes

extensively and teaches IBM classes worldwide on Web

technologies and information security. Before joining theIBM ITSO, he worked at the IBM laboratory in ResearchTriangle Park, North Carolina, as a designer and developer

of networking products.


14/431

xii WebSphere Everyplace Deployment V6 Installation and Administration

Siva Aremanda is a Senior IT Specialist with IBM GlobalServices in Australia. Siva has focused on WebSphere,

J2EE, and Java-based technologies. His expertiseincludes architecting, designing, developing, and deploying

enterprise applications using Java and J2EE with

WebSphere Application Server. He has a degree inComputer Science and Engineering and a Masters degree in

Information Technology from Swinburne University ofAustralia.

Yogesh P. Kamat is a Software Engineer with WebSphereQuality Center of Competence Organization, in ResearchTriangle Park, North Carolina. His areas of expertise include

Pervasive Computing and WebSphere Application Server.

He has also contributed to Technical Sales activities inGermany. He holds a Masters of Science degree inComputer Engineering from University of Texas at El Paso,

Texas.

Leo Kuo is a Software Engineer at the IBM Software Group,

Application and Integration Middleware Software. Hecurrently works in WebSphere Everyplace Deployment

server testing in Taipei, Taiwan. He has experience in

WebSphere products, such as WebSphere ApplicationServer and WebSphere Everyplace Device Manager. Leoholds a Master of Science and an Engineering degree fromthe National Taiwan University.

Matthew Perrins is a Consulting IT Specialist at the IBMSoftware Group Laboratory Services in the U.K. His expertise

includes designing and developing enterprise applicationsusing Java and J2EE Standards with WebSphere Application

Server. He is currently focused on User Interfacetechnologies, such as JavaServer Faces, AJAX, EclipseRCP, SWT, and Smart Clients in WebSphere Everyplace

Deployment and Workplace Managed Client.

Rafael Sanchez is an IT Architect with IBM Spain. He hasB.S. and M.S. degrees in Computer Engineering, a Bachelor

degree of Business Administration, and a Music teacherdegree from the Royal Conservatory of Music of Madrid.

He has years of experience in Pervasive Computing areas,including mobile telephony, embedded devices, wireless

networks, and RFID. He is currently doing Computer and


15/431

Preface xiii

Telecommunication Engineering Ph.D. studies on artificialintelligence and biologically inspired computing.

Pedro Siena Neto is the Founder and CEO of SST itsolutions, an IBM Business Partner in Brazil focused on

wireless solutions and applications. He has been working withPervasive Computing since 1992. He participates on thedevelopment of WLAN adapters, and is a pioneer on

Logistics Solutions using this technology. Before foundingSST, he worked at IBM Brazil, and IBM Research Triangle

Park (North Carolina, U.S.A.), as a product and developmentengineer of networking products.

Jeff Simon is an IT Solutions Architect at IBM in Austin,

Texas, and works with the IBM Systems and TechnologyGroup. He received his Computer Science degree fromTexas State University. He has worked on multiple platforms,

including z/OS, AIX, Windows, and Linux supportingbusiness partners and customers. His current area ofexpertise is centered around WebSphere and Portal

solutions.

Guillermo Villavicencio holds a degree in Informatics

Engineering from the Pontifical Catholic University of Peru. Heis the Chief Information Officer for Carhados Peru, an IBMBusiness Partner. He has been the architect for several

e-business projects, including wireless and Portal solutions.His current area of expertise is centered around Web technologies and pervasive

computing. He writes and teaches classes worldwide on Web technologies andJava Application Development using Eclipse platforms.

Thanks to the following people for their contributions to this project:

Charles LeVayIBM Research Triangle Park, North Carolina, U.S.A.

Ricardo LechetaWasys Technology, Brazil

Angela E. NoetherIBM China

Thomas Fanghnel, Cecilia Chu, Louis Mau, Debby NakamuraIBM San Jose, California, U.S.A


16/431

xiv WebSphere Everyplace Deployment V6 Installation and Administration

Leslie ParhamInternational Technical Support Organization, San Jose Center

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbook

dealing with specific products or solutions, while getting hands-on experiencewith leading-edge technologies. You'll team with IBM technical professionals,Business Partners, and clients.

Your efforts will help increase product acceptance and customer satisfaction. As

a bonus, you'll develop a network of contacts in IBM development labs, andincrease your productivity and marketability.

Find out more about the residency program, browse the residency index, and

apply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our Redbooks to be as helpful as possible. Send us your comments

about this or other Redbooks in one of the following ways:

Use the online Contact us review redbook form found at:

ibm.com/redbooks

Send your comments in an e-mail to:

[email protected]

Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P099

2455 South RoadPoughkeepsie, NY 12601-5400
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html


17/431

Copyright IBM Corp. 2006. All rights reserved. 1

Part 1 Introduction

In this part of the redbook, we introduce you to WebSphere EveryplaceDeployment product overview and installation prerequisites.

Part 1


18/431

2 WebSphere Everyplace Deployment V6 Installation and Administration


19/431


Chapter 1. WebSphere EveryplaceDeployment overview

In this chapter, we discuss the following WebSphere Everyplace Deploymenttopics:

Overview Components System requirements Toolkit

1


20/431


1.1 Introduction

WebSphere Everyplace Deployment is an end-to-end mobile platform supporting

secure messaging, device management, and relational data replication.

Solutions to a broad variety of industries can be developed using WebSphereEveryplace Deployment, including finance, insurance, service solutions, sales

force automation, health care, and subscriber services.

WebSphere Everyplace Deployment supports the WebSphere Everyplace family

of products, Workplace Client Technology Micro Edition v5.7.1 and v5.7.2 FP1and Workplace Client Technology Micro Edition Enterprise Offering v5.8.1.

This chapter provides an overview of WebSphere Everyplace Deployment,

including features and benefits.

1.2 Overview

The WebSphere Everyplace offerings include the WebSphere Everyplace

Deployment family of server-managed client platforms, tooling, and server-sidecomponents.

The framework of WebSphere Everyplace Deployment represents the nextgeneration of mobile computing by delivering data security and transactionalintegrity to mobile clients while extending the services oriented architectures

(SOA) to the edge of the network.

WebSphere Everyplace Deployment server, an extension to WebSphere

Application Server, is a Java-based platform supporting secured messaging,relational data synchronization, and device management on desktops, laptops,

mobile, and embedded devices.

WebSphere Everyplace Deployment extends the J2EE/WebSphereprogramming model and Web services to mobile devices running Windows or

Linux with a client called WebSphere Everyplace Deployment for Windows andLinux. Clients can communicate with back-end servers while maintaining a high

level of security and reliable transactions. See Figure 1-1 on page 5.


21/431

Chapter 1. WebSphere Everyplace Deployment overview 5

Figure 1-1 WebSphere Everyplace Deployment

WebSphere Everyplace Deployment includes the following major components:

WebSphere Everyplace Deployment server v6

Provides an integrated installation and configuration for individual server

components WebSphere Everyplace Deployment for Windows and Linux Client v6

Provides support for a Rich Client platform and Web services

WebSphere MQ Everyplace

Provides secured messaging, once-only assured delivery, andcomprehensive security

DB2 Everyplace Synchronization Server v8.2.1

Small footprint relational database. Supports DB2e or Cloudscape on theclient


22/431


Device Management Server v1.8

Provides software distribution and device management

WebSphere Everyplace Client Toolkit v6

Used to develop, deploy, and manage server-managed client applications

Using WebSphere Everyplace Deployment, developers can develop, deploy, andmanage their Java or services-based applications within the service oriented

architecture (SOA) extending the SOA services out to the edge of the network.

The SOA is a set of open standards and interfaces for Web services, includingsupport for Simple Object Access Protocol (SOAP), Web services Definition

Language (WSDL), and Business Process Execution Language (BPEL).

1.2.1 Enterprise and Starter Editions

WebSphere Everyplace Deployment offers two packages:

WebSphere Everyplace Deployment Enterprise Edition v6.0

Asynchronous/synchronous messaging using MQ Everyplace (MQe)

Relational data synchronization using DB2 Everyplace (DB2e)

Installation and maintenance of on-device software using WebSphere

Everyplace Device Management

Per processor licensing with no limitation on number of users accessing

the server

Client software with entitlement for 50 client devices. The client softwareincludes the toolkit.

WebSphere Everyplace Deployment Starter Edition v6.0

Same content and functionality as the Enterprise Edition

Limit of 50 users accessing the server program

1.3 Components

WebSphere Everyplace Deployment serverWebSphere Everyplace Deployment server is a Java-based platform providingan integrated installation and configuration for the server components.

A common user registry and user management console are shared by DB2Everyplace and Device Management Server. The user management console is


23/431


available to create users and groups when DB2 is configured as the userrepository.

There is a configuration wizard available to reconfigure the user managementsubsystem to use Active Directory 2003 as the user registry instead of DB2.

Also, the Configuration wizard can be used to change administrator passwords.

The installation program does not install the prerequisite software (DB2 UDB,

IBM HTTP Server, and WebSphere Application Server). However, theprerequisite checker ensures the appropriate software is installed before the

WebSphere Everyplace Deployment installation is started.

WebSphere MQ EveryplaceWebSphere MQ Everyplace (MQe) v2.0.1.8 provides support for asynchronous

messaging with a comprehensive security framework. MQ Everyplace worksefficiently in environments where networks are unstable, or where bandwidth istightly constrained.

MQ Everyplace supports the following features:

Asynchronous and synchronous messaging

Once-only assured delivery of messages

Comprehensive security features, including authentication, encryption,

non-repudiation, and compression

MQ Everyplace has a comprehensive set of security features including:

Local

Protects message-related data at a local level such as

authorizing/authenticating access to any data or encrypting MQ Everyplacedata.

Queue-based

Protects messages between the initiating queue manager and the targetqueue Message level.

Queue-manager-based

Configures the queue manager and its private registry to add securityfeatures.

Channel level

The channel between a queue manager and remote queue is given the samelevel of security as the queue (using a cryptor).

Certificate-based


24/431


MQ Everyplace can be configured as a WTLS Mini-Certificate Server addingauthentication capabilities.

Private registry services

A repository where public and private objects can be stored.

Public registry services

A publicly accessible repository for mini-certificates.

Mini-certificate issuance service

Server includes a mini-certificate issuance service.

Figure 1-2 shows the MQ Everyplace message flow from the client to the server.

Figure 1-2 MQ Everyplace message flow

Initially, the server program creates the queue manager (QM1) and defines any

other required queues (such as Q1 on the server).

A listener and a port must be defined before the server receives any message

from the remote queue managers. Other parameters are created for the listenersuch as a protocol (TCP/IP) and a timeout value.

The client establishes a queue manager and a connection to the server, which

identifies the IP address of the server and the port number of its listener.


25/431


For an asynchronous connection, MQ Everyplace stores data locally on the clientmachine until it can be sent. The queue manager is responsible for transmitting

the messages when the connection becomes active.

DB2 Everyplace Synchronization ServerDB2 Everyplace Synchronization Server (DB2e) v8.2.1 is a small footprintrelational database and high performance data synchronization solution that

enables enterprise applications and data to be securely extended to clients suchas laptops, mobile or embedded devices.

DB2e supports sending encrypted bi-directional/directional data transfers

between mobile clients and back-end enterprise databases.

Figure 1-3 demonstrates a synchronization request initiated from the client.

Figure 1-3 DB2e architecture

In this three-tier environment, the DB2e framework consists of a source server,mid-tier server, and the client. The source server is the enterprise database. The

mid-tier server contains the Synchronization Server, DB2 UDB, and a servletengine. The Synchronization Server controls synchronization and uses DB2

UDB for storing and managing data.

Figure 1-3 demonstrates a synchronization request initiated from the client. Hereare the steps:


26/431


1. Client initiates synchronization.

2. Request is authenticated and placed on input queue on mid-tier system. Theinitiating client waits for a reply from the source server.

3. Subscription information is obtained to define how information in a source

system is synchronized with a mobile device. The following subscription typesare supported:

JDBC

Provides access to data in source tables on a data source using a JDBC

interface.

Upload

Allows the user to directly insert rows into a table on a source database.

File

Allows any file type to be replicated from the Synchronization Server.

Custom

Allows custom interactions with the Synchronization Server and data

sources.

DataPropagator

Provides users with access to data in source tables on a DB2 server. The

XML scripting tool is used to create DataPropagator subscriptions.

4. Data is placed into a staging table which improves throughput capacity ofsync requests because changes can be staged while other updates are

taking place.

5. Data is copied from staging table to the mirror table and changes recorded in

the DB2 log.

6. DB2 DataPropagator Capture program starts. Changes are captured to themirror table from the DB2 log and writes them to a change data table.

7. DB2 DataPropagator Apply program applies changes from change data tableto the source system.

Device Management ServerDevice Management Server v1.8 is a device management technology that can

distribute software and manage devices.

Device Management Server provides the following features:

Enrollment/initial device setup Device configuration Device identification


27/431


Job control Software package definitions Software distribution and removal Device inventory collection

Device Management Server also supports software bundle management forOSGi-enabled devices providing provisioning for installing, starting, stopping,updating, and removing bundles. See Figure 1-4.

Figure 1-4 Device Management Server Architecture

Device Management Server v1.8 includes the following major components:

Device Management Server (Device Manager)

Java (J2EE) servlet application providing an application managementinterface to start and stop the Device Manager.

Device plug-ins

Code that extends Device Management Server to handle deviceidentification, communications, job processing, and other high-levelmanagement tasks for a particular class of managed devices. Each plug-in

handles a different device class.


28/431


Device Manager Database (DB2)

Central repository (relational database) for all device managementinformation which can be accessed through the Device Manager API.

Contains tables of entries describing managed devices and store

device-related data, resources, and information. Information about jobs isalso stored in the Device Manager Database.

Device Manager Web services API

Defines the programming interface between the Device Manager Server,

administration clients, external applications, and the device or job-relateddata resources stored in the Device Manager database.

Device Manager Administration Console

An optional GUI for administering device management from a Windows client.Tasks include add and view devices and device software, submit jobs, and

query a job status.

Web-based Customer Care and Customer Self-Care applications

Web-based Customer Care allows a client service representative or

administrator to perform tasks such as manage a device, manage jobs, andview software on a device.

Client Self-Care applications are used by device owners to manage the

device they own. Generally, Self-Care users can view information, but notchange information.

Also, there is a subscription manager component to control access to user

interfaces for administrators and device users.

Integrated user managementA common user registry is provided with WebSphere Everyplace Deployment.DB2 is provided as the default user registry.

A configuration utility is provided to upgrade to Windows Server 2003 ActiveDirectory. This utility does not migrate user data from DB2 to Active Directory.Also, bulk load of users and groups is not supported with the initial release.

WebSphere Everyplace Deployment ClientWebSphere Everyplace Deployment Client v6.0 provides a Java environment

and the WebSphere Everyplace Client Toolkit that is used to develop, deploy,and manage server-managed client applications.

The client supports desktops and laptops providing a rich client platformsupporting enterprise applications, transactions, device management, and Webservices.


29/431


The client platform is a follow-up release to Workplace Client Technology, MicroEdition - Enterprise Offering (WCTME-EO V5.8.1) and will run on WebSphere

Everyplace Deployment for Windows and Linux v6.

WebSphere Everyplace Deployment for Windows and Linux v6 client platform

supports the following features and specifications: JSP v2.0

Servlet v2.4

SSL

JSF and JSTL v1.1 libraries

Embedded Transaction container (ETC) for business logic

Cloudscape relational database

JNDI

Web services

WS-Security and SSL-enablement for WS provider

ICU4J (Globalization)

Application launcher/switcher

1.4 System requirements

Here is a list of requirements for WebSphere Everyplace Deployment server.

Software

Windows 2003 with Service Pack 1, Enterprise or Standard Edition

Prerequisites:

DB2 Universal Database V8.2.2 Enterprise Edition, Workgroup ServerUnlimited Edition, or Workgroup Server Edition with a five user minimum

WebSphere Application Server v6.0.2

IBM HTTP Server (IHS) v6.0.2 (included with WebSphere Application Serverv6.0)

Hardware

Minimum 2 GHz processor (or higher) Minimum physical memory: 2 GB


30/431


ClientHere is a list of requirements for WebSphere Everyplace Deployment Client:

Software

Linux

Red Hat Enterprise Linux Workstation V3.0 WS with GIMP Toolkit (GTK)support - Update 3

Windows XP Professional

Microsoft Windows XP Service Pack 1 or Service Pack 2

Hardware

Linux, Windows XP Professional

Intel Pentium III 800 MHz processor or equivalent (1.0 GHzrecommended)

256 MB RAM (more RAM if applications require additional memory)

A display adapter setting of at least 256 colors and 1024x768 or higher

resolution recommended

100 MB disk space in your operating system temporary directory

150 MB disk space for product installation

x86 processors capable of supporting Windows XP

1.5 WebSphere Everyplace Client Toolkit

The WebSphere Everyplace Client Toolkit (Everyplace Toolkit) provides andintegrates a set of tools that allows you to develop, debug, test, package, anddeploy client applications that use WebSphere Everyplace Deployment services.

Everyplace Toolkit v6.0 supports both the Eclipse v3.0.2 Rich Client Platformlocal GUI-based applications and Web Container Servlet/JavaServer Pages

(JSP) applications.

These tools extend the Rational Software Development Platform supportingRational Web Developer v6.0.0.1, Rational Application Developer v6.0.0.1, and

Rational Software Architect v6.0.0.1.

Everyplace Toolkit enables software developers to extend their Java applicationsto the client in connected, disconnected, or occasionally connected modes.


31/431


Everyplace Toolkit provides the following features to develop applications for theWebSphere Everyplace Deployment environment:

Bundle/plug-in tools

Built on top of Eclipse v3.0.2 release of Plug-in Development Environment

(PDE). The key components include: Integrated plug-in manifest editor

Local launch and debug support for the Windows and Linux clients

Platform profile support for run-time environment

Web tools

Provide developers with a tool to create, test, and deploy Web applications forWebSphere Everyplace Deployment platforms, supporting:

Servlet v2.4 and v2.3

JSP v2.0 and v1.2

Scriptable (command line/ANT task) WAB tool support (RationalApplication Developer, Rational Software Architect, or Rational Web

Developer required)

Web services tools

Provide ability to extend Web services into Windows and Linux mobile or

rich-user-interface environments. The Web services tools include:

Wizard to generate client-side communication stubs

Wizard to configure client-side security (similar in functionality to Web

services for J2ME specification 172)

Editors to modify security configurations

Wizard to expose OSGI services within Web services

Embedded transaction tools

Provide methods to convert existing Rational Application Developer v6.0Enterprise JavaBeans (EJB) projects into Client Services Embedded

Transaction projects.

Platform building tools

Allow for creation of a platform image containing all required components for

users applications. Provides the smallest initial footprint of the WebSphereEveryplace Deployment for Windows and Linux run time in a zip file.


32/431


1.5.1 Sample applications

The WebSphere Everyplace Client Toolkit ships with the following samples andexamples to assist with application development:

Order Entry Applications

A rich client and Web application demonstrating using a Web container, JavaServlet v2.3, Configuration Admin service, WebSphere MQ Everyplace

(MQe), Java Database Connectivity (JDBC), DB2 Everyplace (DB2e), andRich Client views/preference pages.

Mobile Web services

A Web Service Stock Quote Client demonstration project is created and

installed with Rational Software Development Platform demonstrating how toaccess a Web Service from a static and dynamic client.

Pizza JSP Web Application

Creates a Client Services Web project to demonstrate a pizza-ordering Webapplication.

OSGi

Two Client Services projects created to demonstrate how to useConfiguration Admin service and ManagedService interface to manage

configuration properties of the bundle.

DB2e

Creates a Client Service project to demonstrate how to access a local DB2e

database.

MQe

Creates a Client Service project demonstrating how to start and stop a queue

manager and put a message to and get a message from a local queue.


33/431


Part 2 Server

In this part of the redbook, we describe the server-side functions provided withIBM WebSphere Everyplace Deployment. You will find information about server

installation, administration, database synchronization, device management, andsecure connections.

Part 2


34/431



35/431


Chapter 2. Software prerequisitesinstallation

This chapter provides detailed instructions about the installation process of therequired software prerequisites before you install WebSphere Everyplace

Deployment.

This chapter provides details about the following topics:

WebSphere Application Server V6.0.0.2 installation

WebSphere Application Server V6.0.0.2 installation verification

IBM HTTP Server and Web server plug-in installation

Fix pack Installation for WebSphere Application Server, IBM HTTP Server,and Web server plug-in

WebSphere Application Server, IBM HTTP Server, and Web server plug-inverification

DB2 v8.2 installation

DB2 fix pack installation

2

2 1 WebSphere Application Server installation


36/431


2.1 WebSphere Application Server installation

We describe WebSphere Application Server installation process for Windows

2003 in detail.

Step 1. Starting the installationLog on as a member of the administrator group to successfully install the

product. You cannot install the product correctly from a user ID that does notbelong to the administrator group.

Insert the WebSphere Application Server V6.0.0.2 CD into the CD-ROM drive.

The InstallShield Wizard should start automatically depending on whether or not

you have autostart enabled for the CD-ROM drive. If it does not start, you will

need to perform the following actions:

Open the command prompt by selecting Start Run.

When the Run dialog box appears, type cmd in the Open: text entry field andthen click OK.

When the command prompt window appears, type the following command

(substitute the appropriate location and drive letter for your CD-ROM drive):

C:\WASfiles>launchpad.bat

Step 2. LaunchpadThe Launchpad window will open as shown in Figure 2-1 on page 21. TheLaunchpad has links to other resources for different installations on the left side

of the window. WebSphere Application Server offers subcomponents of theApplication Server V.6 such as IBM HTTP Server, Web server plug-ins,

WebSphere Application Clients, and Application Server Toolkit.

Click Launch the installation wizard for WebSphere Application Server

to begin the installation.


37/431

Chapter 2. Software prerequisites installation 21

Figure 2-1 WebSphere Application Server - Launchpad window

The Installation Wizard window in Figure 2-2 on page 22 will appear informing

you that there are two component options, and it is now going to install theApplication Server. The other components have a separate installation process.Click Next.

Figure 2-2 on page 22 appears.


38/431


Figure 2-2 Installation Wizard window

Step 3. License agreement

The software license agreement appears. To proceed you are required to readthis information and select I accept the terms in this license agreement. Click

Next.

Step 4. System prerequisite checkThe installation wizard checks your system to determine whether or not a

supported operating system is running and whether or not the operating systemhas the appropriate service packs and patches. After checking prerequisites, the

installation wizard checks for existing WebSphere Application Server products.Once the installation wizard has completed the check successfully, you will beable to continue with the process. Click Next.

Step 5. Installation locationThe installation wizard will now display the default installation directory setting for

WebSphere Application Server as shown in Figure 2-3 on page 23. Click Next.


39/431


Figure 2-3 WebSphere Application Server installation directory

Step 6. Setup typeThe installation wizard will now give you two installation options: Full Installationor Custom Installation. Click Next.

Step 7. Installation summaryThis window summarizes the information that you have entered throughout theinstallation wizard process. This is illustrated in Figure 2-4. If the information isincorrect, you can click Backto change the values. If the information is correct,

click Next to begin installing IBM WebSphere Application Server v6.

Figure 2-4 Installation summary

The installation of the core products will take about 15-20 minutes to complete.A h i h i ll i i d ill i h i f l hi h Fi


40/431


At that time, the installation wizard will give you the option of launching the First

steps console, which is illustrated in Figure 2-5. Use this console to run aninstallation verification test, start and stop the Application Server, and provide

further information related to the Application Server. Choose Launch the First

steps console and click Finish to complete the process successfully.

Figure 2-5 Completion window

2.2 Installation verification

It is important to verify that WebSphere Application Server was installedsuccessfully. For example, use the First steps utility.

Step 1. First stepsThe First steps console will appear after the installation is complete. If it does not,you can locate this console in:

Programs IBM WebSphere Application Server v6 Profiles default First steps

Step 2. Start WebSphere Application Server


41/431


The First steps console shown in Figure 2-6 displays multiple options. In order to

verify that the installation was successful, you must first select Start the server.

Figure 2-6 First steps console

Step 3. Verify installationOnce the WebSphere Application Server has successfully started, selectInstallation verification from the First steps window. Check the output for any

errors, and ensure that it states that the WebSphere Application Serververification installation is complete.

Step 4. Stop the WebSphere Application ServerSelect Stop the Server from the First steps window. Check the log output

window for the following line:

Server server1 stop completed.

Close the output window.

Step 5. Exit First stepsThe installation of WebSphere Voice Server has now been verified. Click Exit onthe First steps window to close.

2.3 HTTP Server and Web server plug-in installation


42/431


The installation process for the IBM HTTP Server and the Web server plug-in is

similar to the WebSphere Application Server installation. You will use the sameLaunchpad window as shown in Figure 2-1 on page 21.

Note: It is important to install the IBM HTTP Server before the Web server

plug-ins.

Step 1. LaunchpadRefer to the beginning steps of 2.1, WebSphere Application Server installationon page 20 that describes the Launchpad details.

Step 2. IBM HTTP Server WizardClick Launch the installation wizard for IBM HTTP Server. This will start thewizard and a welcome window will appear. Click Next.

Step 3. License agreementThe software license agreement appears. To proceed, you are required to read

this information and select I accept the terms in this license agreement. ClickNext.

Step 4. Installation locationThe installation wizard will now display the default installation directory setting forIBM HTTP Server. Click Next.

Step 5. Setup typeThe next window provides three choices for setup types. We recommend atypical setup for most users. An example of this can be seen in Figure 2-7 on

page 27.


43/431


Figure 2-7 Setup type

Step 6. Account informationThe window that appears next has many options. Select Run IBM HTTP Server

as a Windows Service and Run IBM HTTP Administration as a WindowsService. You can also choose whether or not you want to log on as a Local

System account or as a specified user account and provide a user name andpassword. An example of this can be seen in Figure 2-8. Click Next.

Figure 2-8 Account information

Step 7. SummaryThis window provides a summary of the information that you have entered


44/431


This window provides a summary of the information that you have entered

throughout the installation wizard process. This is illustrated in Figure 2-9. If theinformation is incorrect, you can click Backto change the values. If the

information is correct, click Next to begin the installation.

Figure 2-9 Summary

Step 8. Installation completeWhen the installation of the IBM HTTP Server has completed successfully, thewizard will report this, and you click Next. The final window of the IBM HTTP

Server installation wizard will give you the option to launch plug-in installationand also provide a Web site address for more information. Choose Launch the

WebSphere Application Server- Plug-in install and click Finish. This willautomatically open the Plug-in installation wizard.

Step 9. Web server plug-in wizardThe first window of the Plug-in wizard will provide options for more information. If

you choose this additional information, it will appear once you click Next and also

after the installation. Click Next.

Step 10. License agreementTo proceed, you are required to read this information and select I accept theterms in this license agreement. Click Next.

Step 11. System prerequisite checkThe installation wizard for the Web server plug-ins checks your system to

determine whether or not a supported operating system is running and whetheror not the operating system has the appropriate service packs and patches. Afterchecking prerequisites, the installation wizard checks for existing WebSphere

Application Server products. Once the installation wizard has completed thecheck successfully, you will be able to continue with the process. Click Next.


45/431


y, y p

Step 12. Configure Web serverThis window gives you the option to configure a Web server as seen in

Figure 2-10. You will configure a Web server, so choose IBMHTTP Server V6,and click Next.

Figure 2-10 Web server configuration

Step 13. Installation scenarioIn Figure 2-11, choose an installation scenario that matches your environment.Select WebSphere Application Server machine (local) because the

Application Server and the Web server are on the same machine. Click Next.

Figure 2-11 Installation scenario



46/431


e s a a o a d o d sp ay e de au s a a o d ec o y se g o

the Web server plug-ins as shown in Figure 2-12. Click Next.

Figure 2-12 Plug-ins location

The wizard will then display the default installation directory setting for the

WebSphere Application Server as shown in Figure 2-13. Click Next.

Figure 2-13 WebSphere Application Server location

Step 15. Configuration information

The next window will ask you for the IBM HTTP Server configuration file and theport number. To change the location of your existing configuration file, click

Browse to search for the correct file. An example of this can be seen inFigure 2-14 on page 31. When you have entered the information, click Next.


47/431


Figure 2-14 Configuration file and Web server port

Step 16. Web server definitionThe installation wizard will ask for a unique Web server definition name as seenin Figure 2-15. You may want to keep the default name for the server as

webserver1. Click Next.

Figure 2-15 Web server definition

Step 17. Plug-in fileThe installation wizard will now ask for the location of the plugin-cfg.xml file touse for the Web server. If the file does not exist, the wizard uses the defaultlocation to generate the file. Click Next.


48/431


Figure 2-16 File location

Step 18. InformationThe installation wizard will now display the information for the configuration of theWeb server definition as shown in Figure 2-17. Click Next.

Figure 2-17 Configuration information

Step 19. SummaryThis window provides a summary of the installation. This is illustrated inFigure 2-18 on page 33. If the information is incorrect, you can click Backto

change the values. If the information is correct, click Next to begin theinstallation.


49/431


Figure 2-18 Plug-ins Summary

Step 20. Installation completeThe Web server Plug-ins installation is complete. Click Finish.

2.4 Installing fix packs

The Update Installer is the tool you use to install updates (interim fixes, fix packs,and refresh packs) to WebSphere software, including WebSphere Application

Server v6.0 releases.

Important: Before installing or uninstalling updates, ensure that all WebSphereApplication Server and related processes have been stopped. The product to be

updated must not be running prior to applying service. Make sure that theprerequisites of the installation are met before starting the installation. Installationof fix packs may require the Java run time to be available, even if the installation

is not being updated.

Step 1. DownloadDownload the most current version of the update installer or fix pack ZIP file from

the support site into the install_root directory.

The install_root directory for the base fix pack will be the location of the

WebSphere Application Server that you installed. For example:

C:\Program Files\IBM\WebSphere\AppServer

The install_root directory for the plug-ins fix pack will be the location of the Webserver plug-ins that you installed. For example:

C:\Program Files\IBM\WebSphere\Plugins

The install_root directory for the IBM HTTP Server fix pack will be the location ofthe IBM HTTP Server that you installed. For example:

\ \


50/431


C:\Program Files\IBM HTTP Server

Step 2. Unpack the ZIP file

When unpacking the ZIP file, it is important to choose the correct directory asstated in Step 1. The ZIP file will create the updateinstallerdirectory and severalsubdirectories, including the maintenance directory. An example of the

updateinstaller directory can be seen in Figure 2-19.

Figure 2-19 Updateinstaller directory

Step 3. InstallUse the update installer, update.exe, to install the interim fix or fix pack. Eachupdate installer is located in its specified directory. Update.exe will start the

InstallShield wizard shown in Figure 2-20 on page 35. Click Next.

Note: Do not launch multiple copies of the Update Installer wizard at one time.

Concurrent launches of the update installer program are unsupported.Performing more than one update at the same time can produce unpredictableresults, which might include a failed or faulty installation.


51/431


Figure 2-20 InstallShield Wizard Welcome window


the WebSphere Application Server product that you will update. If the installationdirectory is incorrect, change it, and click Next.

Step 5. Maintenance operationSelect whether or not you would like to install or uninstall the maintenance

package, and click Next. The window that appears will display the defaultinstallation directory of the product you are updating. An example of this is shown

in Figure 2-21. If the directory is not correct, change it, and click Next.

Figure 2-21 Directory location

Step 6. Installation summaryThe next window to appear will summarize the update. When installing the base

fix pack it is necessary to copy the current JDK to a new location and relaunch


52/431


fix pack, it is necessary to copy the current JDK to a new location and relaunchthe wizard using the copied JDK. The wizard will do this for you. Click Next to

begin the copy. An example of this can be seen in Figure 2-22. Once the wizard

has successfully finished copying the JDK, click Next to relaunch the wizard.

For the IBM HTTP Server update, it is not necessary to copy the JDK, so click

Next to start the installation.

Figure 2-22 Update summary

Step 7. FinishOnce the installation has completed successfully, the wizard will inform you ofthe upgrade and the installed maintenance package. Click Finish to exit the

wizard.

Step 8. Verification of installationIt is important to verify the updates of each fix pack. From a command window,enter the appropriate commands. For example:

For the base fix pack, the commands are:

cd Program Files\IBM\WebSphere\AppServer\binversionInfo.bat

Check the output from the versionInfo command for the following entry:

Name IBM WebSphere Application ServerVersion 6.0.2.0

E l 2 1 li t l t t f th d


53/431


Example 2-1 lists sample output of the command.

Example 2-1 Sample output from the versionInfo command for the base fix pack

WVER0010I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.WVER0011I: WebSphere Application Server Release 6.0WVER0012I: VersionInfo reporter version 1.15.3.1, dated 4/25/05

-------------------------------------------------------------------------------IBM WebSphere Application Server Product Installation Status Report-------------------------------------------------------------------------------

Report at date and time 2005-09-30 14:52:09-0400

Installation--------------------------------------------------------------------------------Product Directory C:\Program Files\IBM\WebSphere\AppServerVersion Directory C:\ProgramFiles\IBM\WebSphere\AppServer\properties\versionDTD Directory C:\ProgramFiles\IBM\WebSphere\AppServer\properties\version\dtdLog Directory C:\Program Files\IBM\WebSphere\AppServer\logs

Backup Directory C:\ProgramFiles\IBM\WebSphere\AppServer\properties\version\update\backupTMP Directory C:\DOCUME~1\admin\LOCALS~1\Temp

Installation Platform-------------------------------------------------------------------------------Name IBM WebSphere Application ServerVersion 6.0

Product List

--------------------------------------------------------------------------------BASE installed

Installed Product--------------------------------------------------------------------------------Name IBM WebSphere Application ServerVersion 6.0.2.0ID BASE

Build Level o0526.07Build Date 6/29/05

--------------------------------------------------------------------------------End Installation Status Report


54/431


---------------------------------------------------------------------------------

For the plug-ins fix pack, the commands are:

cd Program Files\IBM\WebSphere\Plugins\binversionInfo.bat

Check the output from the versionInfo command for the following entry:

Name Web server plug-ins for IBM WebSphere Application ServerVersion 6.0.2.0

Example 2-2 lists a sample report.

Example 2-2 Plug-ins fix pack report

WVER0010I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.WVER0011I: WebSphere Application Server Release 6.0WVER0012I: VersionInfo reporter version 1.15.3.1, dated 4/25/05

--------------------------------------------------------------------------------IBM WebSphere Application Server Product Installation Status Report--------------------------------------------------------------------------------

Report at date and time 2005-09-30 16:34:39-0400

Installation--------------------------------------------------------------------------------Product Directory C:\Program Files\IBM\WebSphere\Plugins

Version Directory C:\ProgramFiles\IBM\WebSphere\Plugins\properties\versionDTD Directory C:\ProgramFiles\IBM\WebSphere\Plugins\properties\version\dtdLog Directory C:\Program Files\IBM\WebSphere\Plugins\logsBackup Directory C:\ProgramFiles\IBM\WebSphere\Plugins\properties\version\update\backupTMP Directory C:\DOCUME~1\admin\LOCALS~1\Temp

Installation Platform

--------------------------------------------------------------------------------Name IBM WebSphere Application ServerVersion 6.0

Product List--------------------------------------------------------------------------------


55/431


-

Installed Product

--------------------------------------------------------------------------------Name Web server plug-ins for IBM WebSphere ApplicationServerVersion 6.0.2.0ID PLGBuild Level o0526.07Build Date 6/29/05

-------------------------------------------------------------------------------

-End Installation Status Report--------------------------------------------------------------------------------

There is no versionInfo command to check the IBM HTTP Server version. In

order to verify that the correct version is installed, you must open the Serviceswindow. Do this by:

Start Settings Control Panel Administrative Tools Services

Highlight IBM HTTP Server 6.0 by clicking once on this selection. A descriptionof this service will appear to the left of the list. You should seeIBM_HTTP_Server/6.0.2. You can see an example of this in Figure 2-23.

Figure 2-23 IBM HTTP Server version verification

2.5 Verification

The following steps will guide you through the verification process.

Step 1. Start the serversMake sure that the IBM HTTP Server and the WebSphere Application Server

have started. For example:


56/431


To check the status of the IBM HTTP Server, go to Start Settings ControlPanel Administrative Tools Services.

The status should be Started for IBM HTTP Administration V6.0 and IBM HTTPServer V6.0. If the status is Stopped, right-click, and select Start. For example:

Start Programs IBM HTTP Server 6.0 Start HTTP Server

To start the WebSphere Application Server, go to Start Programs IBM

WebSphere Application Server v6 Profiles default Start theServer.

Step 2. Administrative consoleOpen the Administrative Console by entering the following command:

Start>Programs>IBM WebSphere>Application Server v6>Profiles>default>Administrative Console

Log in to the administrative console and select Servers on the left side of the

console. The selection will drop down with two options. Select Web servers. Youshould see the unique Web server name that you created during the Plug-ins

installation. An example of this can be seen in Figure 2-24.

Figure 2-24 Web server verification

Step 3. SnoopWe also recommend you execute the servlet Snoop. Open a Web browser and

change the address to http://your_hostname/snoop. In this scenario, the addressi htt // d6/ A l f thi b i Fi 2 25


57/431


is http://wsed6/snoop. An example of this can be seen in Figure 2-25.

Figure 2-25 Snoop Servlet

2.6 DB2 installation

The installation of DB2 is now described in detail. This installation assumes thatyou are installing DB2 Universal Database Workgroup v8.2.

Step 1. Starting the installation

Insert the DB2 8.2 CD into the CD-ROM drive. The InstallShield Wizard shouldstart automatically depending on whether or not you have autostart enabled for

the CD-ROM drive. If it does not start, you will need to perform the followingactions:

Open the command prompt by selecting Start Run.

When the Run dialog box appears, type cmd in the open text entry field andthen click OK.

When the command prompt window appears, type the following command

and substitute the appropriate location and drive letter for your CD-ROMdrive:

C:\db2>setup.exe

Step 2. IBM DB2 Setup LaunchpadThe Launchpad window will open. The Launchpad has links to other information

concerning the prerequisites and release notes on the left side of the window.Select Install Product See Figure 2 26


58/431


Select Install Product. See Figure 2-26.

Figure 2-26 IBM DB2 Setup Launchpad

The next window asks you to choose which product you would like to install. See

Figure 2-27. Select DB2 UDB Workgroup Server Unlimited Edition and clickNext.

Figure 2-27 Product selection

Step 3. DB2 Setup wizardThe DB2 Setup wizard appears and will install DB2 UDB Workgroup Server

Unlimited Edition. Click Next.


59/431


Step 4. License agreement

The license agreement appears. To proceed, you are required to read this andselect I accept the terms in this license agreement. Click Next.

Step 5. Installation typeIn Figure 2-28, the Setup window shows three options:

Typical Compact Custom

Select Typical installation, since it is installed with the most features andfunctionality and uses a typical configuration with default values. Click Next.

Figure 2-28 Installation type

Step 6. Installation locationThe Setup wizard will now display the default installation directory setting for DB2Workgroup Unlimited Edition as shown in Figure 2-29 on page 44. To install the

product in a different folder, click Change and select another folder. When youare finished, click Next.


60/431


Figure 2-29 Installation location

Step 7. User informationThe Setup wizard will now ask you to set the user information for the DB2

Administration Server as seen in Figure 2-30. You can use a domain user or alocal user. Click Next.

Figure 2-30 Set user information

Step 8. Administration contact listThe Administration contact list will store contact information used to notify

administrators that a database requires attention. You can create a local contact

list or use an existing global contact list as seen in Figure 2-31. After you specifyyour contact list, click Next.


61/431


Figure 2-31 Administration contact list

Step 9. Configure DB2 instancesIn Figure 2-32 on page 46, the Setup wizard displays the instances that will becreated during the installation. If you do not change the protocol and startupsettings, default values will be used. Click Next.


62/431


Figure 2-32 Configure DB2 Instances

Step 10. DB2 tool catalogThe Setup wizard will now ask you whether or not you want to prepare the DB2

tools catalog. Before you can use certain DB2 tools, you must create the DB2tools catalog. Click Next.

Step 11. Health monitor notificationThe health monitor notification is set up to

Documents

WebSphere Everyplace Deployment V6 Handbook for Developers and Administrators Volume One