IBM SG24-6320-00 User Manual

Download

Front cover

Draft Document for Review July 28, 2004 7:33 pm SG24-6320-00

Keeping Commerce ce Applications Updateddated

WebSphere Commerce 5.1 to 5.6 Migration Guide

Migration Strategy and Planning

Production and Development Environments

Step-by-Step Instructions

ibm.com/redbooks

Hernan Cunico

Andrew Hays

Steve Insley Khurram Wyne Nicolai Nielsen

Sanjeev Sharma

Sanjay Shah

Drake Philbrook

Draft Document for Review July 28, 2004 7:33 pm 6320edno.fm

International Technical Support Organization

Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

July 2004

SG24-6320-00

6320edno.fm Draft Document for Review July 28, 2004 7:33 pm

Note: Before using this information and the product it supports, read the information in

“Notices” on page xi.

First Edition (July 2004)

This edition applies to Version 5, Release 6, Modification 0 of WebSphere Commerce.

This document created or updated on July 28, 2004.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Draft Document for Review July 28, 2004 7:33 pm 6320TOC.fm

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Part 1. Introduction to WebSphere Commerce V5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 Structure of the book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2. WebSphere Commerce V5.6 Overview . . . . . . . . . . . . . . . . . . . . 7

2.1 Product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2 WebSphere Commerce software components . . . . . . . . . . . . . . . . . . . . . 10

2.2.1 Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2.2 WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2.3 Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.2.4 WebSphere Commerce Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.2.5 WebSphere Commerce Payments Server . . . . . . . . . . . . . . . . . . . . 13

2.2.6 Enablement software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.3 WebSphere Commerce Server subsystems . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.1 Member subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.2 Catalog subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3.3 Trading subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.4 Order subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.5 Merchandising subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.6 Marketing subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.7 Inventory subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.8 Messaging subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.4 WebSphere Commerce Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.5 WebSphere Commerce Business models. . . . . . . . . . . . . . . . . . . . . . . . . 22

2.5.1 Direct Sales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.5.2 Value Chain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.5.3 Hosting Ex-Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.6 What’s new in WebSphere Commerce V5.6 . . . . . . . . . . . . . . . . . . . . . . . 26

2.6.1 WebSphere Commerce Development Environment . . . . . . . . . . . . . 26

6320TOC.fm Draft Document for Review July 28, 2004 7:33 pm

2.6.2 WebSphere Commerce Payments . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.6.3 Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.6.4 Loader Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.6.5 Password Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.6.6 Adaptor for CrossWorld. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.6.7 Catalog and product management . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.6.8 Business Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.6.9 Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.6.10 Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.6.11 Campaigns and Promotions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.6.12 Order and inventory Management . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.6.13 Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.6.14 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.6.15 Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.6.16 Product Advisor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 3. Migration Strategy and Planning. . . . . . . . . . . . . . . . . . . . . . . . 37

3.1 Migration Strategy considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.1.1 Add or replace functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.1.2 Take advantage of DynaCache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.1.3 Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.1.4 External product and user management . . . . . . . . . . . . . . . . . . . . . . 39

3.1.5 How does custom code impact the process? . . . . . . . . . . . . . . . . . . 39

3.1.6 Prepare a detailed Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.2 Migration Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.2.1 Skill requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.2.2 Hardware and software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 41

3.3 Product versions mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.4 Migration approach for development environment . . . . . . . . . . . . . . . . . . 44

3.5 Migration approaches for runtime environment. . . . . . . . . . . . . . . . . . . . . 45

3.5.1 Switch-Over migration scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.5.2 Co-existence migration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.5.3 In-place migration scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.6 Approach used for this migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.6.1 Detailed overview of development migration steps. . . . . . . . . . . . . . 50

3.6.2 Detailed overview of production environment migration . . . . . . . . . . 51

Chapter 4. Commerce Application used during the migration . . . . . . . . . 55

4.1 Commerce application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.1.1 Application environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.2 Commerce customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.2.1 Shopping flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.2.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

iv Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320TOC.fm

4.2.3 Database tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.3 Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.4 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Part 2. Development environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 5. Installing WebSphere Commerce Development Environment 67

5.1 Development environment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.2 Pre-installation requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.2.1 VisualAge for Java V4.0 prerequisites . . . . . . . . . . . . . . . . . . . . . . . 69

5.3 Installing WebSphere Studio Application Developer . . . . . . . . . . . . . . . . . 69

5.3.1 Pre-installation steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.3.2 Installing WebSphere Studio Application Developer V5.1.1 . . . . . . . 70

5.3.3 Apply fixes to the test environment . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.4 Installing WebSphere Commerce V5.6 Toolkit . . . . . . . . . . . . . . . . . . . . . 75

5.4.1 Installing WebSphere Commerce V5.6 Toolkit . . . . . . . . . . . . . . . . . 76

5.5 Installing DB2 Universal Database V8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.5.1 Backup development databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.5.2 Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

5.5.3 Preparing a Windows user for DB2. . . . . . . . . . . . . . . . . . . . . . . . . . 79

5.5.4 Installing DB2 Universal Database V8.1 . . . . . . . . . . . . . . . . . . . . . . 80

5.5.5 Installing DB2 Universal Database fixpack 5 . . . . . . . . . . . . . . . . . . 83

5.5.6 Migrate databases to DB2 Universal Database V8.1 level . . . . . . . . 85

5.6 Configuring the development environment for DB2 . . . . . . . . . . . . . . . . . 85

5.7 Installing VisualAge for Java V4.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

5.7.1 Installing VisualAge for Java V4.0. . . . . . . . . . . . . . . . . . . . . . . . . . . 87

5.7.2 Configuring VisualAge for Java V4.0 . . . . . . . . . . . . . . . . . . . . . . . . 89

Chapter 6. Pre-migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

6.1 Preparation overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

6.2 Instance preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

6.2.1 Updating the product information file . . . . . . . . . . . . . . . . . . . . . . . . 97

6.2.2 Prepare resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

6.2.3 Merge EJB groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

6.2.4 Export code from VisualAge for Java V3.5.3 . . . . . . . . . . . . . . . . . 100

6.3 Database preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

6.3.1 Update database configuration values . . . . . . . . . . . . . . . . . . . . . . 102

6.3.2 Unsent messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

6.3.3 Order status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

6.3.4 Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

6.3.5 Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6.3.6 Custom message types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

6.3.7 Dropping foreign key references . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

6.3.8 Erroneous data in encrypted fields . . . . . . . . . . . . . . . . . . . . . . . . . 109

Contents v

6320TOC.fm Draft Document for Review July 28, 2004 7:33 pm

Chapter 7. Migrating the development environment . . . . . . . . . . . . . . . . 111

7.1 Current development environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

7.2 Development environment migrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

7.3 Migrating the development instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

7.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

7.3.2 Running the tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

7.4 Migrating the development database . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

7.4.1 Migrating unencrypted data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

7.4.2 Migrating encrypted data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

7.4.3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

7.5 Migrating custom EJBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

7.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

7.5.2 Export the EJB project from VisualAge for Java V3.5.3 . . . . . . . . . 120

7.5.3 Import the EJB projects into VisualAge for Java V4.0. . . . . . . . . . . 121

7.5.4 Regenerate the deployed code for the EJBs . . . . . . . . . . . . . . . . . 122

7.5.5 Export EJBs as EJB 1.1 JAR files. . . . . . . . . . . . . . . . . . . . . . . . . . 122

7.5.6 Import the EJBs into WebSphere Studio Application Developer. . . 123

Chapter 8. Post-migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

8.1 Setting up aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

8.2 Migrating custom code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

8.2.1 Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

8.2.2 Command parameter validation . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

8.2.3 User registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

8.2.4 Logon command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

8.2.5 Calculation usage framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

8.2.6 Configuration and code changes for migrated EJBs. . . . . . . . . . . . 144

8.2.7 J2EE Connector Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

8.2.8 Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

8.2.9 Product Advisor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

8.2.10 Rule server administration commands . . . . . . . . . . . . . . . . . . . . . 155

8.2.11 JSP and property file changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Part 3. Production environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Chapter 9. Installing WebSphere Commerce V5.6 . . . . . . . . . . . . . . . . . . 163

9.1 Single-node runtime overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

9.1.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

9.1.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

9.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

9.2.1 Install WebSphere Commerce V5.6 . . . . . . . . . . . . . . . . . . . . . . . . 166

9.2.2 Configuring IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

9.3 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

9.3.1 Verify installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

vi Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320TOC.fm

9.3.2 Create test instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

9.3.3 Removing test instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 10. Pre-migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

10.1 Preparation overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

10.2 Instance preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

10.2.1 Updating the product information file . . . . . . . . . . . . . . . . . . . . . . 185

10.2.2 Prepare resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

10.2.3 Disable security on WebSphere Application Server . . . . . . . . . . . 188

10.3 Database preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

10.3.1 Unsent messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

10.3.2 Copying the database from Commerce V5.1 to Commerce V5.6 . 190

10.3.3 Updating database configuration values . . . . . . . . . . . . . . . . . . . . 192

10.3.4 Orders status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

10.3.5 Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

10.3.6 Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

10.3.7 Custom message types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

10.3.8 Dropping foreign key references . . . . . . . . . . . . . . . . . . . . . . . . . . 199

10.3.9 Erroneous data in encrypted fields . . . . . . . . . . . . . . . . . . . . . . . . 200

Chapter 11. Migrating WebSphere Commerce components . . . . . . . . . . 201

11.1 Migration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

11.2 Migrating commerce instance configuration . . . . . . . . . . . . . . . . . . . . . 202

11.2.1 Migrating the instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

11.3 Migrating commerce database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

11.3.1 Migrating the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

11.3.2 Choosing the master catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

11.3.3 Migrating the encrypted data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

11.4 Migrating Payment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

11.4.1 Install Fixpack for WebSphere Payment Manager . . . . . . . . . . . . 218

11.4.2 Install WebSphere Commerce Payments remote node . . . . . . . . 219

11.4.3 Package and transfer the WCIM tool . . . . . . . . . . . . . . . . . . . . . . 221

11.4.4 Backup the WebSphere Payment Manager instance . . . . . . . . . . 222

11.4.5 Backup the WebSphere Payment Manager database . . . . . . . . . 223

11.4.6 Transfer assets to WebSphere Commerce Payments node . . . . . 224

11.4.7 Restore WebSphere Payment Manager database . . . . . . . . . . . . 224

11.4.8 Migrate the WebSphere Payment Manager instance . . . . . . . . . . 224

11.4.9 Migrate the WebSphere Payment Manager database . . . . . . . . . 227

Chapter 12. Post-migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

12.1 Post migration steps for IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . 230

12.1.1 Migrating static content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

12.1.2 Updating configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

12.2 Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Contents vii

6320TOC.fm Draft Document for Review July 28, 2004 7:33 pm

12.2.1 Deploying EJBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

12.2.2 Deploying commands and databeans . . . . . . . . . . . . . . . . . . . . . . 233

12.2.3 Deploying store assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Part 4. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Appendix A. Managing WebSphere Commerce components . . . . . . . . . 239

WebSphere Commerce instance management . . . . . . . . . . . . . . . . . . . . . . . 240

Checking instance status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Starting the instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Stopping the instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

WebSphere Commerce Payments instance management . . . . . . . . . . . . . . 241

Checking instance status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Starting the instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Stopping the instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Start the Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Restarting IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Modifying trace strings for a running server . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Tracing with WebSphere Commerce V5.6 Toolkit . . . . . . . . . . . . . . . . . . . . . 247

Tracing for Lightweight WebSphere Test Environment. . . . . . . . . . . . . . . 247

Tracing for Full WebSphere Test Environment . . . . . . . . . . . . . . . . . . . . . 248

Create missing password scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Create wcs_password script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Create wcs_pmpassword script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Appendix B. Backup WebSphere Commerce Suite V5.1 . . . . . . . . . . . . . 251

File system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Default directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Custom directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Appendix C. Migration scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

WebSphere Commerce V5.6 migration scripts behavior . . . . . . . . . . . . . . . . 256

migratedb.bat behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

migrateEncryptedInfo.bat behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

wcim.bat behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Custom database migration scripts behavior . . . . . . . . . . . . . . . . . . . . . . . . . 260

Database preparation batch script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Database preparation SQL script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Database migration batch script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Database post migration batch script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Database post migration SQL script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

viii Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320TOC.fm

Appendix D. Moving from single to multi-node environment . . . . . . . . . 267

Single-node environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Installing and configuring the database node . . . . . . . . . . . . . . . . . . . . . . . . . 268

Create a Windows user for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Installing DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Moving the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Connecting to the remote database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Verify connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Appendix E. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Contents ix

6320TOC.fm Draft Document for Review July 28, 2004 7:33 pm

x Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320spec.fm

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. Consult your 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 IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility 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 provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES

THIS 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 disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to 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 at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials 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 without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements 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 on the 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 them as 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 business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any 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 the sample 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 of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

6320spec.fm Draft Document for Review July 28, 2004 7:33 pm

Trademarks

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

AFP™ Approach® Cloudscape™ CrossWorlds® DB2 Universal Database™ DB2® Domino®

Eserver®

The following terms are trademarks of other companies:

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.

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

eServer™ ibm.com® IBM® Intelligent Miner™ iSeries™ Lotus® Notes® Perform™

QuickPlace® Redbooks ™ Sametime® Tivoli® VisualAge® WebSphere® z/OS®

xii Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320pref.fm

Preface

This redbook is based on our experience migrating a customer application. Carrot Bunch Companies, Inc is the customer that provided the application, Chapter 4, “Commerce Application used during the migration” on page 55 covers the details of the application, runtime used, hardware specification and degree of customization.

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.

Figure 0-1 The team who wrote this book. From left to right: Sanjeev Sharma, Hernan Cunico, Andrew Hays, Drake Philbrook, Steve Insley, Sanjay Shah, Nicolai Nielsen and Khurram Wyne.

6320pref.fm Draft Document for Review July 28, 2004 7:33 pm

Hernan Cunico is an Senior I/T Specialist, WebSphere Specialist at the IBM

International Technical Support Organization (ITSO), Raleigh Center. He has nine years of experience in Information Technology and e-business consulting. Hernan has written extensively on WebSphere Commerce and Application Server. His areas of expertise include networking, Internet security, e-business and e-commerce solutions architecture.

Andrew Hays is a Senior IT Consultant at Daniel IT Services, Inc., located in Athens, AL. He has over four years of experience in information systems focusing on internet technologies. His areas of expertise include internet site development, web application design & development, systems integration, and WebSphere Commerce solutions. He holds a degree in Computer Science from Athens State University in Athens, AL. Over the last three years he has worked on several WebSphere Commerce Suite V5.1 projects.

Steve Insley is a Senior IT Consultant / Lead Architect for Retail at European Technology Consultants Ltd. in the United Kingdom. He has seven years of experience in the field of application development, system integration and consulting for e-commerce and e-business solutions. He also has four years experience in technical architecture and design. Steve holds a degree in Computer Science from the University of Warwick, England. He has written extensively on WebSphere Commerce and worked on several major WebSphere Commerce customer engagements in the UK.

Khurram Wyne is an I/T Specialist with IBM Global Services Denmark. He has 4 years of experience in application development, systems integration and consulting for J2EE solutions. He holds a Software Engineering degree from Ballerup Technical University in Denmark. His areas of expertise include application design and architecture, systems integration and WebSphere Commerce solutions (including V5.1 and V5.4).

Nicolai Nielsen is an I/T Specialist with IBM Global Services Denmark. He has nine years of experience in the field of consulting, application development and systems integration. Nicolai holds a degree in Engineering from the Technical University of Denmark. Over the last three years, he has worked on several WebSphere Commerce B2C and B2B projects.

Sanjeev Sharma is a team lead of WebSphere Commerce Solutions in IBM Canada’s software development lab in Toronto. He has 5 years of experience in WebSphere Commerce and database administration fields. He holds a Computer Engineering degree from McGill University in Canada. His areas of expertise include solution design, installation, integration and testing. He has written extensively on installation and integration test methodologies.

Sanjay Shah works for IBM Global Services and is an Advisory I/T Specialist for the e-Commerce Solutions practice, which is responsible for defining,

xiv Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320pref.fm

architecting, developing and implementing Enterprise B2C and B2B e-Commerce solutions. He has over five years experience in Product Integration, Information Technology and e-business consulting. Sanjay is skilled in providing infrastructure support, e-commerce solutions, application development and formal document writing.

Drake Philbrook is the Vice President of WebSphere Commerce Practice for Shared Vision Group. Shared Vision Group is an IBM ISSW Core Business Partner working directly with the IBM Commerce Lab to deliver WebSphere Commerce implementation and enablement. Drake is a Senior Web Architect with over 20 years of software development and technical consulting experience and a focus on Java-based enterprise solutions.

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

David Yuan, IBM Canada Michael Au, IBM Canada Yanchun Zao, IBM Canada Cherry Cheng, IBM Canada Bing Jiang Sun, IBM China

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase 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:

Preface xv

6320pref.fm Draft Document for Review July 28, 2004 7:33 pm

 Use the online Contact us review redbook form found at:

ibm.com/redbooks

 Send your comments in an Internet note to:

redbook@us.ibm.com

 Mail your comments to:

IBM Corporation, International Technical Support Organization Dept. HZ8 Building 662 P.O. Box 12195 Research Triangle Park, NC 27709-2195

xvi Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320p01.fm

Part 1

Part 1 Introduction to

WebSphere Commerce V5.6V5.6

6320p01.fm Draft Document for Review July 28, 2004 7:33 pm

2 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_intro.fm

Chapter 1. Introduction

This book describes all the necessary steps needed to successfully migrate a WebSphere Commerce Suite V5.1 application to WebSphere Commerce V5.6 on the Microsoft Windows 2000 platform. This book covers both production and development environments.

6320ch_intro.fm Draft Document for Review July 28, 2004 7:33 pm

1.1 Overview

Migrating complex applications as WebSphere Commerce always demands a lot of effort and preparation. In this book we used a WebSphere Commerce Suite V5.1 customer application as the starting point, a sample site, for the version-to-version migration scenario.

This book covers all the steps we followed to migrate that application as well as the development environment from WebSphere Commerce Suite V5.1 to WebSphere Commerce V5.6.

Some things were changed from the original customer scenario, some extra customization has been done in order to make that application more generic and to cover more topics during the migration process. The following chapters will provide details about the application as it is today and how is was migrated.

For a real WebSphere Commerce Suite V5.1 customer environment we choose Carrot Bunch Companies, Inc. We will refer to this customer from now on as Carrot Ink. This customer is already a success story implementing WebSphere Commerce Suite V5.1 in 2002, the following URL provides the details of this implementation.

http://www.ibm.com/software/success/cssdb.nsf/CS/CDIR-5GRNK9

Changes done from the original customer environment (just for the purposes of this book) and the differences from the default (out-of-the-box) implementation in terms of WebSphere Commerce customization, Catalog, Database and shopping flow are described in detail in Chapter 4, “Commerce Application used during the migration” on page 55.

1.2 Structure of the book

This book is organized in parts and it is designed to easily identify the general concepts for the migration planning, then proceed with the actual migration procedures for both production and development environments.

Part 1, “Introduction to WebSphere Commerce V5.6”

Part 1 of the book describes how the book is laid out, what is new in WebSphere Commerce V5.6, strategy and planning as well as a description of the customer application we migrated. This part of the book is organized as follows:

 Chapter 1, “Introduction”  Chapter 2, “WebSphere Commerce V5.6 Overview”  Chapter 3, “Migration Strategy and Planning”

4 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_intro.fm

 Chapter 4, “Commerce Application used during the migration”

Part 2, “Development environment”

Part 2 of the book provides all the necessary steps to perform the development environment migration. This part of the book is organized as follows:

 Chapter 5, “Installing WebSphere Commerce Development Environment”  Chapter 6, “Pre-migration steps”  Chapter 7, “Migrating the development environment”  Chapter 8, “Post-migration steps”

Part 3, “Production environment”

Part 3 of the book provides all the necessary steps to perform the production environment migration. This part of the book is organized as follows:

 Chapter 9, “Installing WebSphere Commerce V5.6”  Chapter 10, “Pre-migration steps”  Chapter 11, “Migrating WebSphere Commerce components”  Chapter 12, “Post-migration steps”

Part 4, “Appendixes”

Part 4 of the book provides additional information on managing the different components of the WebSphere Commerce environment and detailed information about the scripts behaviors. This part of the book is organized as follows:

 Appendix A, “Managing WebSphere Commerce components”  Appendix B, “Backup WebSphere Commerce Suite V5.1”  Appendix C, “Migration scripts”  Appendix D, “Moving from single to multi-node environment”  Appendix E, “Additional material”

Chapter 1. Introduction 5

6320ch_intro.fm Draft Document for Review July 28, 2004 7:33 pm

6 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

Chapter 2. WebSphere Commerce V5.6

Overview

This chapter provides an overview of WebSphere Commerce V5.6. Sections include an overview of the product, tools used to manage a site or store, and a description of the business and data models.

The chapter is organized into the following sections:

 Product overview  WebSphere Commerce software components  WebSphere Commerce Server subsystems  WebSphere Commerce Tools  WebSphere Commerce Business models  What’s new in WebSphere Commerce V5.6

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

2.1 Product overview

WebSphere Commerce V5.6 provides you with all the functionality that is needed to have a fully functional e-commerce site. It runs on industry leading products like DB2 and WebSphere Application Server. It is designed for security, scalability and performance that any e-commerce site demands. It comes pre-packaged with all the software required to have a fully functional e-commerce site.

In this section we introduce the key components of the WebSphere Commerce runtime architecture. We have categorized the components for the WebSphere Commerce Server as follows (see Figure 2-1 on page 10):

 WebSphere Commerce software components

We have listed the primary software components for WebSphere Commerce.

There are many additional software components included in the IBM

WebSphere Commerce V5.6 product packaging that have not been listed

here but that can be integrated with WebSphere Commerce.

–Web server – WebSphere Application Server – Database Server – WebSphere Commerce Server – WebSphere Commerce Payments Server – Enablement software

 WebSphere Commerce Server subsystems

The subsystems run within the WebSphere Commerce enterprise application

on the WebSphere Commerce Server, and provide the infrastructure to

support the features used by the administration tooling and stores.

– Member subsystem – Catalog subsystem – Trading subsystem – Order subsystem – Merchandising subsystem – Marketing subsystem – Inventory subsystem – Messaging subsystem

 Common server runtime (framework)

The common server runtime provides a framework in which the commerce

applications are deployed and executed.  Business interaction engine

8 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

The subsystems and server runtime operate within an interaction engine that

provides all of the components with the necessary business context. These

are governed by the contextual frameworks such as policies, entitlement,

stores, personalization, and globalization.  Administration tools

The administration tools are used to configure and manage the WebSphere

Commerce site and store operations.

– WebSphere Commerce Configuration Manager – WebSphere Commerce Administration Console – WebSphere Commerce Accelerator – WebSphere Commerce Organization Administration Console – WebSphere Commerce Payments Administration Console. – WebSphere Commerce Password Manager

Chapter 2. WebSphere Commerce V5.6 Overview 9

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

Web Browser Administration Tools

WC Payments Administration Console

Administration

Console

Commerce

Accelerator

Organization

Administration

Console

Development Tools

WebSphere Commerce

Developer

Configuration Tools

Configuration

Manager

(client)

Web Server + WebSphere plug-in

WebSphere Commerce node

WebSphere Application Server

WebSphere Commerce Payments Server

WebSphere Commerce Server

Administration tools

Administration

Console

Business Interaction Engine

Policies EntitlementStores

Personalization

Subsystems

Member

Subsystem

Marketing

Subsystem

Inventory

Subsystem

Configuration Manager Server

Commerce

Accelerator

Common Server Runtime

Trading

Subsystem

Merchandizing

Subsystem

WebSphere Commerce

<instance>.xml

Organization

Administration

Console

Globalization

Catalog

Subsystem

Messaging

Subsystem

Q T P

Order

C S

Database ServerDatabase Server

WebSphere Commerce instance database

WebSphere Commerce Payments database

a i

Transport adapters

Figure 2-1 WebSphere Commerce Server runtime components

2.2 WebSphere Commerce software components

There are many software components included with IBM WebSphere Commerce V5.6. In this section, we will limit our discussion to the following software components of the WebSphere Commerce runtime architecture:

10 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

 Web server  WebSphere Application Server  Database Server  WebSphere Commerce Server  WebSphere Commerce Payments Server

Note: The WebSphere Commerce node architecture depicted in Figure 2-1 on page 10 shows a single-node configuration. The software components listed in this section can be distributed on separate nodes for scalability and security reasons.

2.2.1 Web server

The Web server can be installed on the WebSphere Commerce node or a remote node, which can be optionally clustered for load balancing using the WebSphere Application Server V5, Network Deployment Edition Edge components. Regardless of whether the Web server is local or remote, it must be configured to use the WebSphere Application Server plug-in. There are several supported Web server plug-ins. The IBM HTTP Server and plug-in are found on the WebSphere Application Server CD included with WebSphere Commerce.

The majority of the WebSphere Commerce tooling and store application assets are J2EE components (JSPs, servlets, EJBs, etc.) that run on the application server located on the WebSphere Commerce node. There are some static HTML pages and images found in the WebSphere Commerce tools and stores that can be served by the Web server.

Incoming HTTP requests from Web browser clients are received by the Web server and WebSphere plug-in. The WebSphere plug-in, via the use of the plugin-cfg.xml file, redirects requests to applications on the WebSphere Application Server on the WebSphere Commerce node.

2.2.2 WebSphere Application Server

The WebSphere Commerce Server leverages the J2EE technologies provided by the WebSphere Application Server such as JSPs, servlets (WebSphere Commerce commands), EJBs, XML, Web Services, security, MQ embedded messaging, etc.

IBM WebSphere Commerce V5.6 includes the IBM WebSphere Application Server V5 base edition and Network Deployment Edition. The base edition is suitable for single-node and multi-node runtime configurations. When multiple WebSphere Application Servers are needed for scalability, such as horizontal application clustering, then the Network Deployment Edition is needed.

Chapter 2. WebSphere Commerce V5.6 Overview 11

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

WebSphere Application Server now uses a web based interface which can be accessed at http://<hostname>:9090/admin by default. You must have application server named “server1” running to access this interface.

You will also notice that WebSphere Application Server no longer requires a database or a web server to be installed.

2.2.3 Database Server

DB2 Universal Database V8.1.5 is included with WebSphere Commerce V5.6. In addition, Oracle9i (9.2.0.1) Enterprise Server and Standard Edition are supported (not included). The Database Server is used for the WebSphere Commerce instance database and the WebSphere Commerce Payments database.

The WebSphere Commerce instance database is used for store configuration data such as taxes, shipping, customer profile information, and the product catalog.

The WebSphere Commerce Payments database is used for payment configuration, such as accounts, payment types, cassettes and payment transaction data.

The database server software can be installed on the same node as WebSphere Commerce or on a remote Database Server node.

2.2.4 WebSphere Commerce Server

The WebSphere Commerce Server is a WebSphere enterprise application, which runs on its own application server within the WebSphere Application Server. The WebSphere Commerce application software is installed via the WebSphere Commerce Installer.

After installation, WebSphere Commerce must be configured using the Configuration Manager. The Configuration Manager is used to create the WebSphere Commerce instance. During instance creation, an application server for the WebSphere Commerce Server and the enterprise application is deployed.

For most runtime topologies, the configuration of the WebSphere Application Server is performed for the user via the WebSphere Commerce Configuration Manager. When adding a remote Web server, remote WebSphere Commerce Payments node, and clustering using the WebSphere Application Server Network Deployment Edition, some manual configuration is needed.

12 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

2.2.5 WebSphere Commerce Payments Server

The WebSphere Commerce Payments Server is a WebSphere enterprise application that runs on its own application server within the WebSphere Application Server.

After installation, the WebSphere Commerce Payments instance must be created using the Configuration Manager. When creating a WebSphere Commerce Payments instance using the Configuration Manager, the WebSphere Commerce Payments instance application server is created and the WebSphere Commerce Payments enterprise application is deployed.

The WebSphere Commerce Payments Server can be installed on the WebSphere Commerce node or on a remote node.

2.2.6 Enablement software

There are several enablement software components included with WebSphere Commerce that can be optionally installed. In addition, we have listed WebSphere enablement software that can be leveraged by WebSphere Commerce.

WebSphere Commerce enablement software

This section describes the functionality provided by the following enablement software included with IBM WebSphere Commerce V5.6:

 Personalization

There are two personalization solutions included with WebSphere Commerce, Blaze Rules and LikeMinds collaborative filtering. The personalization software can be used to improve the customer experience by tailoring the site to a number of criteria, such as customer profile, shopping cart contents, and purchase history.

 Commerce analytics

WebSphere Commerce V5.6 has improved analytics capability through the use of WebSphere Commerce Analyzer and IBM DB2 Intelligent Miner for Data V8.1, and IBM DB2 UDB V8.1 warehousing features. There are many business intelligence reports included with WebSphere Commerce, which leverage the technology of the WebSphere Commerce Reporting Framework and are accessible from the WebSphere Commerce Accelerator.

 Messaging integration

WebSphere Commerce V5.6 includes messaging adapters for HTTP, e-mail, MQ, InterChange Server (ICS), and file. Inbound messaging supports the HTTP and MQ adapters and can be customized to support other protocols.

Chapter 2. WebSphere Commerce V5.6 Overview 13

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

Outbound messaging support includes WebSphere MQ, WebSphere InterChange Server (ICS), e-mail, and file adapters. WebSphere Commerce ships with a sample J2C-based connector that can be customized.

 Collaboration

Customer Care, which is a Lotus Sametime application integrated with WebSphere Commerce, provides live help in real time between customers and customer service representatives (CSRs).

Collaborative Workspaces, which is built-upon Lotus QuickPlace and only available with the Business Edition, provides an environment where business customers and line-of-business users can interact.

 Directory Server (LDAP)

IBM Directory Server V5.1 is an LDAP directory server included with WebSphere Commerce V5.6. WebSphere Commerce can optionally be configured to use LDAP as the member repository instead of the default WebSphere Commerce instance database. LDAP provides for better integration and single sign-on (SSO) for multiple participating applications sharing the same LDAP directory.

WebSphere enablement software

The IBM WebSphere software brand includes many enablement software solutions that can be leveraged by WebSphere Commerce. This section highlights the WebSphere Foundations, Tools and Business Portals.

 WebSphere Foundation and Tools

The WebSphere Application Server is a J2EE based application server. The WebSphere Commerce Server (application server) is an enterprise application and has its own application server. WebSphere Commerce V5.6 includes the IBM WebSphere Application Server V5.0.2 base edition and the Network Deployment Edition. WebSphere Commerce can leverage the technologies provided by the WebSphere Application Server and WebSphere tooling, namely WebSphere Studio Application Developer for the development of Java and related application assets.

 WebSphere Business Portals

WebSphere Business Portals help extend and personalize the user experience.

14 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

2.3 WebSphere Commerce Server subsystems

The WebSphere Commerce subsystems provide the database information model of a store. The information model differs from the data model in that in the data model each entity represents a table while in the information model any of the objects depicted may be mapped to the same database table, or a single object may map to several database tables.

The subsystems provide a great deal of functionality for the WebSphere Commerce Server. The subsystems are used to integrate other components and external nodes as well as make it vastly easier for the store developer to customize, deploy, and manage a store.

2.3.1 Member subsystem

The Member subsystem is a component of the WebSphere Commerce Server that provides a framework for managing the following participants of the system:

 Organizational entity (for example, IBM)  Organizational unit (for example, IBM Software Group)  Member group - group of users  Members - users, member groups, organizational entity

The member data is stored within either a WebSphere Commerce instance database or an LDAP directory server database. By default, WebSphere Commerce uses the instance database as its registry.

The major functions of the Member subsystems are to provide member registration and profile management. Other closely related services of the Member subsystem include authentication, access control, and session management.

User registration methods

To facilitate various requirements for e-commerce Web sites, WebSphere Commerce provides several methods for user registration, as seen in Figure 2-2.

Chapter 2. WebSphere Commerce V5.6 Overview 15

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

WebSphere

Commerce

Customer

WebSphere

Commerce

instance

database

Customer Service

Representative

Mass Loader

Mass Import Files

Figure 2-2 User registration and update methods

1. WebSphere Commerce online registration This involves the registration of members online for the e-commerce Web

site. Users will be prompted for registration before catalog navigation or during the order checkout process. This is the most common and direct approach of the user registration method. This method does not support mass registrations.

2. MQ WebSphere Commerce also supports member registration from back-end

systems, such as ERP systems using WebSphere MQ. To enable this method, the WebSphere Commerce message transport adapter and MQ need to be configured. WebSphere Commerce provides an inbound messaging service for creating and updating customer registration. This method is very useful if you have legacy systems, which you need to Web enable. This approach is best suited for an enterprise integration solution. By default, WebSphere Commerce does not provide outbound services over MQ for the Member subsystem.

Applications

LDAP

LDIF

JNDI

LDAP

API

2.3.2 Catalog subsystem

The Catalog subsystem provides online catalog navigation, merchandising features, interest lists, and search capabilities. The Catalog subsystem includes all logic and data relevant to a catalog, including categories, products and their attributes, items, and any associations or relationships among them. It interacts with the Member subsystems and the Order subsystems to obtain information about viewing templates and pricing. The following features are provided:

 Groupings

A generic grouping construct is introduced for categorizations of various products. The owner of a catalog group may not necessarily be the owner of all the catalog entries in the group. This allows portal owners to define the categories of products offered while other suppliers can add their products to the catalog group.

 Catalog entries

One or more catalog entries can belong to a catalog group. A set of base object types is provided to represent products, stock keeping unit (SKU) items, packages, and bundles in a catalog entry.

 Merchandising associations

These make it possible to create an association between any two catalog objects, which become cross-sells, up-sells, and promotions.

 Globalization support

The catalog design addresses the requirement to support multicultural features such as product display and currency format according to the locale.

Chapter 2. WebSphere Commerce V5.6 Overview 19

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

2.3.3 Trading subsystem

The Trading subsystem in WebSphere Commerce provides the logic, function and data relevant for negotiating the price and quantity of a product or set of products between the buyer and seller organization. For the Professional Edition, the trading subsystem includes auctions. For the Business Edition, the trading subsystem includes auctions, contracts, and Request for Quote (RFQ) components that are used to carry out specific transactions between organizations.

2.3.4 Order subsystem

The Order subsystem is a component of the WebSphere Commerce Server that provides shopping carts, order processing, and order management function support. Related services, such as pricing, taxation, payment, inventory, and fulfillment, are also part of the order subsystem. Order processing capabilities include quick order or buy, scheduled orders, multiple pending orders, reorders, and splitting or back orders.

2.3.5 Merchandising subsystem

The Merchandising subsystem is a component of the WebSphere Commerce Server that provides functionality for cross-selling, up-selling, suggested accessories, and merchandising associations between products in the catalog.

2.3.6 Marketing subsystem

The Marketing subsystem is a component of the WebSphere Commerce Server, and provides numerous marketing concepts to your site. Components of the marketing subsystem provide functionality to create marketing campaigns including product recommendations, advertisements, and electronic coupons, discounts, customer profiles, and collaboration.

2.3.7 Inventory subsystem

The Inventory subsystem provides real-time inventory management. Components of the inventory subsystem provide functionality to record inventory received from vendors and that is returned by customers, adjust inventory quantity, determine the disposition of returned inventory, and ship and receive inventory.

20 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

2.3.8 Messaging subsystem

The Messaging system provides WebSphere Commerce with the ability to communicate externally. This communication includes sending messages to and receiving messages from back-end systems or external systems, as well as sending notification to customers and administrators that events have occurred within WebSphere Commerce. This is accomplished through two subsystems: an inbound system that manages inbound messages coming from back-end and external systems, and an outbound messaging system that allows you to send notification to users as well as outbound messages to back-end systems and external systems.

For example, you can set up the messaging system to send e-mail messages notifying your customers that their orders have been shipped. The messaging system provides a mechanism for integrating WebSphere Commerce with back-end systems. You can configure WebSphere Commerce to send an outbound message to a back-end system whenever an order is created at your store. This order information can be used by the back-end system to do necessary order fulfillment processing. The back-end system can later send order status messages back to WebSphere Commerce indicating that order delivery has taken place or an order invoice has been issued. E-mail can also be sent to update the customer.

2.4 WebSphere Commerce Tools

This section gives an overview of the tools available in WebSphere Commerce V5.6. The tools help to manage all aspects of your online store. The tools allow you to manage your catalog data, process orders, manage customers, and offer discount campaigns. The development environment allows you to customize or add new functionality to your store.

WebSphere Commerce Accelerator

It can be used to maintain online stores. WebSphere Commerce Accelerator allows you to manage the catalog, including updating and adding new categories and products to the store. WebSphere Commerce Accelerator is a browser based tool.

Configuration Manager

Configuration Manager allows you to create and configure instances of WebSphere Commerce and WebSphere Commerce Payments.

Chapter 2. WebSphere Commerce V5.6 Overview 21

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

Organization Administration Console

The Organization Administration Console is used to administer users, groups, organizations, approvals, stores (if multiple stores are allowed by your business model) and associated security elements. The Organization Administration Console is a browser based tool.

Administration Console

The Administration Console allows a Site Administrator to control a site or store by completing administrative operations and configuration tasks. The Administration Console allows complete administrative operations at the site level or the store level. The Administration Console is a browser based tool.

The store publish functionality provided by the Store Services Tool in WebSphere Commerce Suite V5.1 has been merged into this tool.

Password Manager

The Configuration Password Manager tool is an extension of the Configuration Manager to meet strict corporate standards to manage an instance. It enables individual users with different roles to enter their passwords to be used in a single WebSphere Commerce instance. This eliminates the need for the WebSphere Commerce site administrator to know the passwords for individual users.

For example, Database Administrators can enter their passwords through the Password Manager for a particular instance. When a Site Administrator launches the Configuration Manager instance creation wizard, WebSphere Commerce populates the field and does not prompt the Site Administrator to enter the Database Administrator's password.

The supported role types are as follows:

 Collaboration Administrator  QuickPlace Administrator  LDAP Administrator  Database User  Database Administrator

2.5 WebSphere Commerce Business models

Business models represent sample business scenarios where WebSphere Commerce may be implemented. A business model provided within WebSphere Commerce includes an organization structure, default user roles and access control policies, one or more starter stores, administration tools, and business processes that demonstrate best practices. A business model can be customized

22 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

to support business requirements and scenarios. A business model is packaged in a composite store archive file format (SAR) and is deployed by publishing that SAR file using the Administration Console.

The business processes within each business model are grouped into three areas:

 Administrative processes: Administrative processes are those processes

that are used to administer a site, a store, or an organization. These processes are normally used as they come packaged with WebSphere Commerce. However, you may feel the need to customize these processes for your application.

 Starter stores: Starter stores provide sample processes that can be

implemented for many different kinds of stores. The diversity of the sample processes can be used to implement a wide range of business requirements. The starter stores can be used as a starting point. However, you may need to change or add processes to fit your requirements. This will require changes to be made to the site design.

A business model differs from a starter store, as a starter store provides the assets (JSP pages and sample data) to demonstrate the key features of a typical store flow.

 Solution: A solution combines the administrative processes and starter store

processes into a high-level view of how these processes work together. A solution gives a clear picture of the relationship between the process groups.

The sample stores are built to represent direct sales (Consumer direct and B2B Direct), value chain (demand chain and supply chain), and hosting scenarios. Consumer Direct is a Business to Consumer (B2C) store and all others are different forms of Business to Business (B2B) stores - B2B Direct and B2B Indirect (Value Chain and Hosting Ex-Sites) stores. The consumer direct model is included in the WebSphere Commerce Professional and Business Editions. All other models are only supported by the Business Edition.

2.5.1 Direct Sales

Direct sales model involve two parties - seller and buyer. Depending on the fact if the buyer is a consumer or another business two business models result.

Consumer direct

The Consumer direct model supports commerce transactions directly between businesses and consumers. The transactions may involve products, services, or information exchange. The customers typically purchase the goods or services directly from a business.

Chapter 2. WebSphere Commerce V5.6 Overview 23

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

In this model, the business can be a retailer, a manufacturer, or any other business that sells goods or provides services directly to consumers.

B2B direct

The B2B direct model supports commerce transactions between two businesses or parties. The transactions may involve products, services, or information exchange. In the B2B direct model, customers may be business buyers, resellers, distributors, or trading partners. The customers obtain information about the products or servers and are able to purchase or otherwise obtain the goods or services directly from the seller.

2.5.2 Value Chain

Value chains support transactions involving multiple enterprises or parties. Products, goods, services, or information are delivered through the parties of the value chain from producers to end users. A value chain also has relationship and administrative aspects, that is, you can manage the relationship of the partners or enterprises in your value chain, as well as offer some administrative services to those parties. As a result, value chains must manage the two sides of their businesses: their customers and direct sales, and their channel partners and suppliers. Each of these sides requires its own management channels and practices.

In order to manage their relationships with partners or suppliers, value chain business models usually include a hub (in WebSphere Commerce known as a hub store). Value chain administrators can administer the operational aspects of the value chain in the hub store, including enabling partners or suppliers to participate in the value chain, that is, registering them, setting them up, creating collaborations. Partners and suppliers can also access the hub store to complete administrative tasks such as registering users.

In order to sell directly to customers (direct sales), value chains usually include a store front, where customers can purchase their good or services directly. WebSphere Commerce supports the transactions through, and relationship management of the following two types of value chains:

Demand chain

A demand chain is composed of the organizations that sell a business’ goods or services. An example of a demand chain would start with the buyers who make the purchase transaction, the resellers who sell the manufacturer’s goods, and the manufacturer who produce the goods. Direct sales channels are also supported by demand chains. In direct sales channels, the demand chain owner sells directly to customers or business partners.

24 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

The following are some examples of some of the demand chains supported by WebSphere Commerce.

Buyers, resellers, and manufacturers

Buyers purchase goods from a manufacturer’s resellers. Resellers, in turn, obtain the goods from the manufacturer, via the manufacturer’s hub. The resellers may be hosted by the manufacturer, or the resellers may be remote.

Resellers, manufacturers, and distributors

The manufacturer provides a hub for their resellers. Resellers and other channel partners may be able to do several functions in this hub, including locating distributors of the manufacturer’s goods. In order to locate suppliers, the reseller may browse a product catalog in the private hub. If the desired products are available from more than one distributor, the reseller can check product availability, distributors’ location, and prices for various distributors. Then, if the reseller chooses, they can split their order between several distributors. The order is then sent to the distributors, who completes the transaction and delivers the goods or services to the reseller. The reseller then sells the goods or services directly to the consumer.

Supply chain

A supply chain is composed of the organizations that provide services to a business. WebSphere Commerce allows buyers and suppliers to interact directly through a private marketplace. In this private marketplace, a forum is provided for suppliers to offer goods or services for sale. Buyers are then able to enter the forum and browse and select the goods or services that is needed. Buyers can establish contractual relationships directly with individual suppliers, and they can issue RFQs or RFPs to selected suppliers.

The private marketplace does not support competitive bidding and counter-bidding or other methods of competition.

2.5.3 Hosting Ex-Sites

This business model provides an easy mechanism to manage a number of stores using one set of tools and processes.

Hosting

The hosting model supports hosting of merchants or other businesses by an Internet Service Provider (ISP) or other hosting provider. Each hosted store can have its individual catalog and various other requirements and thus could operate independent of other stores. Both B2C and B2B stores can be hosted.

Chapter 2. WebSphere Commerce V5.6 Overview 25

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

Ex-Site

An Extended Site, or Ex-Site, is a business-to-business Web site that provides a richly featured site where the selling organization can set up different storefronts to target each of their business customers. When a business customer enters the Ex-Site storefront, any discounts, product configurations, and special instructions particular to that customer are displayed.

All features of the advanced B2B direct starter store, such as approvals, and account management also apply in a Ex-Site. The distinguishing characteristic of a Ex-Site is that the Seller can provide a customized storefront and customized catalog to each business partner or customer.

2.6 What’s new in WebSphere Commerce V5.6

This section provides many of the key enhancements you would find in WebSphere Commerce with some explanation about them. This list should not be considered a comprehensive list of enhancements going from WebSphere Commerce 5.1 to WebSphere Commerce 5.6. Each release of the product includes a separate document on “What’s New” in that release. For a complete list of changes, with detailed explanations, for a given release please refer to such documents.

2.6.1 WebSphere Commerce Development Environment

WebSphere Commerce Studio is now known as WebSphere Commerce Developer. It is based on the Eclipse technology. The development environment is a fully configured workspace for WebSphere Studio Application Developer with various enhancements.

 Unlike the VisualAge for Java based development environment for

WebSphere Commerce Suite V5.1, a WebSphere Commerce run-time environment is not required.

 The WebSphere Test Environment uses full WebSphere Application Server

base edition to give you a more precise testing experience.

 WebSphere Commerce provides you with two pre-configured servers for your

testing needs in development environment - Full WebSphere Commerce Test Environment and Lightweight WebSphere Commerce Test Environment.

Here are some noteworthy version level changes:  The Enterprise Java Beans (EJB) specification level has changed from 1.0 to

1.1.

26 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

 For Web applications, the JSP level changed from 1.1 to 1.2 while the Servlet

level remains at 2.3.

 The level of the Java 2 platform that is supported has changed from 1.2 to 1.3

2.6.2 WebSphere Commerce Payments

Formerly known as Payment Manager, WebSphere Commerce Payments was integrated with WebSphere Commerce V5.5 to facilitate and automate online payment processing. As such, WebSphere Commerce Payments, or Payments, is part of the WebSphere Commerce installation and configuration. Payments now support the following cassettes:

 WebSphere Commerce Payments Cassette for VisaNet  WebSphere Commerce Payments Cassette for BankServACH  WebSphere Commerce Payments Cassette for Paymentech  WebSphere Commerce Payments CustomOffline Cassette  WebSphere Commerce Payments OfflineCard Cassette

2.6.3 Configuration Manager

Since WebSphere Commerce V5.5 the Configuration Manager contains tools to create Oracle tablespace and users, and to configure remote Web servers. Further more, you can install a remote configuration manager client and manage you instance remotely. For example, you may be running commerce on a Unix server but you can still manage your instance remotely using remote Configuration Manager client.

2.6.4 Loader Package

Formerly known as WebSphere Commerce Catalog Manager, the Loader package has been fully integrated part of WebSphere Commerce since version

5.4. However, the Loader package no longer includes the Web Editor.

2.6.5 Password Manager

In WebSphere Commerce V5.6, a new configuration tool called Password Manager allows users to manage their WebSphere Commerce passwords from a single location.

Chapter 2. WebSphere Commerce V5.6 Overview 27

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

2.6.6 Adaptor for CrossWorld

The adapter for CrossWorlds, introduced in WebSphere Commerce Suite V5.4, offers a new mechanism to extend WebSphere Commerce business integration with the InterChange Server (ICS).

2.6.7 Catalog and product management

Catalog and product management tools provide online catalog navigation, merchandising features, interest lists and search capabilities. The following section describes more in detail the new utilities included in WebSphere Commerce V5.6.

Catalog import

This utility makes it quick and easy for customers to import a new or pre-existing product catalog, stored in a spreadsheet in comma-separated values (CSV) format, into the WebSphere Commerce database.

Catalog filtering

You can create unique catalog views for different customer groups using contracts and product sets. Or, in Business Edition, you can use the Catalog Filter to exclude any of the products or categories in a master catalog that you do not want to sell at one or some of your specific store.

Master and Navigational catalog

The master catalog is the central tool for managing your store’s merchandise. This is the single catalog containing all products, items, and standard pricing for each. Every store must contain one master catalog. With one master catalog you can create various navigational catalog to provide a different catalog navigation experience to the customers.

Classification of catalog entries

Catalog entries can now be classified as products, items, packages, bundles and dynamic kits.

 Items and products

– An item is a tangible unit of merchandise that has a specific name, part

number, and price.

– A product, however, is a group of items that exhibit the same attributes.

Once all the attributes of a product have been assigned values, i.e. a product is fully resolved, it refers to an item

28 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

 Packages and bundles are groupings of catalog entries used for promotional

purposes.

– A bundle is a collection of catalog entries that allow customers to buy

multiple items with one click. If you select a bundle, the bundle must be decomposed into separate orderable SKUs that are added individually to the shopping cart before you can check it out. The bundle's price is the aggregate of the prices of all the bundle components.

– Unlike bundles, a package is an atomic collection of catalog entries.

Viewed in similar ways as a product, a package has defining attributes and is a container for fully resolved packages. A fully resolved package is comparable to an item, with its own price, and can be added to a shopping cart.

 Kit: A collection of catalog entries that are ordered as a single item. A kit is

available in one of three types: dynamic kit, prebuilt kit, and static kit.

– Dynamic kits are configurable products that you can dynamically configure

products by using an external product configurator. You can also enable product associations for merchandising purposes. These become cross-sells, up-sells, and accessories.

– A prebuilt kit is a collection of catalog entries that has a code and is

ordered as a single item.

– A static kit is a group of products that are ordered as a unit. The

information about the products contained in a static kit is predefined and controlled within WebSphere Commerce. The individual components within the order cannot be modified and must be fulfilled together. A static kit will backorder if any of its components are unavailable.

SKU generation

Once you have created your product, you must create SKUs to represent each orderable item of merchandise for sale. WebSphere Commerce can generate these SKUs for you now.

Accounts (Business Edition)

Accounts define your relationship with the various buyer organizations with which you do business. Accounts help organize contracts and orders from customer organizations, and to configure how buyers shop at your site by controlling what products can be seen and purchased by customers governed by a given contract.

Chapter 2. WebSphere Commerce V5.6 Overview 29

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

The Product Management tooling

The Product Management tooling in WebSphere Commerce Accelerator allows you to update your catalog merchandise information directly. It also allows you to create bundles, dynamic kits and pre-built kits.

2.6.8 Business Models

Where as WebSphere Commerce 5.1 started with B2C sample store (InFashion), the Business Edition of WebSphere Commerce released a little later added B2B sample store (ToolTech) to the list. The concept of business models was introduced into WebSphere Commerce V5.5. Business models are discussed more in detail in 2.5, “WebSphere Commerce Business models” on page 22.

2.6.9 Access Control

The WebSphere Commerce’s authorization model is based upon the enforcement of access control policies. Access control policies are enforced by the access control Policy Manager. In general, when a user attempts to access a protected resource, the access control policy manager first determines what access control policies are applicable for that user and then, based upon the applicable access control policies, it determines if the user is allowed to perform the requested operation on the given resource. In WebSphere Commerce V5.6 the access control is implemented by:

 Access control policies and roles: Hierarchical policy and role based

system defined during site creation and then enforce during server runtime

 Subscription based model: When an organization subscribes to policy

groups, only the policies in those policy groups will apply to the organization’s resources. Its ancestor organization’s policies will not apply.

2.6.10 Collaboration

WebSphere Commerce supports two types of collaboration functionality. To use one, or both features, you must first install the supporting software associated with each type of collaboration.

 Collaborative workspaces (Business Edition): Collaborative workspaces

support asynchronous communication by way of Lotus QuickPlace. Collaborative workspaces also requires that member data be on an LDAP server used with WebSphere Commerce, not in a relational database.

 Customer care: Customer care provides real-time customer service support

through a synchronous text interface using the Lotus Sametime server.

30 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

2.6.11 Campaigns and Promotions

New changes have been implemented in WebSphere Commerce V5.6 for campaigns and promotions. For example managing promotions where Blaze Advisor is no longer necessary.

 Promotions redesigned: The promotions system has been completely

redesigned. It now provides support for redemption limits and promotion codes. Any promotion type may be distributed as a coupon. The promotions system removes all dependency on the Blaze Advisor rule processing system. While this redesign also removes all dependency on the Blaze Advisor rule processing system, full backward compatibility is maintained for those sites that have existing Blaze licenses.

 Coupons: This feature enables you to offer electronic coupons to your

shoppers. Coupons can be collected by the shopper in a coupon wallet until they either expire, or are redeemed with a qualifying purchase.

 Rules based discount: Rule-based discounts support the following new

discount models:

– Order level shipping discount. – Buy X of item A, give another A for free. – Buy product or item A,orB,orC, and give D as a gift.

 Ad Copy: This feature now supports additional commands as click actions.

The new actions include:

– Displaying an associated promotion. – Adding an associated promotion to a customer's coupon wallet. – Adding a particular product to a customer's shopping cart, and

automatically applying an associated promotion.

2.6.12 Order and inventory Management

A number of other changes were made to the inventory subsystem in WebSphere Commerce 5.4. Please refer to WebSphere Commerce on-line help for latest information on inventory management and documentation for WebSphere Commerce 5.4 for the changes made at that time.

 Split orders (Business Edition): allows buyers to split an order based on the

availability of items in the inventory.

 RFQ (Business Edition): Various RFQ (Request For Quote) enhancements

have occurred over the different releases

 Multiple ShipTo addresses (Business Edition): ToolTech allows buyers to

select different shipping addresses for each item.

 Availability to promise: NewFashion provides customers with an availability

date for each item in their order. This feature is based on real-time inventory.

Chapter 2. WebSphere Commerce V5.6 Overview 31

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

 Refund: In order to appease a customer not satisfied with their purchase, the

merchant or seller can offer a refund. Overridable system settings controls whether certain items are refundable.

 Return Merchandise Authorization (RMA): A RMA may be issued through

a self-service interface or with the assistance of a Customer Service Representative (CSR).

2.6.13 Analytics

WebSphere Commerce Analyzer now includes redesigned installation and configuration components, decreasing install time.

 Single logon: The integration with WebSphere Commerce Analyzer has

been enhanced to support single logon. Now, users do not have to log on to the WebSphere Commerce Accelerator, and then subsequently log on to the WebSphere Commerce Analyzer to view reports.

 Authorization: You can restrict users who could view the reports and  Data Mart: A data mart, installed on a separate server (so that there is no

performance impact to the production environment), for detailed data analysis and reporting. The data mart is designed with predefined and expandable reporting tables to provide historical data for comparison purposes. A set of tools are provided to extract, transform, and load data from the WebSphere Commerce database into the data mart. There are also predefined extractions. A set of data mining tools for business intelligence analysis against the data mart are also provided.

 Reporting Framework: Over 250 reports in 15 categories ensure the user

will have the data needed specific to the area of interest. This Reporting Framework replaces the Brio Broadcast Server included in previous releases. If you want more robust reporting capability, reporting integration kits are also available for several of the commercial reporting vendors.

 WebSphere Commerce Analyzer integrated with Tivoli Web Site

Analyzer: WebSphere Commerce Analyzer is now integrated with Tivoli Web

Site Analyzer allowing you to create reports based on Tivoli Web Site Analyzer's click stream analysis capabilities.

2.6.14 Security

Various security upgrades have been applied over the releases. For more information please refer to the WebSphere Commerce documentation. However, we would discuss the impact of some of those to encrypted data in this book during migration.

32 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

2.6.15 Caching

Server-side caching improves response time and reduces system load thus boosting performance and reducing infrastructure costs. The WebSphere Commerce servlet and page caching is now part of the WebSphere Application Server dynamic caching infrastructure (Dynacache).

Dynacache

WebSphere Application Server offers a built-in dynamic cache service for serving dynamic content and caching data. There is no time-consuming installation and integration work needed to activate. DynaCache can be viewed as a sophisticated hash table, where Java object store and retrieve commands are executed in memory.

Some of the features of WebSphere Application Server dynamic cache (DynaCache) are servlet/JSP result cache, replication support, invalidation support, Edge of Network caching support and tools to assist in configuring the cache and monitoring runtime.

The cache policy is defined by a policy based cachespec.xml file. Some of the cacheable objects defined by this policy include: servlet/JSP files, command beans, Web services, cache and dependency ID's generation rules, replication policy, invalidation rules, time-out, and priority for least recently used eviction algorithm. The cachespec.xml file resides inside the Web Module WEB-INF directory and a copy of this file can be placed in the application server properties directory. It is also flexible and modifiable at runtime.

This type of cache also supports fragment caching. This is the ability to cache portions of a page. For example, instead of caching a full page MyJSP.jsp, you can choose to cache fragments, which can include the header, footer, sidebar and the main area. All of these fragments are dynamic pages that are part of the larger dynamic page for MyJSP.jsp. There is a performance gain in fragment caching but it is not dramatic because the non-cached parts of the page determine the performance.

Replication support enables cache sharing (central cache) and replication (local cache) among multiple servers and tiers. Replication uses a built-in high performance JMS broker messaging system as its underlying engine for data replication. In local cache replication among server, if there is a update to the cache, the cache server publishes a message regarding the change to the messaging broker and the changes are automatically replicated to the other servers.

Some factors to consider for fragment caching include reusability, invalidation and variations. Fragments should be able to be reused frequently enough by

Chapter 2. WebSphere Commerce V5.6 Overview 33

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

multiple users or pages. Fragments should be stable over a long enough period of time for meaningful reuse to occur.

The goal of fragment caching with DynaCache is to maximize fragment reusability and cache utilization by breaking a page into smaller and simpler page fragments. This makes any caching, even a highly dynamic page, possible.

The caching should take place as close to the user as possible, taking into consideration security and personalized data factors. For example, non-user specific data can be place closest to the user (like on an Edge Server), but secure information should be placed behind a firewall. Pages need to be fragmented out as much as possible so they can be cached at different locations. The order for placing this from close to far is: Edge server, IBM HTTP Server, WebSphere Application Server, Database Server.

WebSphere Commerce has dynamic cache enabled by default, but the cachespec.xml contains no entries for any of the provided business models. Instead, sample subsets of cachespec.xml files are provided to enable caching of the business models. They also support invalidation using different techniques.

WebSphere Commerce comes with a Dynamic Cache Monitor enterprise application that displays statistics and contents of the dynamic cache. The monitor can be accessed via a Web browser accessing the following URL:

https://<hostname>:8002/cachemonitor

This application is provided as an installable Enterprise Archive (EAR) file and can be installed in a server that has dynamic cache enabled. With this application, you can monitor caching interactively and invalidate pages.

In summary, almost everything can be cached if the pages are broken down into smaller fragments. DynaCache can be viewed as a sophisticated hash table that can increase performance and reduce infrastructure costs. Among its many features include the ability to off load caching from memory to disk, full page and fragment caching, invalidation support (either manual using cache monitor, time-out based, event driven, WAS API, or invalidation command) and replication across servers and Edge of Network caching support. DynaCache is configured through a policy-based XML file called cachespec.xml. Some factors to consider on deciding what to cache include reusability, invalidation and variations of the JSP fragments. Finally, for best performance, caching should be placed as close to the user as possible.

34 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm

2.6.16 Product Advisor

The Product Advisor creates an interactive online product catalog that provides customers with different ways of finding what they want, using shopping metaphors. WebSphere Commerce 5.4 introduced Product Advisor Administration user interface, which included four metaphors to help customer compare products, explore products and provide guidance in making appropriate selection.

Chapter 2. WebSphere Commerce V5.6 Overview 35

6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm

36 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

Chapter 3. Migration Strategy and

Planning

This chapter provides an overview of the migration process and discusses the initial stages of planning that are involved in choosing the appropriate migration approach. This chapter also includes the skills needed to complete migration. Hardware and software requirements are also defined.

This chapter is organized in the following sections:

 Migration Strategy considerations  Migration Planning  Product versions mapping  Migration approach for development environment  Migration approaches for runtime environment  Approach used for this migration

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

3.1 Migration Strategy considerations

Migration to WebSphere Commerce 5.6 is a complex undertaking. Regardless of the migration approach you choose, it will require a significant investment in time and resources. It will often be cost effective to include any pending site redesign or feature addition projects along with your migration effort. Here are some of the factors to consider.

3.1.1 Add or replace functionality

Consider adding new features and functionality that are available in WebSphere Commerce V5.6. Many of the marketing, advertising and convenience features built into the new version provide mechanisms to increase revenue and improve the customer experience.

Additionally, if you have custom implementations that provide similar functionality to those new built-in features, you may want to consider the advantages of using the “stock” implementations provided in the product.

By rebuilding your store based on one of the new “Starter Store” models you can take advantage of the new functionality rather than implementing or maintaining these features in your existing site. Often you can reduce the amount of customization you have to manage which translates directly into lower operating costs.

3.1.2 Take advantage of DynaCache

Redesigning JSPs to utilize the DynaCache page and fragment caching technology may result in measurable improvements in throughput by reducing the load on the application server and database. If you employ personalization, isolating the personalized content within JSP fragments is recommended to ensure the efficient operation of the site. Consider using the new “Starter Stores” as a model.

3.1.3 Optimization

Customers that are satisfied with their existing set of features and functionality and are interested in moving their existing implementation to the current version without any changes may still benefit from a site redesign if the load on the application server and database components can be reduced.

38 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

3.1.4 External product and user management

If you manage your persistent data externally, then there may be little benefit derived from performing a migration. Some examples may include:

 Third-party or custom catalog management systems  LDAP authentication  Order status and history retrieved on-demand from an external source

3.1.5 How does custom code impact the process?

Regardless of the approach chosen for the migration, you will have to recreate and test your custom code to account for changes in the new version.

WebSphere Commerce V5.6 introduces the concept of a “Master Catalog”. The Master Catalog must be a true tree with no loops in the structure. Items must now have parents and the parent products can only exist in a single category in the Master Catalog. If you manage your product information in an external system, consider how these new requirements will impact your integration code.

Several changes in the structure and deployment of custom code will require your attention.

 String Converters in Access Beans are no longer supported  Security Roles are now required for Enterprise Java Beans  Fine Grained Access Control methods have changed  Command parameter validation methods have changed  User registration and logon mechanisms have changed  Calculation framework customization is now policy based  Access to OrderItems through the OrderItemAccessBean has been changed

to use a new Item Bean instead

Note: For further details refer to the product information center at the following URL:

http://publib.boulder.ibm.com/infocenter/wc56help/index.jsp

3.1.6 Prepare a detailed Plan

Review with your development team the requirements and then prepare a detailed migration plan that includes the refactoring and testing effort required to implement these changes on your site. The following section cover Planning more in detail.

Chapter 3. Migration Strategy and Planning 39

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

3.2 Migration Planning

WebSphere Commerce integrates with several other software products to provide award winning e-commerce solutions. Migrating WebSphere Commerce can be a complex and challenging task given the number of products and subsystems involved. A complete migration plan must include all the necessary upgrades to application code and WebSphere Commerce servers, but that plan must also consider business requirements, while ensuring that during the migration, service cannot be negatively impacted in any significant way. That is, business must continue during the migration.

Migrating to a new version of WebSphere Commerce will have an impact on several aspects of your business. WebSphere Commerce is far more than just application code; along with the application code, there are development environments, build processes, runtime environments and other aspects that must be considered.

While planning it is important to consider:

 The customization level for the application to be migrated  Development environment (including source code management)  Testing environment  Runtime environments  Deployment processes  Database size  Integration level with third-party applications  How well the application to be migrated complies with the recommended best

practices and standards.

 Education and training

3.2.1 Skill requirements

People who will be installing and configuring WebSphere Commerce V5.6, WebSphere Commerce development environment, and those involved in the migration process should have knowledge in the following areas:

 IBM DB2 Universal Database  Understanding of relational database concepts  Ability to perform basic SQL queries  IBM HTTP Server administration skills  Understanding of TCP/IP, HTTP and SSL protocols

40 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

3.2.2 Hardware and software prerequisites

The following sections represent the minimum requirements for hardware and software involved in the installation and configuration of both production and development environments.

Important: After installing all the required software you must install WebSphere Commerce V5.6 Fixpack 1 required for migration. It can be downloaded from the following URL:

http://www-306.ibm.com/software/genservers/commerce/wcpe/support/

Production Environment

Before installing WebSphere Commerce ensure your system meets the following hardware and software prerequisites.

Hardware prerequisites

Intel™ Pentium® III 733 MHz (1 GHz or higher recommended for a production environment) IBM-compatible personal computer. This machine should not be running any other applications other than those required by WebSphere Commerce and the system must have the following:

 Memory:

– A minimum of 1 GB of RAM per processor for the first WebSphere

Commerce instance with optional WebSphere Commerce Payments instance.

– Each additional WebSphere Commerce instance with optional

WebSphere Commerce Payments instance will require an additional 512 MB of RAM per processor.

 Disk space:

– A minimum of 2 GB of free disk space on your target installation drive. – Additional 900 MB temporary disk space in the location defined by the

Windows %tmp% environment variable.

– If your machine is formatted with FAT partitioning and the partition is over

1.024 GB, you will need twice as much free disk space. If your machine is formatted with FAT partitioning and the partition is over 2.049 GB, you will need three times as much free disk space.

– The paging file size should be double the size of the RAM. For example,

512 MB RAM should have a 1024 MB paging file.

 Accessories:

Chapter 3. Migration Strategy and Planning 41

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

– A mouse or other pointing device. (optional) – A graphics-capable monitor with a color depth of at least 256 colors. – A CD-ROM drive

 Connectivity: A local area network (LAN) adapter that is supported by the

TCP/IP protocol.

Software prerequisites

Ensure that any system on which you plan to run the WebSphere Commerce V5.6 installation wizard meets the following minimum software requirements:

 Ensure that you have one of the following Microsoft Windows operating

systems installed:

– Microsoft Windows 2000, Server Edition with service pack 4 (or higher) – Microsoft Windows 2000, Advanced Server Edition with service pack 4 (or

higher) – Microsoft Windows Server 2003, Enterprise Edition – Microsoft Windows Server 2003, Standard Edition

Note: Microsoft Windows Server 2003 is not supported for the WebSphere Commerce development environment.

In addition to the required service pack levels, you should ensure that your system has the latest critical fixes installed.

For more information about service packs and critical fixes, refer to the Microsoft Windows Update site:

http://www.windowsupdate.com

 Ensure that the system is DNS enabled so that there is a host name and

domain present. Pure IP address environments are not supported by WebSphere Commerce.

 Ensure that you disable any virus scanning software active on the system.

Virus scanning software often interferes with the installation by causing problems when changing CDs during the installation.

You can re-enable the virus scanning software immediately after completing the installation.

42 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

Development Environment

Before installing WebSphere Commerce Developer, ensure your machine meets the following hardware and software prerequisites.

Hardware prerequisites

Ensure that the system on which you plan to install WebSphere Commerce Developer meets the following hardware requirements as outlined in the following table:

Table 3-1 Hardware prerequisites for development environment

Minimum hardware Recommended for

lightweight test environment

Processor Intel™ Pentium® II

processor

Memory 512 MB RAM 768 MB RAM 1 GB RAM

Hard Disk 4.0 GB hard drive

space broken down as follows:

WebSphere Studio Application Developer

2.1 GB

WebSphere Commerce toolkit 1.9 GB

Display resolution

800 x 600 display resolution

Intel Pentium III 500 MHz processor or higher

4.0 GB hard drive space broken down as follows:

WebSphere Studio Application Developer

2.1 GB

WebSphere Commerce toolkit 1.9 GB

1024 x 768 display resolution

Recommended for full test environment

Intel Pentium III 500 MHz processor or higher

4.0 GB hard drive space broken down as follows:

WebSphere Studio Application Developer

2.1 GB

WebSphere Commerce toolkit 1.9 GB

1024 x 768 display resolution

Software prerequisites

Ensure that the system on which you want to install the WebSphere Commerce Developer Environment meets the following software requirements.

 Ensure that you have one of the following Microsoft Windows operating

systems installed:

– Microsoft Windows 2000, Professional Edition with service pack 3 (or

higher) – Microsoft Windows 2000, Server Edition with service pack 3 (or higher) – Microsoft Windows 2000, Advanced Server Edition with service pack 3 (or

higher) Product versions mapping

Chapter 3. Migration Strategy and Planning 43

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

Note: Microsoft Windows Server 2003 is not supported for the WebSphere

Commerce development environment.

3.3 Product versions mapping

This section illustrates the product versions mapping we used in our scenario while migrating from WebSphere Commerce Suite V5.1 to WebSphere Commerce V5.6.

Table 3-2 illustrates the application environment, products and versions before and after the migration.

Table 3-2 Product versions mapping, production environment

Pre-Migration Post-Migration

WebSphere Commerce Suite V5.1 Start WebSphere Commerce V5.6 Professional

WebSphere Application Server V3.5.6 WebSphere Application Server V5.0.2

DB2 Universal Database V7.2.5 DB2 Universal Database V8.1.5

IBM HTTP Server 1.3.12 IBM HTTP Server 1.3.26

IBM Payment Manager 2.2.1.0 IBM WebSphere Commerce Payments is

a base (integrated) component within WebSphere Commerce V5.6

Table 3-3 illustrates the development environment, products and versions before and after the migration.

Table 3-3 Product versions mapping, development environment

Pre-migration Post-Migration

Visual Age For Java 3.5 WebSphere Studio Application Developer

V5.1.1

WebSphere Studio 3.5 WebSphere Commerce V5.6 Toolkit

3.4 Migration approach for development environment

Only one migration approach for the Development environment is supported In-place migration. You must install WebSphere Commerce V5.6 development environment on the same machine that hosts the old development environment WebSphere Commerce Studio V5.1.

44 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

After migration only the new development environment could operate on this machine and as such it is important that you have another WebSphere Commerce Studio V5.1 environment if you need to continue to develop or maintain WebSphere Commerce Suite V5.1 site.

The following is a general ordered list of tasks that are required to complete development migration:

1. Backup: Backup files, database and environment assets

2. Install/migrate software stack

3. Perform pre-migration steps

4. Import files to WebSphere Commerce V5.6 development environment

5. Generate deployment code and access beans

6. Apply changes for code migration

7. Migrate WebSphere Commerce development instance

8. Migrate database schema and unencrypted data

9. Migrate encrypted data

10.Setting up Test environment and Testing the migrated application

3.5 Migration approaches for runtime environment

This section describes three different approaches to migrating from WebSphere Commerce Suite V5.1 to WebSphere Commerce V5.6 runtime environment. A number of factors goes into deciding which approach is best suited to the system to be migrated such as: existing configuration, hardware resources available, and acceptable downtime of the production system during course of migration.

When the appropriate migration approach is chosen, the downtime of the production system can be kept to a minimum. The following sections describes options provided by the migration tools of WebSphere Commerce V5.6. Consider the approaches and decide which is best suited for your system. The approaches are as follows:

 Switch-Over migration scenario- involves creating a separated WebSphere

Commerce V5.6 environment on a remote node while keeping WebSphere Commerce Suite V5.1 environment operational.

 Co-existence migration scenario - involves migrating to WebSphere

Commerce V5.6 environment and creating a new instance while the WebSphere Commerce Suite V5.1 environment is still running on the same machine. This is possible if the WebSphere Commerce Suite V5.1 node has

Chapter 3. Migration Strategy and Planning 45

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

sufficient capacity to operate both of the instances (and software stacks, for single node install) at the same time.

Note: This approach is not supported for Microsoft Windows platforms.

 In-place migration scenario- migration is done on one system (but a test

server is highly recommended).

3.5.1 Switch-Over migration scenario

This approach is suitable when the necessary hardware to duplicate the current runtime environment is available to create a test environment where the migration takes place. Once this test environment is fully migrated and tested this test environment becomes the new production environment and the old production environment is taken off line.

With this approach the server downtime is kept to a minimum. The migration is carried out and tested on the test environment while the production servers remain running in parallel. By the time the migration and testing are complete, the database from the migrated environment will be out of sync with the production database. To reconcile the data, the production environment (still on WebSphere Commerce Suite V5.1) must be taken off-line and the database re-migrated based on the already learnt lessons. Once the migration is complete the test environment will be switched-over as the production environment.

Turning the newly migrated environment into production is a relatively simple task to do. Figure 3-1 depicts a high level layout of the Switch-Over migration scenario approach implementation. Once the test environment has been fully tested and the database reconciled, at the firewall or router level, depending on the configuration used, the NAT (Network Address Translation) rules are changed to route all the user traffic to the new runtime. The original WebSphere Commerce Suite V5.1 runtime remains active to serve as the contingency environment in the case of any problems after may occur turning the migrated environment into production.

46 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

FIREWALL

Network Address Translation (NAT)

DMZ

WebSphere

Commerce Suite V5.1

DB2 UDB V7.2

WebSphere Commerce Suite V5.1

runtime environment

Figure 3-1 Switch-Over migration scenario

WebSphere Commerce V5.6

WebSphere

Commerce

V5.6

DB2 UDB V8.1.5

runtime environment

The following is a general ordered list of tasks that are required to complete a Switch-Over migration:

 Complete migration of a development environment, as discussed in the

In-place migration section.

 Complete pre-migration steps required on production server  Backup production system  Perform pre-migration actions  Install WebSphere Commerce V5.6 components on the test server  Migrate instance  Backup database from the production server  Restore database to the test server  Run scripts to migrate database  Deploy migrated code from deployment machine  Complete required migration tasks on the test server  Test migrated instance  Take the WebSphere Commerce Suite V5.1 production server offline  Backup database from the production server  Restore database to the test server  Run scripts to migrate database

Chapter 3. Migration Strategy and Planning 47

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

 Bring WebSphere Commerce V5.6 test server online to become the new

production server

We choose and document this approach in this book, to minimize both the production downtime and the risk involved in migration. Section 3.6, “Approach used for this migration” on page 49 describes more in detail the migration path we followed.

3.5.2 Co-existence migration scenario

This approach is suitable if your WebSphere Commerce Suite V5.1 server has sufficient capacity to operate both instances WebSphere Commerce Suite V5.1 and WebSphere Commerce V5.6 environments.

It involves setting up a WebSphere Commerce V5.6 instance on WebSphere Commerce Suite V5.1 machine while the original instance is still operational and then switching the instances from old to new when the environment is ready.

Note: This migration approach is not supported on Microsoft Windows platforms. Additional information about this migration approach can be found in the product guide.

3.5.3 In-place migration scenario

In-place migration is performed on the production server. This approach typically has the longest server downtime in comparison to the other two approaches, although not necessarily the entire migration has to be done all at once. Migrating individually some components may help to minimize the production server downtime.

This approach should be considered when there are limited hardware resources and only the production server is the available system for migration (i.e. single-node implementations). This is assuming that neither high availability is required nor additional systems are available. If this is the case then this approach offers an option to migrate to WebSphere Commerce V5.6.

Having a multiple-node environment may provide the chance to consolidate functionality and nodes, freeing up some nodes should allow you to migrate them off line. The cost of doing this would be a reduction in the processing capacity but the site would still remain operational.

For this particular approach a very detailed and careful planning is required. Although supported, this approach may not be preferred if server downtime and working directly on the production server is a concern.

48 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

The following is a general ordered list of tasks that are required to complete an In-place migration:

 Take WebSphere Commerce Suite V5.1 production server offline  Backup production system  Perform pre-migration actions  Install (for coexistence) or update software levels to WebSphere Commerce

V5.6

 Perform instance migration  Migrate database  Deploy migrated code from the development machine  Complete required migration tasks on the test server  Test migrated instance  Bring WebSphere Commerce V5.6 test server online to become the new

production server

3.6 Approach used for this migration

In our approach our main goal was to minimize the downtime of the production server. To achieve this we chosen the Switch-Over migration.

Our final production environment consisted of a three nodes - a WebSphere Commerce node with a remote database node and a remote WebSphere Commerce Payments node. Initially, however, we migrated the WebSphere Commerce and database to a single node. Then, once we had successfully tested the migrated environment and we were satisfied with migration to WebSphere Commerce V5.6, we moved the database to a remote database server creating a three node environment as the original system topology.

While we were migrating the solution, the first stage of the migration, the WebSphere Commerce Suite V5.1 remained running thus we had minimal downtime. As soon as we had migrated we switched over the actual production environment from WebSphere Commerce Suite V5.1 to WebSphere Commerce V5.6, WebSphere Commerce Suite V5.1 remained operational as our backup incase of problems.

Below are described the high level tasks we performed to do a complete migration on the development and runtime. It is important to migrate the development environment first so that you have the migrated code for deployment after you have migrated the production environment:

1. Migrate development environment

2. Migrate production environment

Chapter 3. Migration Strategy and Planning 49

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

3. Deploy the code changes from the development environment to the production environment to finish the migration of the production environment

3.6.1 Detailed overview of development migration steps

Since all the following steps are performed on the development environment there should not be any downtime on the production environment.

1. Backup: Backup files, database and environment assets

2. Install/migrate software stack:

– upgrade Database level to DB2 Universal Database V8.1.5 – Install WebSphere Commerce Development environment on the same

system as your WebSphere Commerce Suite V5.1 development environment. Switch-Over migration scenario for this environment is not supported. This involves installing: WebSphere Studio Application Developer, eFixes and WebSphere Commerce V5.6 Toolkit

• Reconfigure development environment to use DB2 database by running the “setdbtype” script

– If required, install VisualAge for Java V4.0 on a separate machine, import

repository and apply fixes

3. Pre-migration actions – Setup custom constraints

• Before migrating the database you need to drop all your custom constraints

• Once you have finished migrating the database, the custom constraints you dropped need to be re-established.

– Ensure that your data meets various other premigration requirements.

This includes messages, messages types, payments, catalog, members and access control data.

4. Prepare code for importation into the WebSphere Commerce V5.6 development environment

– Export Java project from WebSphere Commerce Studio V5.1 as JAR – Export EJB projects from VisualAge for Java V3.5.3 and import into

VisualAge for Java V4.0 to migrate the EJB level from 1.0 to 1.1. Export EJB project from VisualAge for Java V4.0 as EJB 1.1 JARs.

You could also recreate EJBs in the WebSphere Commerce V5.6 development environment instead of installing VisualAge for Java V4.0 and channeling through it.

5. Import files to WebSphere Commerce V5.6 development environment

– Import EJB project into WebSphere Commerce V5.6 development

environment in WebSphereCommerceServerExtensionData

50 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

– Import Java project into WebSphere Commerce V5.6 development

environment in WebSphereCommerceServerExtensionLogic

6. Generate deployment code

– For full test environment: From the EJB JAR pop-up menu, click Generate

> Deployment and RMIC Code

– For lightweight test environment: From the EJB JAR pop-up menu, click

Generate > Test Deployment Code

7. Generate Access beans

8. Code Changes

– Fix any WSAD compilation errors

9. Migrate WebSphere Commerce Suite V5.1 development environment instance: You would need to copy the product.xml and product.dtd file to the <WCS51_home> /xml directory and update: edition, release, fixpack and path before you migrate instance

10.Migrate database schema and unencrypted data: First run the database migration script in -precheck mode to find any

inconsistencies which could be discovered with actually migrating the data. This does not, obviously, guarantee the discovery of all the issues you may

find while doing the actual database migration. As such you may want to position your first attempt at database migration to discover any additional database inconsistencies. The migration script does not interrupt when it finds any issues and this could allow the first migration run to act as a more thorough check for database consistency for migration. After the first test-run, you can restore the database and fix the problems discovered and re-run the migration scripts. You may want to tune database migration performance if it took a long time during the first run. Please refer to the behavior of migration scripts found in Appendix C, “Migration scripts” on page 255.

In order to ease the task of migrating the database second time over we created custom scripts to perform preparation and migration tasks. These scripts can be found in Appendix C, “Migration scripts” on page 255.

11.Migrate encrypted data: At this step you migrate user password data and which you could have chose to encrypted viz, credit card data.

12.Setting up Test environment and testing the migrated environment

3.6.2 Detailed overview of production environment migration

In our scenario since we performed Switch-Over migration we installed and configured WebSphere Commerce V5.6 environment on another machine, say

Chapter 3. Migration Strategy and Planning 51

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

environment #2, and restored a backup of production database on the environment #2. When we were satisfied that the migration had gone well:

– we took our environment #2 and split it into a multiple-node environment

and re-tested to ensure everything was operational – we took our production server environment, say environment #1, offline – restored the latest copy of our database from environment #1 to

environment #2, – remigrated the database – switched over environment #2 as the new production environment

Following this approach we were able to minimize our production downtime.Here are the detailed summary of steps we undertook to migrate to environment #2 before splitting it into a multiple-node environment:

1. Decide migration approach Based on the differences of migration approaches we decided to go with

Switch-Over migration to minimize the production server downtime.

2. Recreate production environment on environment #2, as discussed above.

3. Premigration actions: Same actions as on the development environment. You

may, however, discover some additional issues on this database due to additional data.

4. Bring system offline

5. Install/upgrade system

6. Migrate instance. Before executing instance migration script, ensure that:

– the product.xml and product.dtd have been copied to the appropriate

places and the content updated as required

– WebSphere Application Server security is turned off – if you are using IBM HTTP Server then you need to uncomment some

lines in the httpd.conf file

– the default ports 8000, 8002, 8004 are available for WebSphere

Commerce V5.6 tools usage, or change the defaults

– Execute instance migration script – Re-enable WebSphere Application Server security, if desired – Configure Web Server

7. Deploy your custom code

8. Performance tune your database: Sample script can be found in the bin

directory of WebSphere Commerce V5.6 install directory:

updateDB2Configuration.sh database_name log_name.

52 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm

The database tuning parameters given in this script should be considered as as the minimum required. It is highly recommended that you check the values of this script and evaluate your specific database needs, e.g. you may already be using higher values and, in such a case, you should not execute this script.

9. Migrate database schema and unencrypted data: Same actions as performed

on the development environment

10.Migrate encrypted data

11.Post migration actions: Apply changes unique to your scenario, e.g. optional

cache setup, etc.

12.Migrate WebSphere Commerce Payments

13.Migrate Staging server: We did not have staging server in our environment

14.Migrate member subsystem if you have setup with LDAP: We did not have a

separate member subsystem component in our scenario

15.Start components: You may want to run test case to ensure that the site is up

and running to your needs.

Chapter 3. Migration Strategy and Planning 53

6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm

54 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_application_used.fm

Chapter 4. Commerce Application used

during the migration

This chapter provides an overview of the application used during the WebSphere Commerce migration. An overview of the application is given along with a description of the customizations that were made to the default architecture.

The chapter is organized into the following sections:

 Commerce application  Commerce customization  Catalog  Database

6320ch_application_used.fm Draft Document for Review July 28, 2004 7:33 pm

4.1 Commerce application

CarrotInk.com is an Internet-based retailer of inkjet printer cartridges and supplies. CarrotInk.com sells after-market and OEM brand printer supplies. The company supplies as many as 400 individual cartridge types, supporting thousands of different printer models. Before migrating to WebSphere Commerce Suite V5.1, the original site contained more than 800 static HTML pages. The pages were managed manually and the need to upgrade to a new system became prevalent.

Carrot Ink needed a solution that would provide easy maintenance of the product catalog and Web site design. Another issue was that customers could not register with the site and store billing and shipping information, therefore no order history was provided to the customer.

The solution was to migrate the existing site to WebSphere Commerce Suite V5.1. The products catalog is now easier to update, the site look and feel is easier to update, and the performance of the site is excellent. Back-end integration has been facilitated, helping Carrot Ink to process and fulfill more orders.

This section gives an overview of the application environment of the commerce application.

4.1.1 Application environment

The application environment has been implemented as two node which consists of an WebSphere Commerce Suite V5.1 application node and a database server node. These servers are mirrored servers running Raid 1. Both of these servers are behind a firewall.

Hardware Configuration

The following is a list with the hardware configuration of the application and database servers:

 Microsoft Windows 2000 Server, Service Pack 4  Pentium III, 1266 MHz  2 GB Ram  40 GB Hard Disk

Application Server Tier

The following shows the software and levels installed and configured on the application server tier:

 WebSphere Application Server V3.5.6

56 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_application_used.fm

 WebSphere Commerce Suite V5.1 Start Edition  IBM HTTP Server V1.3.12

Database Server Tier

For the database node, DB2 Universal Database V7.2.5 is installed and configured.

4.2 Commerce customization

Customization of WebSphere Commerce related to the application has been minimal. The site design was based on the InFashion sample SAR file. The application’s customization can be defined in three areas: shopping flow, overriding of default controller commands, and database tables. The following sections describe these customization in more detail.

4.2.1 Shopping flow

The default functionality of the shopping flow has been modified to provide custom account creation, dynamic shiprates, expected delivery dates, payment processing, offline orders, and checkout page flow.

Account Creation

First-time customers are allowed to create an account as they navigate through the shopping flow. After adding an item to the shopping cart and continuing with the shopping process by leaving the shopping cart, a page is displayed that allows registered users to logon or unregistered users to create an account. The registered user logs on with their email address and password and continues with the checkout process. The unregistered user fills in their email address but specifies they are a new user. They continue through the checkout process by entering their shipping and billing information. After the billing information is completed, the next page prompts the user to enter a password to be used with their account. After entering a password, the account creation process is complete and the user is forwarded to the final step of the checkout process.

The default account creation process from InFashion has also been implemented.

Dynamic Shiprates/Expected Delivery Dates

The shipping select page has been customized to implement dynamic shiprates and expected delivery dates. The dynamic shiprates are based on factors such as weight of the order and the zip code the order will be shipped. The rates are based on each shipping provider’s rate system.

Chapter 4. Commerce Application used during the migration 57

6320ch_application_used.fm Draft Document for Review July 28, 2004 7:33 pm

Expected delivery dates have also been implemented for the shipping providers. Custom code was written to calculate the number of expected days that it will take to receive the order. The factors for calculating expected delivery dates are based on the shipping policies of Carrot Ink and each shipping provider. These include exclusion of holidays, non-working days such as Saturday and Sunday, and shipping cut-off times.

Payment Processing

Payment Manger was not implemented in the original the application. The default controller command used for Payment Manager was overridden to implement custom payment processing. The application implements an authorization company for credit card verification. Once the credit card has been verified the order is processed and manually authorized. However, for the purpose of this book, the migration will include the implementation of Payment Manager for order processing.

Offline Orders

Offline orders have also been implemented. At the checkout page, customers have the option of placing the order offline. The customer is given a form to complete which becomes a mail order. Once the customer service department receives the mail order, the order is processed. No order is created in WebSphere Commerce for offline orders so no custom controller commands were written to handle the offline order process. A simple view command was created to display the offline form once the offline order has been submitted.

Billing/Shipping Selection

Another simple modification was to change the order of the select billing address and select shipping address pages. After leaving the shopping cart, the customer is directed to the select shipping address page, followed by the select billing address page.

The application model flow was based upon the InFashion sar file. Figure 4-1 illustrates the default shopping flow as packaged with the InFashion store.

58 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_application_used.fm

Home

Page

Help Page

Select CategoryHelp

Category

pages

Category

pages

New billing

address

New shipping address

Select

product

New

billing

address

New

shipping

address

Add to Shopping cart

Confirmation

Select

Product

page

Return to Shopping cart

Shopping

cart

Checkout

Choose

billing

address

Choose shipping address

Choose shipping

method

Order

summary

Order now

Order

Contact

Change

Personal

Information

Change

personal

information

Privacy

Policy

My account

page

Delete

address

Account

Log

Edit My

Address

Book

Address

Book

Add new

address

Legend

Forgot

password

Registration

page

EditDelet e

Edit

address

These pages can be accessed from any page in t he site.

Default InFasion pages

Forgot your

Password

Send

password

Password

sent

Figure 4-1 InFashion default shopping flow

Chapter 4. Commerce Application used during the migration 59

6320ch_application_used.fm Draft Document for Review July 28, 2004 7:33 pm

Figure 4-2 illustrates the customized shopping flow of the application. The changes from the InFashion flow are shown in the shaded boxes.

Home

Page

New

shipping

address

Ne w billing

address

Help

Page

New shipping address

New

billin g

address

Se lect C atego ry

Category

Product

Add to

Shopping

cart

Shopping

If no t

registered or

logged on

Create

Account

Choose

address

Shipping

If creating account

Create

password

summ ary

Order now

confirmation

Category

pages

Select

page

Retu rn to Shopping

cart

If already

logged on

Choose shipping address

billin g

method

Order

cart

Contact

Offline order

Offline

order form

Change

Personal

Info rmatio n

Change

personal

inform ation

Account

Privacy

Po licy

My account

address

Log

page

Delete

Edit My

Address

Book

Address

Book

Add new

address

Legend

Forgot

password

Registration

page

EditDelete

Edit

address

CustomizedInFashion flow

These pages can be accessed from any page in the site.

De fault InF asion page s

Forgot your

Password

Send

password

Password

sent

Figure 4-2 Customized shopping flow

4.2.2 Commands

Only a few commands from the default architecture were overridden in the application. The custom commands are used in areas of category display, dynamic shipping rates, and payment processing. Commands were also used to send customers their password and increase the functionality of the search.

60 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_application_used.fm

Table 4-1 provides a summary of the custom commands used with the application.

Table 4-1 Custom Commands

Default Command(s) Override Command Description

ApplyOrderShippingCharg esCmdImpl.java

CategoryDisplayCmdImpl CategoryDisplayCmdImpl Verifies that the category

DoPaymentVerifyCmdImpl DoPaymentCmdImpl

ApplyOrderShippingCharg esCmdImpl.java

DoPaymentMPCCmdImpl

Implements dynamic shiprates for each shipping provider. The shiprates on factors such as weight of the order and to what zipcode the order will be shipped.

referenced is valid and exists in the catalog. If category is valid, the category is displayed. This command is used primarily for customers who have bookmaked a category page but the category reference no longer exists in the database.

Bypasses Payment Manager. Authorizes credit card at point of order processing. A request is sent to authorization company and credit card is verified.

SendPasswordCmd SendPasswordCmdImpl

Chapter 4. Commerce Application used during the migration 61

N/A Accesses the database

and retrieves customer logon id and password. A message is then sent to the customer with their account information.

6320ch_application_used.fm Draft Document for Review July 28, 2004 7:33 pm

Default Command(s) Override Command Description

TXSearchSampleCmd TXSearchSampleCmdImpl

4.2.3 Database tables

Custom tables were added to increase functionality. Tables were added to implement dynamic shiprates. Other tables were added to store potential fraudulent payment transactions.Table 4-2 provides a summary of custom tables that were created for use with the application.

Table 4-2 Custom Tables

Table Description

RURALZIPCODES SHIPRATE SURCHARGE ZIPCODE ZONE

N/A Sample commands

provided by IBM for use with the DB2 Text Extender. The controller command generates a SQL statement that is then used to query the database to return search results.

Implements dynamic shiprates for FedEx, UPS, USPS. Based on factors such as zipcode, shipping zone, and order weight, the application will deliver real time ship rates to the customer.

XBLOCKIPS XPOTIPS

Non-Commerce related tables. Part of external application that records potential fraudulent payment transactions.

4.3 Catalog

The product catalog includes all the items sold on Carrotink.com. The catalog contains the hierarchy for categories with the items being associated with the bottom level category. The top categories are the printer brand. The subcategories are the printer models. Some items have a 1:1 relation with their parent category while other items have a 1:M (1 to many) relationship. This 1:M relationship is due to the fact that one ink jet cartridge can work with different printers.

62 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_application_used.fm

4.4 Database

The database architecture has been modified slightly from the default. No customizations have been made to the WebSphere Commerce schema. However, as mentioned earlier, some tables were added for increasing functionality. Tables were added to implement dynamic ship rates. These tables store data related to shipping zones and ship-to zip codes. Also, an external application was written to record possible fraudulent payment transactions. Two tables were created to store this information. These custom tables are mentioned in Table 4-2.

Chapter 4. Commerce Application used during the migration 63

6320ch_application_used.fm Draft Document for Review July 28, 2004 7:33 pm

64 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320p03.fm

Part 2

Part 2 Development

environment

6320p03.fm Draft Document for Review July 28, 2004 7:33 pm

66 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

Chapter 5. Installing WebSphere

Commerce Development Environment

This chapter details the steps that should be taken to install the development environment for WebSphere Commerce V5.6. Once complete, you will have a fully working WebSphere Commerce development environment, using DB2 Universal Database V8.1 as the database. All steps in this chapter must be completed before attempting the development environment migration in the next chapter.

This chapter is organized in the following sections:

 Development environment overview  Pre-installation requirements  Installing WebSphere Studio Application Developer  Installing WebSphere Commerce V5.6 Toolkit  Installing DB2 Universal Database V8.1  Configuring the development environment for DB2  Installing VisualAge for Java V4.0

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

5.1 Development environment overview

This section describes how we installed the WebSphere Commerce Developer software package. The development environment consists of the following products:

 WebSphere Studio Application Developer V5.1.1  WebSphere Commerce V5.6 Toolkit  DB2 Universal Database V8.1.5

In the WebSphere Commerce V5.6 Toolkit, two test environments are available, a lightweight environment and a full environment. During the installation documented in this chapter, both environments will be installed and configured for use with DB2 Universal Database V8.1.5.

Unlike the VisualAge for Java development environment for WebSphere Commerce Suite V5.1, a WebSphere Commerce run-time environment is not required. The servers configured in WebSphere Studio Application Developer are all that are required.

Important: For the purposes of migrating from the WebSphere Commerce Suite V5.1 development environment it is mandatory that you install WebSphere Studio Application Developer V5.1.1 on the same system as VisualAge for Java V3.5.3.

After installation of WebSphere Studio Application Developer V5.1.1 and WebSphere Commerce V5.6 Toolkit, your existing VisualAge for Java will still be intact. However, due to the fact that you must upgrade your database to DB2 Universal Database V8.1, you may no longer be able to use the WebSphere Test Environment in VisualAge for Java.

Important: After installing all the required software you must install WebSphere Commerce V5.6 Fixpack 1. It can be downloaded from the following URL:

http://www-306.ibm.com/software/genservers/commerce/wcpe/support/

5.2 Pre-installation requirements

Before installing WebSphere Studio Application Developer V5.1.1 and WebSphere Commerce V5.6 Toolkit, ensure that your machine meets the hardware and software prerequisites found in 3.2.2, “Hardware and software prerequisites” on page 41.

68 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

The steps detailed in this chapter are provided under the assumption that you have a fully working WebSphere Commerce Suite V5.1 test environment in VisualAge for Java V3.5.3. It is also assumed that you are using DB2 Universal Database V7.2.5 with a local development database.

5.2.1 VisualAge for Java V4.0 prerequisites

In order to install and configure VisualAge for Java V4.0 for EJB migration, you will need the following components:

 VisualAge for Java V4.0 installation CD  The following fixes from the WebSphere Commerce Studio V5.4 installation

CD:

– EJB-1.1-DeployedTool.zip – ivjfix35.zip – PQ50159.jar – readonly.zip

Note: You will need to contact IBM support to obtain these files.

 The WebSphere Commerce Suite V5.1 repository file, shipped on the

WebSphere Commerce Studio V5.1 installation CD.

5.3 Installing WebSphere Studio Application Developer

This section details the steps that must be taken to install WebSphere Studio Application Developer V5.1.1. Once this section is completed, you will have a WebSphere Application Server test environment configured at the correct fixpack level required to install the WebSphere Commerce V5.6 Toolkit.

Note: DB2 (or Oracle) is required when migrating from a previous version of the WebSphere Commerce development environment. If you are starting development from scratch, you should follow the recommendations in WebSphere Commerce Developer V5.6 Installation Guide for Windows.

5.3.1 Pre-installation steps

The following list describes the steps that are needed to be carried out prior to the installation of WebSphere Studio Application Developer V5.1.1:

Chapter 5. Installing WebSphere Commerce Development Environment 69

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

 Ensure that the user ID that you are using does not contain double-byte

characters.

 Ensure that the environment variable TEMP or TMP is pointing to a valid

temporary directory

 Ensure that the drive containing the temporary directory (mentioned above)

has more than 2GB available.

5.3.2 Installing WebSphere Studio Application Developer V5.1.1

The steps below describe how to install WebSphere Studio Application Developer V5.1.1.

Attention: Remember that you must install WebSphere Studio Application Developer V5.1.1 on the same system as your existing VisualAge for Java environment for WebSphere Commerce Suite V5.1.

1. Run launchpad.exe from the root of the first installation CD

2. On the WebSphere Studio Installation Launchpad window click the button next to Install IBM WebSphere Studio Application Developer.

3. Wait for the WebSphere Studio Installation Welcome page to open, then click Next to continue the installation. The welcome page may take several minutes to appear.

4. Read the license agreement, select I accept the terms in the license agreement and click Next.

5. Enter the desired target directory in the Directory Name field and click Next. We recommend that you do not install into a directory containing spaces in the name.

In our example, we entered the following directory:

D:\WebSphere\WSAD511

Important: Do not install into a directory with a name that contains double-byte characters or special characters such as a dollar sign. Doing so may cause undesirable results such as class path problems in the WebSphere test environment.

70 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

Note: The installation program checks to see if WebSphere Studio Application Developer V5.1 is installed. Since this cannot coexist with WebSphere Studio Application Developer V5.1.1, if WebSphere Studio Application Developer V5.1 is detected, a message appears asking if you want the installation program to uninstall it. WebSphere Studio Application Developer V5.1.1 re-uses the same install directory as specified for WebSphere Studio Application Developer V5.1, to preserve links to third-party plug-ins.

6. In the features window you can select the WebSphere Studio Application Developer V5.1.1 features that you would like to install. Select WebSphere Application Server V5.0.2 Test Environment and deselect any other test environment and click Next.

Note: If you are upgrading from WebSphere Studio Application Developer V5.1, all features that were previously installed will be pre-selected as well.

7. Click Next to install WebSphere Studio Application Developer V5.1.1. During the installation you will be prompted to insert WebSphere Studio

Application Developer V5.1.1 CD 2. Insert the CD and click OK to continue. Refer to WebSphere Commerce Developer V5.6 Installation Guide for

Windows if you encounter warnings or errors during the installation.

8. When WebSphere Studio Application Developer V5.1.1 is installed, click Finish to close the installation window.

9. Click the button next to Exit in the WebSphere Studio Installation

Launchpad window to close it.

5.3.3 Apply fixes to the test environment

In order to prepare the test environment for the installation of the WebSphere Commerce V5.6 Toolkit, several fixes must be installed to upgrade the level of the WebSphere Application Server test environment to the same level as is required by the WebSphere Commerce V5.6 run-time environment. These fixes are provided in the WebSphere Application Server fixpack CD.

Check that the following has been completed before applying fixes:  WebSphere Studio Application Developer V5.1.1 with WebSphere Application

Server V5.0.2 Test Environment is installed on the machine.

 Any applications running on your machine have been stopped.

The fixpack installation consist of three steps:

Chapter 5. Installing WebSphere Commerce Development Environment 71

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

1. Prepare for fixpack installation

2. Install WebSphere Application Server V5.0.2 cumulative fix 3

3. Install interim fixes

The installation procedure is described in the following sections.

Prepare for fixpack installation

Before the fixpack can be applied, the WebSphere Test Environment inside WebSphere Studio Application Developer V5.1.1 must be prepared. The following list describes the necessary steps to configure the test environment for the fixpack installation.

1. Insert the WebSphere Application Server Fixes CD from your WebSphere Commerce package provided with WebSphere Commerce Developer into the CD-ROM drive.

2. From a Windows command prompt, change to the directory CD-ROM drive:\WSAD and issue the following command on a single line:

<WSAD_home>\runtimes\base_v5\java\bin\java -jar PrePatcher.jar <WSAD_home>

3. The pre-patcher will ask you to confirm the location of your WebSphere Studio Application Developer V5.1.1 installation directory. Validate the location and enter Y followed by Enter to continue.

The last message from the pre-patcher should be:

All done... You should be able to apply WebSphere v5.0.2 Cumulative fix to your WTE.

Now you can continue with the next step of actually applying the fixes.

Install WebSphere Application Server V5.0.2 cumulative fix 3

Apply WebSphere Application Server Version V5.0.2 Cumulative Fix 3 to your WebSphere Studio Application Developer installation as follows:

1. Copy the updateInstaller directory from the root of the WebSphere Application Server Fixes CD to a temporary location on the hard drive.

2. From a Windows command prompt, do the following: a. Change to the updateInstaller directory that you just created on your

hard drive.

b. Issue the following commands:

set JAVA_HOME=<WSAD_home>\runtimes\base_v5\java updateWizard

72 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

This starts the update installation wizard. You can close the command prompt at this point.

3. The language prompt will appear. Select the desired language for the Update Wizard and click OK.

4. The Welcome page appears. Click Next.

5. When prompted to select the product to update, check Specify product information and enter the following path in the Installation directory field:

<WSAD_home>\runtimes\base_v5

Click Next.

Note: The Wizard will show the following message on the page where you

specify the location:

WebSphere Application Server Family product - Not found

This just means that the wizard could not find an installation of WebSphere Application Server V5.0.2 and can safely be ignored.

6. Select Install fixpacks and click Next.

7. In the fixpack directory field, enter the following path and click Next.

CD-ROM drive:\BASE\fixpack

The Update Wizard will determine which fixes are applicable for the selected path. This may take several minutes.

8. A list of available fixpacks will be shown. Ensure that was502f_cf3_win is selected and click Next.

9. The Update Wizard will warn that the following fixes will be uninstalled:

– PQ78374 – PQ78419

Click Next. The Update Wizard will begin applying the selected fixpack.

When the installation has completed, click Run Wizard Again. This will leave the update installation wizard open to apply the required interim fixes in the next step.

Chapter 5. Installing WebSphere Commerce Development Environment 73

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

Install interim fixes

Apply the WebSphere Application Server interim fixes to your WebSphere Studio Application Developer V5.1.1 installation as follows. The update installation wizard should still be open from the previous step:

1. From the Update Installation Wizard, select Install fixes and click Next.

Note: The Install fixes is the third option on the window, easily confused with the first option, Install fixpacks.

2. In the Fix directory field, enter the following path and click Next:

CD-ROM drive:\WSAD\fixes

3. From the list of available fixes, check PQ82074, leaving all other fixes unchecked, and click Next.

Important: Ensure that only PQ82074 is checked. If you apply more than one fix at a time, the installation will fail.

4. The installation summary will show. Click Next to start the fix installation.

5. When the installation has completed, click Run Wizard Again.

6. Repeat steps 1 to 4 to install PQ81989_win.

7. When the installation has completed, click Run Wizard Again.

8. Select Install fixes and click Next.

9. In the Fix directory field, enter the following path and click Next:

CD-ROM drive:\BASE\fixes

10.From the list of available fixes, check PQ85933_Fix, leaving all other fixes unchecked, and click Next.

11.The installation summary will show. Click Next to start the fix installation.

12.When the installation has completed, click Run Wizard Again.

13.Repeat steps 8 to 11 for the each of the following fixes, one at a time, in the order they are listed:

– PQ83918 – PQ85469

74 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

Important: Fixes must be installed in the order they are listed and one at a time because each fix often replace files from the one before it.

If you do not apply these fixes in the correct order, your test environment may not work properly.

14.After the last fix, PQ85469, has been applied, you can click Finish to close the Update Installation Wizard.

5.4 Installing WebSphere Commerce V5.6 Toolkit

Assuming you have completed the installation steps in the previous sections of this chapter, you are ready to install the WebSphere Commerce V5.6 Toolkit. Installing the Toolkit will create the WebSphere Commerce components in WebSphere Studio Application Developer and create the necessary server configuration for the test environment.

As mentioned in 5.1, “Development environment overview” on page 68 the WebSphere Commerce development environment is available with both a lightweight and full test environment. By default, the lightweight test environment is configured to use Cloudscape as the test database.

At a later stage, the full test environment will be installed and both test environments will be configured to use DB2 Universal Database, as this is a requirement for migrating the development instance and database. This is documented in 5.6, “Configuring the development environment for DB2” on page 85.

After finished installation and migration, you can switch between the two environments as you development needs require.

Before continuing with the installation of the WebSphere Commerce V5.6 Toolkit you must ensure that the following have been completed:

 WebSphere Studio Application Developer V5.1.1 with WebSphere Application

Server V5.0.2 Test Environment is installed on the machine.

 WebSphere Application Server V5.0.2 cumulative fix 3 and interim fixes have

been applied to the test environment as described in 5.3.3, “Apply fixes to the test environment” on page 71.

 No applications are running on your system.

Chapter 5. Installing WebSphere Commerce Development Environment 75

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

5.4.1 Installing WebSphere Commerce V5.6 Toolkit

The steps below describe how to install WebSphere Commerce V5.6 Toolkit.

1. Insert the WebSphere Commerce V5.6 Toolkit CD in the CD-ROM of the WebSphere Studio Application Developer V5.1.1 machine. The WebSphere Commerce V5.6 Toolkit installation wizard should start automatically. If the installation does not start automatically, run setup.exe on the root of the WebSphere Commerce V5.6 Toolkit CD.

2. The language prompt will appear. Select your desired language for the installation wizard and click OK. For our example, we selected English.

3. The Welcome page will appear. Click Next.

4. Read the license agreement, select I accept the terms in the license agreement and click Next.

5. The destination path page will appear. Enter the directory in which you wish to install the WebSphere Commerce V5.6 Toolkit and click Next.

For our example, we entered the following path:

D:\WebSphere\WCToolkitPro56

Important: Do not enter a path containing spaces, double byte characters or other special characters.

6. The installation summary wind will appear. Ensure that you have sufficient hard disk space and click Next to start the installation.

7. Click Finish when the installation is complete, to close the installation wizard.

Installation verification

To validate that the installation of the WebSphere Commerce V5.6 Toolkit was successful, do the following:

1. Examine the contents of <wctoolkit_home>\logs\setup.log. If setup.log is empty or has errors, you can retry the configuration steps by running <wctoolkit_home>\bin\setup.bat from the command line.

2. Check that the install was able to properly detect WebSphere Studio Application Developer V5.1.1 on your system by ensuring that the following file sets the WSAD_HOME environment variable to <WSAD_home> correctly:

<wctoolkit_home>\bin\setenv.bat

The file should look like the sample file shown in Example 5-1 with your environment specific values substituted.

Example 5-1 Sample setenv.bat file for WebSphere Commerce V5.6 Toolkit

76 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

set WSAD_HOME=D:\WebSphere\WSAD511

call setshortname RUNTIME_JARS ..\AppServer\classes call setshortname RUNTIME_CLASSES ..\AppServer\classes call setshortname J2EE_JAR ..\AppServer\lib\j2ee.jar call setshortname XERCES_JAR ..\AppServer\lib\xerces.jar call setshortname XALAN_JAR ..\AppServer\lib\xalan.jar call setshortname XMLPARSERAPIS_JAR ..\AppServer\lib\j2ee.jar call setshortname JAVA_HOME ..\AppServer\java call setshortname PROPERTIES ..\properties set path=%JAVA_HOME%\bin;%PATH% call setshortname WSAD_HOME “%WSAD_HOME%“ call setshortname WCTOOLKIT “%~d0%~p0..“ set WORKSPACE_DIR=%WCTOOLKIT%\workspace set WAS_HOME=%WSAD_HOME%\runtimes\base_v5 call setshortname WCS_HOME .. call setshortname WCLOGDIR ..\logs call setshortname WCTEMPDIR ..\temp

You now have a fully functioning WebSphere Commerce V5.6 development environment installed. The development environment is set up to use the lightweight WebSphere Commerce test environment with Cloudscape as database system.

In 5.6, “Configuring the development environment for DB2” on page 85, the test environment will be configured to use DB2 Universal Database, but first we must install DB2 Universal Database V8.1.

5.5 Installing DB2 Universal Database V8.1

DB2 Universal Database V8.1 must be installed in your new development environment in order to complete a successful migration. This is because the full WebSphere Commerce test environment is required. This section details the installation steps.

Note: This guide assumes that your WebSphere Commerce Suite V5.1 development environment uses a local installation of DB2. That is, DB2 Universal Database V7.2.5 is installed on the same machine as VisualAge for Java V3.5.3.

5.5.1 Backup development databases

We recommend that you backup all databases in the development environment that cannot be recreated before you install DB2 Universal Database V8.1, as

Chapter 5. Installing WebSphere Commerce Development Environment 77

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

databases are not interchangeable between these DB2 Universal Database versions.

In this case you will have a DB2 Universal Database V7.2.5 level of your databases, should you later need to change back to DB2 Universal Database V7.2.5.

In our example, we created a backup of the database MALL, as the remaining databases can be recreated if necessary.

5.5.2 Installation requirements

Before continuing, you should ensure that you have a working development environment that is using Cloudscape, as installed in 5.3, “Installing WebSphere Studio Application Developer” on page 69 and 5.4, “Installing WebSphere Commerce V5.6 Toolkit” on page 75.

As you already have a database on your development system in DB2 Universal Database V7.2.5, you must run the DB2CKMIG tool provided on the DB2 Universal Database V8.1 installation disk before installing DB2 Universal Database V8.1. This tool will check your existing databases for conditions that would prevent a successful migration.

To run the DB2CKMIG tool, complete the following steps:

1. Insert the DB2 Universal Database V8.1.5 CD, supplied with WebSphere Commerce V5.6 in your CD-ROM drive.

Important: WebSphere Commerce V5.6 is shipped with a special version of DB2 Universal Database V8.1, refreshed to fixpack 5 level. Do not confuse the DB2 Universal Database V8.1.5 CD with a standard DB2 Universal Database V8.1 installation CD.

2. In a Windows command prompt, navigate to the following directory on the DB2 Universal Database V8.1.5 CD:

<CD_Drive>db2\Windows\utilities

3. Run the db2ckmig tool as follows for each database on you system:

db2ckmig database_name -L logfile -U username -P password

where:

– database_name is the name of your development database – logfile is a path and filename for the log to be output to –username is the user name for your development database

78 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

– password is the password for this user

In our example, we used the following:

db2ckmig mall -L D:\db2miglog.txt -U dbusr01 -P dbusr01pwd

If there are no potential problems, you will see the following output in the command line.

db2ckmig was successful. Database(s) can be migrated.

4. Inspect the content of the log file, specified as a parameter to db2ckmig, to ensure that no error conditions are logged.

If the tool reports any potential problems, you must resolve these before continuing with the remainder of this chapter.

5.5.3 Preparing a Windows user for DB2

In order to simplify the process of migrating the development database, it is advisable that you ensure that an administrative user, with the same user name and password as is used for DB2 on your VisualAge for Java V3.5.3, exists in Windows.

Also, if your WebSphere Commerce database was created under a different schema, you should create a user for that schema name.

Attention: While it is possible to use a different user name and password for the DB2 admin user and the WebSphere Commerce database owner, it is advisable that you use the same user for both in the development environment. This may help avoid configuration problems later on.

Create a Windows user with the appropriate access rights by completing the following steps:

1. Click Start -> Settings -> Control Panel.

2. Double-click Administrative Tools.

3. Double-click Computer Management.

4. In the tree on left of the new window, expand Local Users and Groups and click Users.

5. Select Action -> New User...

6. Enter the user name used for your original development database. In our example, we used dbusr01.

7. Enter the corresponding password in the Password and Confirm Password fields. In our example, we used dbusr01pwd.

Chapter 5. Installing WebSphere Commerce Development Environment 79

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

8. Deselect User must change password at next logon.

9. Select User cannot change password and Password never expires.

10.Click Create.

11.Click Close.

Before this new user can be used by DB2, it must be given administrative rights. To do this, complete the following steps:

1. In the Computer Management window, right-click on the user you just created and select Properties from the menu.

2. Click the Member Of tab and click the Add... button.

3. Select Administrators from the list of user groups and click Add.

4. Click OK to add the user to the group and then click OK to close the user properties window.

5. Close the Computer Management window.

5.5.4 Installing DB2 Universal Database V8.1

Before installing DB2 Universal Database V8.1, you must ensure that the current installation is not in use and all DB2 services are stopped. To ensure this is the case, complete the following steps:

Note: At the time of writing, we had problems upgrading from DB2 Universal Database V7.2.5 to DB2 Universal Database V8.1.5 directly, using the CD supplied with WebSphere Commerce V5.6.

The following instructions documents how to install DB2 Universal Database V8.1.5 by installing the base product DB2 Universal Database V8.1 and then applying fixpack 5.

An alternative is to uninstall the DB2 Universal Database V7.2.5 installation and then install DB2 Universal Database V8.1.5.

1. Restart your computer.

2. Ensure that no local databases are in use. To check for connections, execute the following command in a DB2 command line window:

db2 list applications

The output from this command should be as follows:

SQL1611W No data was returned by Database System Monitor. SQLSTATE=00000

80 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm

If the response is a list of database agent connections, you must ensure that each of the corresponding processes are ended before continuing.

Tip: A typical installation of DB2 Universal Database V7.2.5 will include the DB2 Warehouse components. These will be registered as Windows services, to be started automatically. If the DB2 Warehouse services are running, the list applications command will return lines reporting that the database named DWCTRLDB is in use by the applications named IWH2LOG.EXE and IWH2SERV.EXE.

To eliminate these connections, stop the following services from the Services console, or by using the command line net stop command:

Warehouse logger Warehouse server

3. Run the following command once you ensured that no databases are in:

db2stop

4. Ensure that you have no DB2 applications running, including DB2 Command Windows.

5. Open the Services console and stop all DB2 services, that is all services starting with the word DB2.

To install DB2 Universal Database V8.1, complete the following steps:

1. Run setup.exe from the root of the DB2 Universal Database V8.1 installation CD.

2. When the Launchpad windows opens, click Install Products.

3. Click Next to start the installation wizard. Several warning messages will appear. In our example, we saw the following

warnings:

– An earlier version of DB2 Universal Database is already installed as

shown in Figure 5-1. We clicked Yes to continue.

Figure 5-1 Warning that an earlier version of DB2 Universal Database is installed

Chapter 5. Installing WebSphere Commerce Development Environment 81

6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm

– Information that the Query Patroller Client is not available in the new

version of DB2 Universal Database as shown in Figure 5-2. We clicked Yes to continue.

Figure 5-2 Warning that a feature is not available in DB2 Universal Database V8.1

– Information that we should run the db2chmig tool against our databases

before upgrading, as shown in Figure 5-3. We clicked OK to continue, as we have already done this in 5.5.2, “Installation requirements” on page 78.

Figure 5-3 Warning that db2chmig should be run before installation

4. On the welcome screen, click Next.

5. Red the license agreement, select I accept the terms in the license agreement and click Next.

6. Select the Typical option, uncheck Data warehousing and Satellite administration capability, and click Next.

7. A warning about use of APPC will appear. This does not apply to us, so click click OK to continue.

8. Ensure that Install DB2 Enterprise Server Edition on this computer is checked, that Save your settings in a response file is unchecked, and click Next.

9. The path where DB2 Universal Database V7.2.5 is installed will be preselected. Ensure that you have sufficient disk space and click Next to continue.

82 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

IBM SG24-6320-00 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Front cover

Contents

Notices

Trademarks

Preface

The team that wrote this redbook

Become a published author

Comments welcome

Chapter 1. Introduction

1.1 Overview

1.2 Structure of the book

2.1 Product overview

2.2 WebSphere Commerce software components

2.2.1 Web server

2.2.2 WebSphere Application Server

2.2.3 Database Server

2.2.4 WebSphere Commerce Server

2.2.5 WebSphere Commerce Payments Server

2.2.6 Enablement software

2.3 WebSphere Commerce Server subsystems

2.3.1 Member subsystem

2.3.2 Catalog subsystem

2.3.3 Trading subsystem

2.3.4 Order subsystem

2.3.5 Merchandising subsystem

2.3.6 Marketing subsystem

2.3.7 Inventory subsystem

2.3.8 Messaging subsystem

2.4 WebSphere Commerce Tools

2.5 WebSphere Commerce Business models

2.5.1 Direct Sales

2.5.2 Value Chain

2.5.3 Hosting Ex-Sites

2.6 What’s new in WebSphere Commerce V5.6

2.6.1 WebSphere Commerce Development Environment

2.6.2 WebSphere Commerce Payments

2.6.3 Configuration Manager

2.6.4 Loader Package

2.6.5 Password Manager

2.6.6 Adaptor for CrossWorld

2.6.7 Catalog and product management

2.6.8 Business Models

2.6.9 Access Control

2.6.10 Collaboration

2.6.11 Campaigns and Promotions

2.6.12 Order and inventory Management

2.6.13 Analytics

2.6.14 Security

2.6.15 Caching

2.6.16 Product Advisor

3.1 Migration Strategy considerations

3.1.1 Add or replace functionality

3.1.2 Take advantage of DynaCache

3.1.3 Optimization

3.1.4 External product and user management

3.1.5 How does custom code impact the process?

3.1.6 Prepare a detailed Plan

3.2 Migration Planning

3.2.1 Skill requirements

3.2.2 Hardware and software prerequisites

3.3 Product versions mapping

3.4 Migration approach for development environment

3.5 Migration approaches for runtime environment

3.5.1 Switch-Over migration scenario

3.5.2 Co-existence migration scenario

3.5.3 In-place migration scenario

3.6 Approach used for this migration

3.6.1 Detailed overview of development migration steps

3.6.2 Detailed overview of production environment migration

4.1 Commerce application

4.1.1 Application environment

4.2 Commerce customization

4.2.1 Shopping flow

4.2.2 Commands

4.2.3 Database tables

4.3 Catalog