User manual

ManualsBrandsIBM ManualsSoftwareMarine Radio SG24-6320-00

ibm.com/redbooks

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

Hernan Cunico

Andrew Hays

Steve Insley

Khurram Wyne

Nicolai Nielsen

Sanjeev Sharma

Sanjay Shah

Drake Philbrook

Migration Strategy and Planning

Production and Development

Environments

Step-by-Step

Instructions

Front cover

Summary of content (306 pages)

PAGE 1
Front cover Draft Document for Review July 28, 2004 7:33 pm SG24-6320-00 Keeping Commerce ce Applications Updated dated WebSphere Commerce 5.1 to 5.6 Migration Guide Migration Strategy and Planning Production and Development Environments Step-by-Step Instructions Hernan Cunico Andrew Hays Steve Insley Khurram Wyne Nicolai Nielsen Sanjeev Sharma Sanjay Shah Drake Philbrook ibm.
PAGE 2
PAGE 3
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.
PAGE 4
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. © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S.
PAGE 5
Draft Document for Review July 28, 2004 7:33 pm 6320TOC.fm Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
320TOC.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. . . . . . . . . . . . . .
PAGE 7
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
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 . . . . . . . .
PAGE 10
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.
PAGE 11
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 . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
6320TOC.fm x Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 13
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.
PAGE 14
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® eServer™ ibm.
PAGE 15
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.
PAGE 16
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.
PAGE 17
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.
PAGE 18
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.
PAGE 20
6320p01.fm 2 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 21
Draft Document for Review July 28, 2004 7:33 pm 6320ch_intro.fm 1 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. © Copyright IBM Corp. 2004. All rights reserved.
PAGE 22
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.
PAGE 23
6320ch_intro.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 24
6320ch_intro.fm 6 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 25
Draft Document for Review July 28, 2004 7:33 pm 6320ch_sum_of_changes.fm 2 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.
PAGE 26
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.
PAGE 27
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.
PAGE 28
6320ch_sum_of_changes.
PAGE 29
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 30
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://: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.
PAGE 31
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 32
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).
PAGE 33
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 34
6320ch_sum_of_changes.fm 1 Draft Document for Review July 28, 2004 7:33 pm WebSphere Commerce Customer WebSphere Commerce instance database Customer Service Representative MQ Applications 2 MQ 3a 3 3b LDAP 4 JNDI LDAP API LDAP Directory Management Tool 3c Mass Loader Directory Applications Legacy DB LDIF 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.
PAGE 35
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 4. Using WebSphere Commerce Loader Package (MassLoad) WebSphere Commerce Loader Package is used for mass database updates. The MassLoad tool can be used for mass registration of users. This method is especially useful in the migration from previous versions, in database management, and in member registration exchange across WebSphere Commerce systems.
PAGE 36
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm An access control policy authorizes a group of users to perform particular actions on a group of WebSphere Commerce resources. Unless authorized through one or more access control policies, users have no access to any functions. Access control policies grant authorization to a specific group of users to perform particular actions on resources in a specified resource group.
PAGE 37
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm non-secure session cookies, which are used to manage the session data, and secure authentication cookies used to manage authentication data. Single sign-on WebSphere Commerce supports single sign-on when configured with an LDAP directory. 2.3.2 Catalog subsystem The Catalog subsystem provides online catalog navigation, merchandising features, interest lists, and search capabilities.
PAGE 38
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.
PAGE 39
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 40
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.
PAGE 41
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.
PAGE 42
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.
PAGE 43
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 44
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.
PAGE 45
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 46
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.
PAGE 47
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 48
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.
PAGE 49
6320ch_sum_of_changes.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 50
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.
PAGE 51
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.
PAGE 52
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.
PAGE 53
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.
PAGE 54
6320ch_sum_of_changes.fm 36 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 55
Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm 3 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.
PAGE 56
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.
PAGE 57
6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 58
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.
PAGE 59
6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 60
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.
PAGE 61
6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm Development Environment Before installing WebSphere Commerce Developer, ensure your machine meets the following hardware and software prerequisites.
PAGE 62
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.
PAGE 63
20ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 64
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.
PAGE 65
6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm FIREWALL Network Address Translation (NAT) DMZ WebSphere Commerce Suite V5.1 WebSphere Commerce V5.6 DB2 UDB V7.2 DB2 UDB V8.1.5 WebSphere Commerce Suite V5.1 runtime environment WebSphere Commerce V5.
PAGE 66
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.
PAGE 67
6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 68
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.
PAGE 69
6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm – 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.
PAGE 70
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.
PAGE 71
6320ch_planning.fm Draft Document for Review July 28, 2004 7:33 pm 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.
PAGE 72
6320ch_planning.fm 54 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 73
Draft Document for Review July 28, 2004 7:33 pm 6320ch_application_used.fm 4 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.
PAGE 74
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.
PAGE 75
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.
PAGE 76
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.
PAGE 77
6320ch_application_used.
PAGE 78
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.
PAGE 79
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 ApplyOrderShippingCharg esCmdImpl.java 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.
PAGE 80
6320ch_application_used.fm Draft Document for Review July 28, 2004 7:33 pm Default Command(s) Override Command Description TXSearchSampleCmd TXSearchSampleCmdImpl 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. 4.2.3 Database tables Custom tables were added to increase functionality. Tables were added to implement dynamic shiprates.
PAGE 81
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.
PAGE 82
6320ch_application_used.fm 64 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 84
6320p03.fm 66 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 85
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm 5 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.
PAGE 86
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.
PAGE 87
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.
PAGE 88
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.
PAGE 89
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.
PAGE 90
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.
PAGE 91
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: \runtimes\base_v5 Click Next.
PAGE 92
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.
PAGE 93
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.
PAGE 94
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.
PAGE 95
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 ..
PAGE 96
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.
PAGE 97
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.
PAGE 98
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.
PAGE 99
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.
PAGE 100
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.
PAGE 101
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm 10.In the User Information frame, enter the user name and password of the user that you created in 5.5.3, “Preparing a Windows user for DB2” on page 79. Ensure that Use the same user name and password for the remaining DB2 services is checked and click Next. 11.In the Administration contact list page, select Local - Create a contact list on this system, ensure that Enable notification is unchecked and click Next.
PAGE 102
6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm Important: You will need at least 500MB of free space on the drive where the TEMP environment variable points to. This is typically the Windows installation drive. 2. When the Launchpad window opens, click Install Product. Note: The Launchpad window is identical to the original DB2 Universal Database V8.1 Launchpad window, although it is in fact the fixpack 5 Launchpad window. 3. Click Next to start the installation.
PAGE 103
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm 5.5.6 Migrate databases to DB2 Universal Database V8.1 level At this point, the databases in the system are all DB2 Universal Database V7.2.5 databases, not compatible with DB2 Universal Database V8.1. In order to use the databases, you must migrate these. To migrate the databases, perform the following steps: 1. Log on to the system with a Windows administrator 2.
PAGE 104
6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm Note: After completing this chapter, the development database will still be using the schema for WebSphere Commerce Suite V5.1. The migration steps in the next chapter will migrate the database to the new schema for WebSphere Commerce V5.6. Complete the following steps: 1. Ensure that WebSphere Studio Application Developer V5.1.1 is not running. 2.
PAGE 105
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm 5.7 Installing VisualAge for Java V4.0 If you have developed custom EJBs for your WebSphere Commerce Suite V5.1 store and wish to migrate them to your new development environment, you will need to install VisualAge for Java V4.0. Attention: Please read the opening paragraphs of 7.5, “Migrating custom EJBs” on page 118 to determine if you wish to do this step.
PAGE 106
6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm Note: VisualAge for Java V3.5.3 and VisualAge for Java V4.0 cannot coexist on the same system. As such, you must install VisualAge for Java V4.0 on a separate system, remote from your VisualAge for Java V3.5.3 installation. Alternatively, if your access to additional systems is limited, you could perform the steps in the following order: 1. Follow the instructions in 6.2.4, “Export code from VisualAge for Java V3.5.
PAGE 107
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm 10.The repository location window appears. Ensure that Local is selected and click Next. 11.The Ready to install program confirmation window appears. Click Install. 12.When the installation is complete, a confirmation window will appear. Click Finish to close the window. At this point, VisualAge for Java V4.0 is installed with a default workspace. In the next section, we will import the WebSphere Commerce Suite V5.
PAGE 108
6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm Install the DeployTool fix The DeployTool fix upgrades the version of the Export Tool for EJBs and can be found on the original WebSphere Commerce Studio V5.4 CD in the efixes/vaj directory. The fix is stored in the file EJB-1.1-DeployedTool.zip. To install this fix, complete the following steps: 1. Ensure that VisualAge for Java V4.0 is not running. 1. Extract the EJB-1.1-DeployedTool.
PAGE 109
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm This will create the following three files in the \ide\_update directory, where is the installation directory for VisualAge for Java V4.0: – readonly.tfs – readonly.tfi – readonly.txt 3. Open VisualAge for Java V4.0. 4. Select Workspace -> Tools -> Fix Manager. 5. In the Fix manager window, select readonly - Prevent invalid deletion of EJB read-only attributes and click the >> button, then click OK. 6.
PAGE 110
6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm 8. Version the IBM WebSphere Test Environment project by right-clicking on the IBM WebSphere Test Environment project, and selecting Manage -> Version. 9. Select One Name, enter 3.5.3 PQ50159 in the text field and click OK. Install IBM EJB Tool fix To apply the fix to the IBM EJB Tool project, do the following: 1. In VisualAge for Java V4.0, create an open edition of the project IBM EJB Tool. 2.
PAGE 111
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_installation.fm Note: These instructions are only necessary if you choose to import the WebSphere Commerce Suite V5.1 repository into VisualAge for Java V4.0. If you have access to the WebSphere Commerce Suite V5.4 repository and your custom EJBs do not rely on features only present in WebSphere Commerce Suite V5.1, you can use that repository instead, and will not have to delete the packages mentioned here.
PAGE 112
6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm VisualAge for Java V4.0 is now ready for you to import your custom EJBs as part of the migration. This will be covered in 7.5, “Migrating custom EJBs” on page 118. 94 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 113
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_before_migration.fm 6 Chapter 6. Pre-migration steps This chapter describes the tasks needed to prepare the development instance and database for migration. These steps will partially overlap the pre-migration steps for the runtime environment, covered in Chapter 10, “Pre-migration steps” on page 183. This chapter is organized as following: Preparation overview Instance preparation Database preparation © Copyright IBM Corp. 2004.
PAGE 114
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 6.1 Preparation overview This chapter describes the actions needed to prepare the WebSphere Commerce Suite V5.1 development environment prior to migrating to WebSphere Commerce V5.6 Developer. It is recommended to prepare and migrate the elements in the following order: 1. Instance 2.
PAGE 115
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_before_migration.fm 6.2 Instance preparation Before you can migrate the development instance, you must prepare the development system, as described in this section. 6.2.1 Updating the product information file Before running the WCIM tool, you must create a product.xml file for WebSphere Commerce Suite V5.1. This file will be used by the tool to determine details about your installation that are required during the instance migration process.
PAGE 116
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 6. Save and close the file. 7. Copy the file product.dtd from the following directory : \xml To the following directory: \xml For example, we copied the file product.dtd from the directory: D:\WebSphere\WCToolkit56\xml To the following directory: D:\WebSphere\WCS\xml Example 6-1 Example product.
PAGE 117
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_before_migration.fm WebSphere Commerce version edition_name value WebSphere Commerce Suite V5.1 Professional Edition Pro WebSphere Commerce Suite V5.1 Business Edition Business Table 6-2 Choosing the value for mod WebSphere Commerce version mod value WebSphere Commerce Suite V5.1.0.1 0 WebSphere Commerce Suite V5.1.1 1 WebSphere Commerce Suite V5.1.1.
PAGE 118
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm Where is the VisualAge for Java V3.5.3 installation directory. In order for the migration tools to correctly migrate properties files and JSPs, you must ensure that they are located in the directories mentioned. Note: It may be that the properties and JSP files for your store already exist in the mentioned directories. In either case, you should double-check that these files are the correct versions. 6.2.
PAGE 119
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_before_migration.fm “Migrating custom EJBs” on page 118 and 8.2.6, “Configuration and code changes for migrated EJBs” on page 144. Overview VisualAge for Java provided a source control feature through the concept of a repository. This feature allowed typical source control functionality such as restoring previous editions of code and marking releases etc.
PAGE 120
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 3. Select Jar file and click Next. 4. In the Jar file: text box, enter a path and filename for your exported code. In our example, we used D:\MyStoreCommands.jar. 5. Ensure that only the .java check box is checked, and unchecking the .class, resources and beans if necessary. If you wish to check that all of your code is selected correctly, you can click the Details... button next to .java. 6.
PAGE 121
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_before_migration.fm updateDB2Configuration [] Where is the name of the database to change configuration values for and is an optional parameter, naming the file to use for logging the progress of the script. Important: The script must be called from a DB2 Command Window.
PAGE 122
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm Important: Ensure that all connections to the database are terminated before continuing. Otherwise the changes performed by the script in this section may not take effect. 6.3.2 Unsent messages If the development database contains any messages in the MSGSTORE table, these must be removed before migrating the database, as they cannot be handled by WebSphere Commerce V5.6.
PAGE 123
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_before_migration.fm Master catalog In order to be able to use the product management tools in the WebSphere Commerce Accelerator, the store must have a valid master catalog. Refer to “Master catalog” on page 193 for details about master catalogs and a procedure for generating a valid master catalog for your store. Product-item relationship In WebSphere Commerce V5.6 all items must have a product.
PAGE 124
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm All organizations without a parent organization, that is organizations for which the MEMBER_ID column of ORGENTITY is set to null, will have Root Organization assigned as their parent organization. If this is not desired, you must update the MEMBER_ID column for the organizations that must have other parent organizations before migrating.
PAGE 125
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_before_migration.fm Administrators Administrators with register type S or A (Site administrator or Administrators, respectively) that also belongs to an access group must have their profile type set to B (Business user). This is because all future administrators created in Organization Administration Console will have profile type B.
PAGE 126
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 3. Customer Service Representative We found that Store Administrator would be a more suitable role for these two users. Therefore we assigned these two users the Store Administrator role instead.
PAGE 127
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm Once the migration has completed successfully, you must recreate your foreign key relationships manually. If possible, while you are working on the migration, it is a good idea if a member or your team starts create a script that will recreate the references once the migration has completed.
PAGE 128
6320ch_DEV_before_migration.fm 110 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 129
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm 7 Chapter 7. Migrating the development environment This chapter describes the process of migrating your store from the WebSphere Commerce Suite V5.1 development environment with VisualAge for Java V3.5.3 to the WebSphere Studio Application Developer V5.1.1 based WebSphere Commerce V5.6 development environment.
PAGE 130
6320ch_DEV_migration.fm Draft Document for Review July 28, 2004 7:33 pm 7.1 Current development environment This is a high level overview of the development environment as was installed for WebSphere Commerce Suite V5.1 development. Our WebSphere Commerce Suite V5.1 development environment consisted of a single-tier installation of WebSphere Commerce running on DB2 Universal Database V7.2.5. We had a single instance called demo created for our store.
PAGE 131
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm 7.3 Migrating the development instance This section details the use of the WCIM tool to perform the instance migration in your development environment. In WebSphere Commerce Suite V5.1, the development environment is reliant on a local run-time instance. Configuration of the WebSphere Test Environment in VisualAge is taken from the configuration files of this instance.
PAGE 132
6320ch_DEV_migration.fm Draft Document for Review July 28, 2004 7:33 pm 7.3.2 Running the tool To run the WCIM tool, complete the following steps: 1. Open a command prompt in windows. 2. Navigate to the following directory: \bin In our example, we used the following directory: D:\WebSphere\WCToolkitPro56\bin. 3. Run the WCIM tool as follows: wcim -component toolkit -from 51 -instance instancename where instancename is the name of your instance in your development environment.
PAGE 133
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm Event: Starting to execute command com.ibm.commerce.migration.wcim.command.WCIMMigrateStudioCommand Event: Method: migrateDevEnv Enter the previous WebSphere Commerce home directory: D:\WebSphere\WCS Enter the home directory of VisualAge for Java: D:\WebSphere\VAJava Enter the name of the custom code JAR file: D:\MyStoreCommands.
PAGE 134
6320ch_DEV_migration.fm Draft Document for Review July 28, 2004 7:33 pm Note: At this point the WebSphere Test Environment inside WebSphere Studio Application Developer V5.1.1 has been updated and your custom commands and data beans have been imported into WebSphere Studio Application Developer. The development environment is not completely migrated until the migration steps in the following section are completed. 7.
PAGE 135
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm We used the following command: migratedb -dbtype db2 -dbname mall -dbuser dbusr01 -dbpass dbusr01pwd -from 51 -instance demo -schema dbuser01 In our example, with 1400 users, 1400 orders and 2700 order items, the database migration script took 15 minutes. 7.4.2 Migrating encrypted data This sections explains how to run the script to migrate your encrypted data within your database and to reflect a new merchant key.
PAGE 136
6320ch_DEV_migration.fm Draft Document for Review July 28, 2004 7:33 pm 7.4.3 Summary At this point, you should be at the following stage of migration: You have installed and configured the new WebSphere Commerce test environment in WebSphere Studio Application Developer V5.1.1. Your development WebSphere Commerce instance is migrated to the new test environment in WebSphere Studio Application Developer V5.1.1. Your existing development database has been migrated from DB2 Universal Database V7.2.
PAGE 137
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm Note: The process of migrating EJBs to the new specification is not straightforward. The level of effort involved is often the same or greater than recreating the EJBs from scratch using the tools in WebSphere Studio Application Developer V5.1.1. We would recommend that unless you have 10 EJBs or more you should consider recreating them in WebSphere Studio Application Developer V5.1.1.
PAGE 138
6320ch_DEV_migration.fm Draft Document for Review July 28, 2004 7:33 pm VisualAge for Java V3.5.3 EJB 1.0 Repository VisualAge for Java V4.0 EJB 1.1 JAR WebSphere Studio Application Developer V5.1.1 Figure 7-2 Process for converting from EJBs from version 1.0 to 1.1 Before you continue, you must have installed and configured a VisualAge for Java V4.0 system as described in 5.7.1, “Installing VisualAge for Java V4.0” on page 87.
PAGE 139
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm Reminder: Ensure that only EJB code exists in the project you select for export. 4. Right-click on the project and select Export... from the menu. The Export Smart Guide will appear 5. Select Repository as the export destination and click Next. 6. On the next page, make sure that Local Repository is selected. 7. Specify a location for your exported repository in the Repository name text-box. For example, D:\myStoreEjbs.dat 8.
PAGE 140
6320ch_DEV_migration.fm Draft Document for Review July 28, 2004 7:33 pm c. Select the option to import Projects and click Details... next to this option. d. In the window that opens, select your EJB project and click OK. e. Check the option to Add most recent project edition to workspace and click Finish. Even with only small numbers of EJBs in your repository, VisualAge can take several minutes to complete the import. 5.
PAGE 141
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm 3. Choose a path and file name for the JAR file and enter it into the JAR file text box. 4. Ensure that DB2 for NT, V7.1 is selected in the target database list. 5. Check the options for .class and .java. Uncheck resource if it is selected. 6. Click Finish to start the export. Even with small numbers of EJBs, this can take a long time.
PAGE 142
6320ch_DEV_migration.fm 124 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 143
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm 8 Chapter 8. Post-migration steps This chapter describes the additional steps to be performed after the development instance and database have been migrated.
PAGE 144
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm 8.1 Setting up aliases The application that we migrated contained static web content that was addressed outside the scope of the web application in order to minimize the load on the application server. The WebSphere Commerce V5.6 Toolkit does not contain any static web projects when installed, so in order to support static web content, you must do the following: 1. Create a new Dynamic Web Project: a.
PAGE 145
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm Example 8-1 Excerpt from the looseconfig.xmi file : : : PAGE 146
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm : : : 4. Edit the application.xml file located in one of the following directories, depending on the type of test environment that you use: – Full test environment: \applications\wcfull.
PAGE 147
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm : : : 5. Start or restart the server in WebSphere Studio Application Developer. 8.2 Migrating custom code This section describes the mandatory and optional changes necessary to complete the migration from WebSphere Commerce Suite V5.1 to WebSphere Commerce V5.6.
PAGE 148
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm In WebSphere Commerce Suite V5.1, fine-grained resource control was implemented programatically using the following methods: public Long[] getResourceOwners() throws ECException public boolean checkPermission() throws ECException These methods became deprecated in WebSphere Commerce Suite V5.4.
PAGE 149
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm RunTime Framework PolicyManager Command Resource isAllowed(User,Action,Resource) : Command level getOwner( ) getAndApplyApplicablePolicies( ) validateParameters( ) getResources( ) isAllowed(User,Action,Resource) : Resource level getOwner( ) getAndApplyApplicablePolicies( ) fulfills(Member, Relationship) performExecute( ) Figure 8-1 Sequence diagram for WebSphere Commerce V5.6 command framework 8.2.
PAGE 150
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm latter approach is recommended, as validation of the user ID should happen in the update command. Important: UserRegistrationUpdateCmd, UserRegistrationAddCmd and UserRegistrationDeleteCmd must be invoked as URL commands.
PAGE 151
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm com.ibm.commerce.order.utils.ApplyCalculationUsagesCmd com.ibm.commerce.price.commands.ApplyOrderAdjustmentsCmd com.ibm.commerce.fulfillment.commands.ApplyOrderShippingChargesCmd com.ibm.commerce.taxation.commands.ApplyOrderTaxesCmd Typically, the implementation classes for these commands would be referenced by the custom implementation, either by extending or other means.
PAGE 152
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm Note: Table 8-1 does not show any mapping for the WebSphere Commerce Suite V5.1 ApplyCalculationUsagesCmd command. The reason for this is that this command is not meant to be used independently. Instead, this command is the base class for the rest of the calculation commands mentioned. Additionally, Table 8-1 does not display the calculate usage for coupons as this was not available in WebSphere Commerce Suite V5.1.
PAGE 153
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm 2. Use Table 8-1 on page 133 to identify the WebSphere Commerce V5.6 interface that match the WebSphere Commerce Suite V5.1 interface used in the previous step. In our example, the WebSphere Commerce V5.6 interface is com.ibm.commerce.order.calculation.ApplyShippingCmd. 3. Create a custom interface, extending the the WebSphere Commerce V5.6 command interface.
PAGE 154
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm */ protected Item[] getItems() { return iItems; } /** * Set the list of order items that must be processed. */ public void setItems(Item[] items) { super.setItems(items); iItems = items; } /** * Apply order adjustments to all items in iItems. * Update iAppliedItems with the items that have had order adjustments * applied to them. */ public void performExecute() { : : // customized shipping calculation...
PAGE 155
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm public void checkAppliedItems() throws ECException { final String METHOD_NAME = "checkAppliedItems"; if(ECTrace.traceEnabled(COMPONENT)) { ECTrace.trace( COMPONENT, CLASS_NAME, METHOD_NAME, "itemIds=" + CalculationHelper.getInstance().toString(iItems)); ECTrace.trace( COMPONENT, CLASS_NAME, METHOD_NAME, "appliedItems=" + appliedItems); } for(int i = 0; i < iItems.
PAGE 156
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm (, , , current timestamp) Where is the store ID, is the name of the WebSphere Commerce V5.6 interface, matching the original WebSphere Commerce Suite V5.1 interface, and is the full name, including package, of the custom version of the WebSphere Commerce V5.6 implementation class.
PAGE 157
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm and storeent_id=-1 Where is the ID of the store, is the ID of the new entry that was added to the CALMETHOD table and is the calculation usage ID from Table 8-1 on page 133. Interface changes This section gives an overview of the most important changes from WebSphere Commerce Suite V5.1 to WebSphere Commerce V5.6 in the signature of the payment commands.
PAGE 158
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm public java.util.Set getAppliedItems() This method should return a java.util.Set instance containing the Item instances that have had adjustments calculated and applied. The method should be used in the checkAppliedItems method. Note: We found that at the time of writing, the ApplyShippingCmdImpl and ApplyCalculationUsageCmdImpl command implementations did not use the getAppliedItems method from the checkAppliedItems method.
PAGE 159
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm This method has been made obsolete by the introduction of the getCurrency method in the CalculationCmd interface, which is the ancestor interface to ApplyCalculationUsageCmd and ApplyShippingCmd interfaces. public void setOrderItems(...) This method existed in two overloaded versions, taking either an array or a java.util.Enumeration of OrderItemAccessBean instances.
PAGE 160
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm Tip: Mapping OrderItemAccessBean to Item considerations: If an accessor is not available in the interface to Item, it is possible to access the underlying OrderItemAccessBean using the following method: public OrderItemAccessBean getOrderItem() This should be avoided, if at all possible. Table 8-2 shows only the accessors that directly map between OrderItemAccessBean and Item.
PAGE 161
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.
PAGE 162
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm 8.2.6 Configuration and code changes for migrated EJBs EJBs developed in VisualAge for Java V3.5.3 follow the EJB 1.0 specification. these must be converted to EJB 1.1 specification level. Since the process of converting involves exporting the EJB code from VisualAge for Java V3.5.3, importing the EJBs into VisualAge for Java V4.0, exporting from VisualAge for Java V4.
PAGE 163
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm Figure 8-2 Adding string converters to an access bean in VisualAge for Java V3.5.3 The access bean configuration data is stored in the file ibm-ejb-access-bean.xmi, placed in the ejbModule/META-INF folder of the WebSphereCommerceServerExtensionsData project in WebSphere Studio Application Developer V5.1.1. A sample file is shown in Example 8-7. Note that field1 and field2 have set up string converters, whereas field3 does not.
PAGE 164
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm Example 8-7 Example ibm-ejb-access-bean.xmi file PAGE 165
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm 2. Switch to the J2EE Perspective by with clicking it’s icon or clicking Window -> Open Perspective -> J2EE. 3. Expand WebSphereCommerceServerExtensionsData and open the EJB Deployment Descriptor. 4. Click on the Access tab. 5. In the Isolation Level section: a. Click Committed and then click Remove. b. Click Add.... c. Ensure Repeatable read is selected and click Next. d. Select all of your custom EJBs and click Next. e.
PAGE 166
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm g. Save your changes by pressing Ctrl + S and close the EJB Deployment Descriptor document. Remember, these changes will not take effect until you have regenerated the deploy code for your EJBs in “Regenerating the deploy code” on page 152. Add the WCSecurity role Follow these instructions to add the WCSecurity role to all methods in your beans.
PAGE 167
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm Change the container transaction type From the Assembly Descriptor tab of the EJB Deployment Descriptor. (see , “Add the WCSecurity role” on page 148 for details), do the following: 1. If any transaction levels are already associated with your EJBs, you may wish to remove them and re-add them again. This is easier than finding which need to be updated and which do not. 2. In the Container Transactions section, Click Add....
PAGE 168
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm Note: As the ejbCreate method on session beans must have return type void, they are not encompassed by this change. See section 6.10.3 of the EJB 1.1 specification for details on ejbCreate methods for session beans. If one of the ejbCreate methods in your entity bean is not declared to return an object of the primary key type, WebSphere Studio Application Developer V5.1.
PAGE 169
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm Where x.y.z denotes the subsection number in the EJB 1.1 specification in which the use of java.rmi.RemoteException deprecation for the relevant method is mentioned. For ejbCreate and ejbPostCreate this will be 9.2.3 and 9.2.4, respectively.
PAGE 170
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm public abstract java.util.Enumeration findGreaterThan(Integer value) throws java.rmi.RemoteException, javax.ejb.FinderException; Note: Other methods for generating finder methods were available, but the one described here was the recommended method. The FinderHelper interface has been replaced in WebSphere Studio Application Developer V5.1.1 with the use of the file ibm-ejb-jar-ext.
PAGE 171
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm If your WebSphere Commerce Suite V5.1 solution contains code that uses connectors, you must rewrite this code to use the J2EE Connector Architecture. For more information about the J2EE Connector Architecture, see: http://java.sun.com/j2ee/connector Note: This does not apply to code that uses the WebSphere Commerce Suite V5.
PAGE 172
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm 8.2.9 Product Advisor WebSphere Commerce Suite V5.1 contains the following three files in the \samples\web\pa directory: pc51.jsp pe51.jsp sa51.jsp WebSphere Commerce V5.6, during the installation, provides newer versions for these sample files available in the following directories: For WebSphere Commerce V5.6 runtime: – \samples\web\pa – installedApps\\WC_.ear\Stores.
PAGE 173
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm Any code, referring to the types using the old package names must be updated to work with WebSphere Commerce V5.6. 8.2.10 Rule server administration commands A number of changes have been made to the structure and behavior of the rule service administration commands. Refer to Migration Guide for WebSphere Commerce Developer - migrating from WebSphere Commerce Studio V5.1 for details about the changes. 8.2.
PAGE 174
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm D:\WebSphere\AppServer\installedApps\wcs56h\WC_demo.ear\Stores.war\MyS tore the following summary of changes has been added to improve the error handling: Add logic to check the error code returned and create error message to show user Example 8-8 shows part of the content of the modified myAccount.jsp file. The changes are outlined in bold. Example 8-8 The content of the modified myAccount.
PAGE 175
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm the following summary of changes has been added to improve the error handling: Add import statement to import the package which contains the new error codes Add logic to check the error code returned and create error message to show user Example 8-9 shows part of the content of the modified register.jsp file. The changes are outlined in bold. Example 8-9 The content of the modified register.
PAGE 176
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm : Changes to property files The new error codes must have some descriptive text associated with them. This is done in the language-dependent properties file, located in the following directory: \installedApps\hostname\app_name\Stores.war\WEB-INF\classes\store_na me In our example: D:\WebSphere\AppServer\installedApps\wcs56h\WC_demo.ear\Stores.
PAGE 177
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm WAIT_TO_LOGIN = Please wait a few seconds before attempting to log in again. Chapter 8.
PAGE 178
6320ch_DEV_post_migration.fm 160 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 180
6320p02.fm 162 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 181
Draft Document for Review July 28, 2004 7:33 pm 6320ch_install_56.fm 9 Chapter 9. Installing WebSphere Commerce V5.6 This chapter describes the procedure we used to install the WebSphere Commerce V5.6 runtime environment on a single-node. The installation consists of the following part: Single-node runtime overview Installation Verifying the installation © Copyright IBM Corp. 2004. All rights reserved.
PAGE 182
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm 9.1 Single-node runtime overview The following sections describe the software and hardware we used for installing WebSphere Commerce V5.6. 9.1.1 Hardware Ensure that your hardware meets the requirements described in 3.2.2, “Hardware and software prerequisites” on page 41. We installed WebSphere Commerce V5.6 on a system with the following configuration: Intel Pentium 4 1.8 GHz 1.
PAGE 183
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm The user must be defined locally on the system and must belong to the local Administrators group. The user must have the following privileges assigned: – Act as part of the operating system – Create a token object – Increase quotas – Log on as a service – Replace a process level token Note: You must log off and log in again for these privileges to take effect. The user ID must not exceed 20 characters in length.
PAGE 184
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm 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/ 9.2.1 Install WebSphere Commerce V5.6 Perform the following steps to install WebSphere Commerce V5.6: 1. Insert the WebSphere Commerce V5.6 CD 1 into your CD-ROM drive.
PAGE 185
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm – IBM DB2 Universal Database Enterprise Server Edition – IBM HTTP Server Note: The two remaining components, Remote WebSphere Commerce Configuration Manager client and WebSphere Application Server Web server plug-in, should not be selected as this is included in the already selected components. 10.The database and Web server selection window appears.
PAGE 186
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm Note: During the installation of WebSphere Application Server V5.0.2 fixes, the installation progress bar may stay at 95% for a very long time. This is normal behavior. The progress of the fixpack installation can be followed by monitoring the contents of the \logs\update directory and the file \logs\WASFixPack.log, where is the installation directory for WebSphere Application Server. 19.
PAGE 187
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm Port 80 AfpaEnable AfpaCache on AfpaLogFile "/logs/afpalog" V-ECLF If you enable AFPA, ensure that the following line is not active: Listen 80 9.3 Verifying the installation To verify the installation we will perform the following two steps: Verify installation log files Create test instance 9.3.1 Verify installation log files Verify the installation log files.
PAGE 188
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm After a successful installation, the last message in the file install__.log will contain the following text: WebSphere Commerce installation complete. DB2 Universal Database installation logs Examine the following log files: \logs\db2wi.log \logs\DB2.log Where is the installation directory for WebSphere Commerce.
PAGE 189
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm \logs\WASFixPack.err.log Where is the installation directory for WebSphere Application Server. If the installation fails, these files may be placed in the directory pointed to by the tmp Windows environment variable. The default value for this variable is the directory: C:\Documents and Settings\\Local Settings\Temp Where is the name of the currently logged on Windows user. The the log.
PAGE 190
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm was_50_fp2_win.ptfDriver (only for Microsoft Windows 2000) was_502_cf3_win.ptfApplied (only for Microsoft Windows 2000 and Microsoft Windows 2003 Server) was_502_cf3_win.ptfDriver (only for Microsoft Windows 2000 and Microsoft Windows 2003 Server) PQ83918.efixApplied PQ83918.efixDriver PQ84196.efixApplied PQ84196.efixDriver PQ85469.efixApplied PQ85469.efixDriver PQ85933.efixApplied PQ85933.efixDriver PQ86588.
PAGE 191
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm Note: The following log files are shared between WebSphere Application Server and IBM HTTP Server, and may thus contain information for both products: \logs\WASFixes.log \logs\WASFixPack.log \logs\WASFixes.err.log \logs\WASFixPack.err.log 9.3.
PAGE 192
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm 4. The database window appears. Ensure that the Create a new DB2 database or Oracle tablespace option is selected and that the Remote and Advanced Options check boxes are not checked.
PAGE 193
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm When the instance has been successfully created, the following message should appear in the log panel of the Configuration Manager: Event: Instance was successfully created. Also, the message shown in Figure 9-2 will appear. Check that all messages in the dialog indicate success and click OK. Figure 9-2 Commerce instance creation confirmation Create a WebSphere Commerce Payments instance 1.
PAGE 194
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm Note: The chosen Instance Password is only for test purposes. It is strongly recommended to a different password for a production site. When choosing an Instance Password, the password must adhere to the following rules: Must contain at least eight characters. Must contain at least one alphabetic character. Must contain at least one numeric character. The same character cannot occur more than four times in total.
PAGE 195
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm The Payments Instance Creation Wizard will now begin the instance creation. The progress can be monitored on the main Configuration Manager window which may be hidden behind the Payments Instance Creation Wizard. The Payments Instance Creation Wizard may prompt you to restart the Web server as seen in Figure 9-3. Click OK to dismiss the dialog.
PAGE 196
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm 1. Ensure that the instance is not running. Refer to Appendix A., “Managing WebSphere Commerce components” on page 239 for details about checking instance status and stopping WebSphere Commerce instances. 2. Remove the server from WebSphere Application Server by running the following command from the \bin directory: rmCommerceServer Important: The directory, the script is executed from must be \bin.
PAGE 197
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm Tip: The Configuration Manager will remove the instance from the instance list, located in the file wcs_instances. Also, the file \instances\\xml\.xml will be renamed to .xml.bak. To accomplish the same result without opening the Configuration Manager, simply edit the file \instances\wcs_instances.
PAGE 198
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm Example 9-1 Sample rmPaymentServer.bat script @echo off REM Licensed Materials - Property of IBM REM 5724-A18 REM (c) Copyright IBM Corp. 2000, 2004 REM US Government Users Restricted Rights - Use, duplication or REM disclosure restricted by GSA ADP Schedule Contract with IBM Corp. setlocal call config_env.bat if exist %WAS_HOME%\bin\setupCmdLine.bat call %WAS_HOME%\bin\setupCmdLine.
PAGE 199
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm b. Expand the tree until you find the instance to be deleted. c. Right-click the instance name and select Delete instance.... d. You are asked if you really want to delete the instance. Click Yes. e. A message informing that the instance was deleted appears. Click OK. f. Close the Configuration Manager. Tip: The Configuration Manager will remove the instance from the instance list, located in the file wcs_instances.
PAGE 200
6320ch_install_56.fm 182 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 201
Draft Document for Review July 28, 2004 7:33 pm 6320ch_before_migration.fm 10 Chapter 10. Pre-migration steps This chapter describes the actions needed to prepare the WebSphere Commerce Suite V5.1 elements prior to the migration. The chapter is organized in the following sections: Preparation overview Instance preparation Database preparation © Copyright IBM Corp. 2004. All rights reserved.
PAGE 202
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 10.1 Preparation overview This chapter describes the actions needed to prepare the WebSphere Commerce Suite V5.1 production environment prior to migrating to WebSphere Commerce V5.6. It is recommended to prepare and migrate the elements in the following order: 1. Instance 2.
PAGE 203
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 10.2 Instance preparation This section describes the tasks needed to prepare our instance for the WebSphere Commerce V5.6 instance migration script. Some of the tasks needs to be performed in the WebSphere Commerce Suite V5.1 system and some in the WebSphere Commerce V5.6 system. Note: The WebSphere Commerce Suite V5.1 environment does not need to be shut down in order to prepare the instance. 10.2.
PAGE 204
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 6. Update the relevant sections as shown in Example 10-1 on page 186. Ensure that you enter the appropriate levels for your scenario. Refer to Table 10-1, 10-2 and 10-3 for assistance on how to choose the values for your environment. 7. Update the path node with the path to your WebSphere Commerce Suite V5.1 installation, such that it corresponds to the WebSphere Commerce Suite V5.
PAGE 205
Draft Document for Review July 28, 2004 7:33 pm 6320ch_before_migration.fm Table 10-2 Choosing the value for mod WebSphere Commerce version mod value WebSphere Commerce Suite V5.1.0.1 0 WebSphere Commerce Suite V5.1.1 1 WebSphere Commerce Suite V5.1.1.x 1 Table 10-3 Choosing the value for fixpack WebSphere Commerce version fixpack value WebSphere Commerce Suite V5.1.0.1 1 WebSphere Commerce Suite V5.1.1.1 1 WebSphere Commerce Suite V5.1.1.2 2 WebSphere Commerce Suite V5.1.1.
PAGE 206
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 10.2.2 Prepare resources The WCIM tool will create a ZIP archive with the entire directory structure for the instance directory, that is all files under the directory \instances\ Where is the WebSphere Commerce Suite V5.1 installation directory and is the name of your instance. If you have WebSphere Commerce Suite V5.
PAGE 207
Draft Document for Review July 28, 2004 7:33 pm 6320ch_before_migration.fm We copied the database from the WebSphere Commerce Suite V5.1 system to the WebSphere Commerce V5.6 system and performed all the pre-migration preparation steps on it, recording all steps in a database script file. Once our pre-migration script was built and tested on the database copy, we used the same script to perform pre-migration steps on the production database.
PAGE 208
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm The select statement shows how many messages WebSphere Commerce Suite V5.1 still needs to deliver. The result is one row, one column with a numeric result that is 0 (zero) or greater. If the result is 0, it means that there are no pending messages to be delivered and that the table is ready to be migrated. If the result is greater than 0, it means that WebSphere Commerce Suite V5.1 is still attempting to deliver remaining messages.
PAGE 209
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm d. Click Yes on the Confirmation dialog window. The WebSphere Application Server Administrative Console will close automatically. Ensue that all database background processes and connections are terminated by typing the following commands from a DB2 command line: DB2 terminate DB2 force application all 2. Take a offline backup of the database in the WebSphere Commerce Suite V5.
PAGE 210
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 10.3.3 Updating database configuration values The database configuration values, such as logfile size, application heap and statement heap, must be updated up to WebSphere Commerce V5.6 level prior to running any migration scripts. A script file is provided with WebSphere Commerce V5.6 for updating the database configuration values: \bin\updateDB2Configuration.
PAGE 211
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm Parameter Value catalogcache_sz 4096 Important: Ensure that all connections to the database are terminated before continuing. Otherwise the changes performed by the script in this section may not take effect. 10.3.4 Orders status Orders still in state C (Complete - Payment has been authorized) will be reallocated from the inventory when the WebSphere Commerce V5.6 system is brought online.
PAGE 212
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm introduced in WebSphere Commerce Suite V5.4. The master catalog rule is enforced and therefore will need to be added during the migration. The Product Management Tool only work with the master catalog. The structural restrictions for a master catalog are: The master catalog must be a proper tree with no cycles e.g The parent category A has a subcategory B. Subcategory B and any of B’s subcategories must not have A as their child.
PAGE 213
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm In our example we only had one catalog which did not comply with the restrictions set for a master catalog as it had items, which belonged to more than one category. This meant that we had to create a new master catalog and use the existing catalog as a sales catalog. To create a master catalog we performed these steps: 1. Create catalog insert into catalog values (10002,-2000,'Master Catalog','Master Catalog') 2.
PAGE 214
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm update keys set counter=(select max(counter) from keys where tablename='catgroup')+1 where tablename='catgroup' Product-item relationship In WebSphere Commerce V5.6 all items must have a product. This rule is enforced as the Product Management Tool uses products as its starting point. This rule can be applied in two ways (if needed): 1. Manually create products and associate items.
PAGE 215
Draft Document for Review July 28, 2004 7:33 pm 6320ch_before_migration.fm Users with an entry in BUSPROF and with PROFILETYPE set to B (Business user) will be assigned the organization, pointed to by the ORGUNIT_ID or ORG_ID columns, as follows: – If ORGUNIT_ID is not null, the organization pointed to by ORGUNIT_ID, is used. as the user’s parent organization – If ORGUNIT_ID is null and ORG_ID is not null, the organization pointed to by ORG_ID, is used as the user’s parent organization.
PAGE 216
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm where registertype in ('A','S') and users_id in (select users_id from accmbrgrp) Role changes Some of the roles in WebSphere Commerce Suite V5.1 are no longer available in WebSphere Commerce V5.6. Table 10-5 lists the WebSphere Commerce Suite V5.1 and the roles that should be used in WebSphere Commerce V5.6. Table 10-5 Roles that are not included in WebSphere Commerce V5.6 WebSphere Commerce Suite V5.1 role WebSphere Commerce V5.
PAGE 217
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 2. Delete all roles for user. delete from accmbrgrp where users_id= 3. Add Store Administrator as role for our users. insert into accmbrgrp values (-6,,-2000,NULL) 10.3.
PAGE 218
6320ch_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm 10.3.9 Erroneous data in encrypted fields Before migrating encrypted data, you should check the following fields in Table 10-6 for data that has a leading space and is unencrypted. In WebSphere Commerce, in a field that may be encrypted, such as the field listed in Table 10-6, the presence of a leading space indicates that the field contains encrypted data.
PAGE 219
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm 11 Chapter 11. Migrating WebSphere Commerce components This chapter describes the actions needed to migrate the WebSphere Commerce Suite V5.1 elements to the WebSphere Commerce V5.6 environment. This chapter is organized in the following sections: Migration overview Migrating commerce instance configuration Migrating commerce database Migrating Payment Manager © Copyright IBM Corp. 2004. All rights reserved.
PAGE 220
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm 11.1 Migration overview This chapter describes the actions needed to migrate the WebSphere Commerce Suite V5.1 elements to the WebSphere Commerce V5.6 environment. It is recommended to prepare and migrate the elements in the following order: 1. Instance 2. Database The preparation steps are described in Chapter 10, “Pre-migration steps” on page 183. The following is a list of the specific sections that are covered.
PAGE 221
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm Note: Although Co-existence is supported by the WCIM tool, it is not supported in Microsoft Windows platform. For more information on instance migration approaches please refer to Chapter 3, “Migration Strategy and Planning” on page 37 We choose to do an Switch-Over migration as we had available hardware running WebSphere Commerce V5.6. The following are the high level steps that needs to be performed during a Switch-Over migration: 1.
PAGE 222
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm The WCIM tool wcim.bat, is provided to do the instance migration. WCIM is located in the following directory: \bin\ In our example: D:\WebSphere\CommerceServer56\bin Note: The WCIM tool must be run from the WebSphere Commerce V5.6 bin subdirectory. Refer to Migration Guide for Windows 2000 and Windows 2003 - migrating from WebSphere Commerce Suite V5.1 for a complete syntax information.
PAGE 223
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm Note: all the information required for this step is derived from the WebSphere Commerce Suite V5.1 system. – The WebSphere Application Server home directory . – The WebSphere Application Server administration node name. – The WebSphere Application Server node name. – Whether the IBM HTTP Server is installed locally or not. – The IBM HTTP Server home directory . On the WebSphere Commerce Suite V5.
PAGE 224
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm Copy the generated file, instance_backup.zip, to the working directory on the WebSphere Commerce V5.6: \temp Unpack the instance_backup.zip file in the working directory of WebSphere Commerce V5.6 machine. This will produce the following file: \temp\zip\backupwc_51_instance_name.zip 6.
PAGE 225
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm – Is a new IBM HTTP Server installed locally? [DEFAULT yes] yes – Enter the new IBM HTTP Server home directory: D:\WebSphere\IBMHTTPServer – Enter a new Web server host name: [DEFAULT wc56.itso.ral.ibm.com] wc56.itso.ral.ibm.com – Are the old instance and the new instance using the same database server? [DEFAULT yes] no Running the above command will migrate your instance to the WebSphere Commerce V5.6 level. 7.
PAGE 226
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm approach would result in minimum hassle. All the database migration tasks were done in WebSphere Commerce V5.6 system. Refer to Appendix C, “Migration scripts” on page 255 for details on custom scripts behavior. Here is the high level steps and order required to migrate the WebSphere Commerce database: 1. Migrating the database 2. Choosing the master catalog 3.
PAGE 227
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm -precheck Table 11-1 details the mandatory parameters and values for the database migration script. Note: For migratedb.bat script to succeed the following rules must be applied: 1. migratedb.bat must be executed from a DB2 command window (db2cmd) 2. All the connections to the database must be terminated prior to and during the script execution.
PAGE 228
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm In our example: D:\WebSphere\CommerceServer56\logs\migration\instancename\migrateddb51_time stamp.log Example 11-1 A Sample of the migration log file with the precheck option set [2004.04.30 11:38:29] Info : Logging started in VERBOSE mode. [2004.04.30 11:38:29] Info : DTD path: ... [2004.04.30 11:38:29] Event: Loading plan: D:\WEBSPH~1\COMMER~1\schema\migration\config\DataMigrationPlan51.xml [2004.04.30 11:38:32] Info : Plan loaded.
PAGE 229
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm In the above example the migration script has generated two warning (outlined in bold). The first one is to warn you that the transaction log size would get full and cause the migration script to fail. To solve this we updated the size of the transaction log to 30,000 blocks which should be enough for even very large databases.
PAGE 230
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm [2004.04.29 21:08:36] Error: [IBM][CLI Driver][DB2/NT] SQL0605W The index was not created because the index "DBUSR01.I0000433" already exists with the required description. SQLSTATE=01550 . . . [2004.04.29 21:09:35] Info : CREATE INDEX I0000539 ON contract ( member_id ASC ) [2004.04.29 21:09:35] Error: [IBM][CLI Driver][DB2/NT] SQL0601N The name of the object to be created is identical to the existing name "DBUSR01.
PAGE 231
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm db2 create index on
( ) The index exists but on the wrong table. Typically it would exist on the same tablename with an ‘_OLD appended to it (e.g for above mentioned table the index would exist on ‘CONTRACT_OLD’ instead of on ‘CONTRACT’).
PAGE 232
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm --please replace MASTERCATALOG_ID with one of the catalog of the store you want to designate as MasterCatalog update storecat set mastercatalog='1' where catalog_id=10002 and storeent_id=10001; insert into catgrptpc (catgroup_id,catalog_id,tradeposcn_id) values (0,10002,10001); To execute the file, run the following from a DB2 command window: db2 -tvf choosemc.sql Ensure that the script has run successfully be examining the output. 11.
PAGE 233
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm data, instead a system key was used. Since this behavior has changed the data must be re-encrypted. To summarize, the encrypted data must be re-encrypted because: Salt key is introduced for passwords One way hash keys are used for passwords Prior to WebSphere Commerce Suite V5.1.1.
PAGE 234
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm Table 11-3 Encrypted data migration script parameters and behavior Behavior needed Parameters to include A non-default WebSphere Commerce Suite V5.1 merchant key is used and should be reused. dbtype instance (optional) example: migrateencryptedinfo db2 demo A default WebSphere Commerce Suite V5.1 merchant key is used and needs to be redefined as a custom merchant key.
PAGE 235
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm Note: At the time of writing this book this script had an error when managing the logs. The log files after execution are empty, but still can be monitored during the execution time. We used the tail command (unix command) as it would show the content on the fly (to have this unix command in a windows environment, an additional unix tool package for windows needs to be installed).
PAGE 236
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm 3. On the WebSphere Commerce Payments Node, run WCIM to package the tool. 4. Transfer WCIM tool package to the WebSphere Payment Manager Node. 5. On the WebSphere Payment Manager Node, run WCIM to backup instance and other assets. 6. Backup WebSphere Payment Manager database. 7. Transfer the backups to the WebSphere Commerce Payments Node. 8. Restore WebSphere Payment Manager database on the WebSphere Commerce Payments Node. 9.
PAGE 237
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm a. Open the WebSphere Application Server Administrative Console b. Expand the Administrative Domain c. Expand the Node d. Right click on the WebSphere Payment Manager application server and select Stop e. Click OK on the information dialog window that confirms the command completed successfully f. Close the WebSphere Application Server Administrative Console 3.
PAGE 238
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm 2. On the Language selection window, select the language and click OK 3. The Welcome window will appear. Click Next. 4. Select I accept the terms in the license agreement and click Next. 5. The Installation Wizard will display a warning window. Check to see if these warnings apply to you. Click Next when all problems have been resolved. 6. The system will prompt for the installation type. Select Custom Installation and click Next. 7.
PAGE 239
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm 17.Insert the IBM WebSphere Commerce V5.6 CD 2 when the Installation Wizard prompts for it and click OK 18.A window confirming that WebSphere Commerce V5.6 has been installed is shown. Click Next 19.The Installation Wizard prompts for restarting the system. Ensure that Restart now is selected and click Finish 11.4.
PAGE 240
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm 2. Copy the file \temp\zip\backupwcim.zip to the WebSphere Payment Manager Node directory \temp\zip and unzip it to the directory \temp. For example, we unzipped the file to the directory D:\WebSphere\PaymenManager\temp, creating the following subdirectories: – – – – – bin java lib payments xml 11.4.
PAGE 241
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm Note: At the time of writing this book WebSphere Payment Manager instance backup failed because of a missing file, the error shows as follows: Error: File C:\Progam Files\IBM\PaymentManager/temp/xml/migration\ instbackupwpm221.xml does not exist. Terminate WCIM. Copy this file from the WebSphere Commerce V5.6 node if it is not present on your WebSphere Commerce Payments Node before running the above command.
PAGE 242
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm DB2 backup db payman to c:\db2backup 11.4.6 Transfer assets to WebSphere Commerce Payments node The assets need to be transferred from the WebSphere Payment Manager Node to the new WebSphere Commerce Payments Node. 1. Transfer the instance backup file, wcbackupwpm221.zip, from the \temp\zip directory on the WebSphere Payment Manager Node to the \temp\zip directory on the WebSphere Commerce Payments node. 2.
PAGE 243
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm – Please type the new WAS node name: [DEFAULT ] In our example, we accepted the default – Please type Payment DataBase password: In our example, we entered dbuser01pwd 2. Verify the logs located in \temp\logs and review in the following file: wcim.migration.wpm.default.wpm221..
PAGE 244
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm l. click on New to create a new datasource m. we used these values to create the new datasource: • Name: migrated_default Commerce Payments Datasource • JNDI Name: jdbc/ migrated_default Commerce Payments Datasource • Database name: payman • Default User ID: dbusr01 • Default Password: dbusr01pwd click OK n. in the messages area, click on Save and then again on the Save button to save these changes o.
PAGE 245
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm Note: When configuring these parameters pay special attention to these values, they must match to what you have configured in the commerce instance. Make sure that the commerce instance has properly configured the WebSphere Commerce Payments Web Server Hostname and ports values. 11.4.
PAGE 246
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm 1. Still on the WebSphere Commerce Payments Node open a DB2 Command Window and navigate to the \bin directory, in our example: D:\WebSphere\CommerceServer56\bin 2. run migratepaymentsdb.bat with the following parameters: migratepaymentsdb db2 in our example migratepaymentsdb db2 payman dbusr01 dbusr01pwd dbusr01 This concludes the payments database migration.
PAGE 247
Draft Document for Review July 28, 2004 7:33 pm 6320ch_post_migration.fm 12 Chapter 12. Post-migration steps This chapter describes the additional steps to be performed after the production instance and database have been migrated. This chapter is organized in the following sections: Post migration steps for IBM HTTP Server – Migrating static content – Updating configuration Deploying – Deploying EJBs – Deploying commands and databeans – Deploying store assets © Copyright IBM Corp. 2004.
PAGE 248
6320ch_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm 12.1 Post migration steps for IBM HTTP Server After migrating WebSphere Commerce, there are still some steps that require to be done manually. These steps will vary from one environment to another depending if it is a single or a multi-node environment. 12.1.1 Migrating static content The static HTML content must be moved over manually.
PAGE 249
Draft Document for Review July 28, 2004 7:33 pm 6320ch_post_migration.fm Example 12-1 WebSphere Commerce section of httpd.conf ########## IBM WebSphere Commerce (Do not edit this section) ################# . . . ########## End of IBM WebSphere Commerce (Do not edit this section) ########## If one of the following Web Server is used, then the configuration must be migrated manually: IBM HTTP Server running remote from WebSphere Commerce V5.
PAGE 250
6320ch_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm Configure and export the JAR file To configure and export the JAR file, perform the following steps: 1. Open WebSphere Commerce development environment (Start > Programs > IBM WebSphere Commerce development environment > WebSphere Commerce development environment) and switch to the Project Navigator view. 2. Expand the EJB project WebSphereCommerceServerExtensionsData 3. Double-click EJB Deployment Descriptor. 4.
PAGE 251
6320ch_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm 1. Stop the WebSphere Commerce instance that is running within WebSphere Application Server V5.0.2. 2. Locate the original EJB JAR file (WebSphereCommerceServerExtensionsData.jar) in the WebSphere Commerce instance. The EJB file will be located in: \installedApps\host_name\instance_name.ear 3. Make a backup copy of the original EJB JAR file to a convenient directory 4.
PAGE 252
6320ch_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm 2. Right-click the WebSphereCommerceServerExtensionsLogic project and select Export. The Export wizard opens. 3. In the Export wizard, do the following: a. Select JAR file and click Next. b. Ensure that Export generated class files and resources is selected. c. Do not select Export Java source files and resources. d. In the Select the export destination field, enter WebSphereCommerceServerExtensionsLogic.
PAGE 253
6320ch_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm 1. Open WebSphere Commerce development environment (Start > Programs > IBM WebSphere Commerce development environment > WebSphere Commerce development environment) and switch to the Project Navigator view 2. Expand the Stores folder 3. Right-click the Web Content directory and select Export. The Export wizard opens. 4. In the Export wizard, do the following: a. Select File system and click next b.
PAGE 254
6320ch_post_migration.fm 236 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 255
6320p04.fm Draft Document for Review July 28, 2004 7:33 pm Part 4 Part 4 Appendixes © Copyright IBM Corp. 2004. All rights reserved.
PAGE 256
6320p04.fm 238 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 257
Draft Document for Review July 28, 2004 7:33 pm 6320ax04.fm A Appendix A. Managing WebSphere Commerce components The following appendix provides information on how to check the status, start and stop various WebSphere Commerce components for the runtime environment as well as detailed information for enabling tracing and re-creating missing password scripts for the development environment.
PAGE 258
6320ax04.fm Draft Document for Review July 28, 2004 7:33 pm WebSphere Commerce instance management This section describes how to start and stop, as well as how to check the status, of the WebSphere Commerce instance. Note: The parameters to the serverStatus, startServer and stopServer scripts are case sensitive. Checking instance status Run the following command from the \bin directory: serverStatus WC_ Where is the name of the instance.
PAGE 259
Draft Document for Review July 28, 2004 7:33 pm 6320ax04.fm ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: WC_ Stopping the instance Run the following command from the \bin directory: stopServer WC_ Where is the name of the instance.
PAGE 260
6320ax04.fm Draft Document for Review July 28, 2004 7:33 pm Other messages are possible, for example when the instance is starting or stopping. Starting the instance Run the following command from the \bin directory: startServer _Commerce_Payments_Server Where is the name of the instance. When the instance is started, the last message from the serverstatus command should be: ADMU3200I: Server launched. Waiting for initialization status.
PAGE 261
Draft Document for Review July 28, 2004 7:33 pm 6320ax04.fm 1. Ensure that the DB2 Universal Database V8.1 instance is running by entering the following command in a Windows command window: db2start The output from this command should be as follows: SQL1063N DB2START processing was successful. If the instance was already running, the output will be as follows: SQL1026N The database manager is already active. 2.
PAGE 262
6320ax04.fm Draft Document for Review July 28, 2004 7:33 pm Tip: If you forget the password for the webadmin user, you can reset the password manually by editing the file \instances\PwdMgr.xml. This file contains the password in encrypted form. To change the password, run the command: wcs_encrypt Where is the new password for the webadmin user. Copy the ASCII encrypted string output from this command and insert it into the LoginPassword node of the PwdMgr.xml file.
PAGE 263
Draft Document for Review July 28, 2004 7:33 pm 6320ax04.fm Follow the instructions in this section to modify the trace specification for a running server. Note: The commands shown in this section are very long and may span more than one line. All commands should be entered on one single line in the wsadmin tool. 1. Identify the SOAP port for your server by opening the SystemOut.log file, residing in the directory \logs\. Search for the string SOAP connector available at port.
PAGE 264
6320ax04.fm Draft Document for Review July 28, 2004 7:33 pm WASX7209I: Connected to process "WC_demo" on node WC56 using SOAP connector; The type of process is: UnManagedProcess WASX7029I: For help, enter: "$Help help" wsadmin> Note: If you get the following messages when attempting to launch wsadmin, you have either specified a wrong SOAP port number, or the server you are trying to reach is not started: WASX7023E: Error creating "SOAP" connection to host ""; exception information: com.ibm.
PAGE 265
Draft Document for Review July 28, 2004 7:33 pm 6320ax04.fm Tip: The trace strings for the various WebSphere Commerce components can be found in the WebSphere Commerce InfoCenter at the following address: http://publib.boulder.ibm.com/infocenter/wc56help/topic/com.ibm.commer ce.admin.doc/refs/rlslogging.htm Also, to enable logging for more than one component, separate the trace strings with a colon, for example: com.ibm.websphere.commerce.WC_ORDER=all=enabled:com.ibm.websphere.comm erce.
PAGE 266
6320ax04.fm Draft Document for Review July 28, 2004 7:33 pm To change the tracing level and which components have tracing enables, edit the following file: \properties\com\ibm\commerce\litecontainer\Logging.properti es. Where is the base directory for the WebSphere Commerce V5.6 Toolkit. Uncomment the components that you wish to enable tracing for.
PAGE 267
Draft Document for Review July 28, 2004 7:33 pm 6320ax04.fm 1. Double-click the Full WebSphere Test Environment server in the Servers panel of the Debug or J2EE perspectives. 2. Expand the Tracing section on the Server tab. 3. Ensure that Enable trace is checked and enter the WebSphere Application Server trace string. Create missing password scripts The WebSphere Commerce V5.6 Toolkit lacks support for generation of passwords for WebSphere Commerce and WebSphere Commerce Payments.
PAGE 268
6320ax04.fm Draft Document for Review July 28, 2004 7:33 pm Example: A-4 wcs_pmpassword.bat script for WebSphere Commerce V5.6 Toolkit @echo off %~d0 cd %~p0 setlocal rem Pick up the WebSphere Commerce environment variables call setenv.bat set CP=%RUNTIME_CLASSES%;%PROPERTIES%;%RUNTIME_JARS%\wcs.jar %JAVA_HOME%\bin\java -classpath %CP% com.ibm.commerce.util.WCSPMPassword %1 %2 endlocal 250 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 269
Draft Document for Review July 28, 2004 7:33 pm 6320ax03.fm B Appendix B. Backup WebSphere Commerce Suite V5.1 This appendix provides instructions for backing up the WebSphere Commerce environment. Two main aspects will be covered, backing up the directory structure where WebSphere Commerce is installed and backup up the database. This appendix is organized in the following structure: File system Database © Copyright IBM Corp. 2004. All rights reserved.
PAGE 270
6320ax03.fm Draft Document for Review July 28, 2004 7:33 pm File system The directories where WebSphere Commerce resides along with any other user defined directory needs to be backed up. For example, the default installation directory, configuration files, and any customized files and directories (generally defined for static content). Default directories The default directories are made up of the installation directory including all its subdirectories and files.
PAGE 271
Draft Document for Review July 28, 2004 7:33 pm 6320ax03.fm WebSphere Commerce Payments (formerly WebSphere Payment Manager), the Web server, and the IBM Developer Kit Java 2 Technology Edition. For example, you may have changed the IBM HTTP Server document root to a directory outside the default WebSphere Commerce install directory. This directory would need to be included in the backup.
PAGE 272
6320ax03.fm Draft Document for Review July 28, 2004 7:33 pm shut down the connected applications, reissue the db2 list applications command and verify that no data is returned by the status monitor. 5. Ensure that all your Commerce Suite 5.1 databases (such as MSER, MALL, and so on) are cataloged. To view a list of all the cataloged databases in the current instance, type the following command: db2 list database directory 6.
PAGE 273
Draft Document for Review July 28, 2004 7:33 pm 6320ax02.fm C Appendix C. Migration scripts This appendix describes in detail the behavior for each of the scripts we used during the migration. The appendix is organized in the following sections: WebSphere Commerce V5.6 migration scripts behavior Custom database migration scripts behavior © Copyright IBM Corp. 2004. All rights reserved.
PAGE 274
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm WebSphere Commerce V5.6 migration scripts behavior This section discusses the specific execution behaviors of the various migration scripts. This information would be useful for the advanced users who have gone through various test-runs of migration and are concerned about performance tuning the database for quicker migration by understanding the underlying execution behavior of these scripts.
PAGE 275
Draft Document for Review July 28, 2004 7:33 pm 6320ax02.fm This file controls the sequence of execution of various SQL files, in addition to other activities. This provides fine grain control over how migration should proceed. Here are some examples of the usefulness of this approach. Some of the column lengths have decreased in the WebSphere Commerce V5.6 schema when compared to the column lengths in WebSphere Commerce Suite V5.1.
PAGE 276
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm instead a system key was used. Since this behavior has changed the data must be re-encrypted. b. PDI flag enforcement: The variable PDIEncrypt (on | off) in the instance file indicates if credit card data is encrypted. Depending on the value of this variable credit card information is encrypted or decrypted accordingly. This script provides you with an opportunity to change and enforce the PDI encryption setting. 2.
PAGE 277
Draft Document for Review July 28, 2004 7:33 pm 6320ax02.fm The following two are additional steps for Switch-Over instance migration (for Runtime environment only). You will not need to do these before migrating a local WebSphere Commerce Suite V5.1 instance or a WebSphere Commerce Studio V5.1 instance. 1. Package WCIM on v5.6 machine and its environment for remote execution: Run WCIM to create a zip file including WCIM itself as well as the environment it requires.
PAGE 278
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm – The JDBC provider and the datasource is configured for the server. The migrated EAR is installed onto the server. – The deployment descriptor is modified as well. – Configuration of the original instance, including instance itself, access control, organization, trading, loader, payment, and store JSPs are migrated. – The Web server host name and the database name / SID can also be changed by WCIM during the migration if users choose to do so.
PAGE 279
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm The batch scripts consists of: testrun.bat This file is the initial start file. This will call migration.bat with the correct parameters. migration.bat This file will perform the actual migration. It calls other scripts in the following order: i. pre.migration.bat ii. migratedb.bat (WebSphere Commerce V5.6 script) iii. post.migration.bat pre.migration.bat This file will perform all the pre-migration tasks. post.migration.
PAGE 280
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm 2. DB user id 3. DB password 4. Log directory 5. Instance name The script has the following behavior: 1. Set parameters as local variables 2. Call updateDB2Configuration.bat to update the database attributes 3. Update the database attribute logfilesize to 30000 4. Stop and start DB2 for changes to take effect 5. Connect to database 6. Execute pre.migration.sql file, refer to, “Database preparation SQL script” on page 263 for more details 7.
PAGE 281
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm db2 -tvf pre.migration.sql > %logfile% echo Disconnect db2 terminate Database preparation SQL script The SQL file executes the changes needed on the database needed to prepare the database for migration. The pre.migration.sql file will perform the following tasks: 1. Clear MSGSTORE table (not to be used on production database, refer to Section 10.3, “Database preparation” on page 188 for more information) 2.
PAGE 282
6320ax02.
PAGE 283
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm 4. Call WebSphere Commerce V5.6 database migration script migratedb.bat to migrate the database 5. Call post.migration.bat to perform the final post tasks The content of the migration.bat file: Example: C-4 Content of the migration.bat file @echo off set set set set set database=%1 user=%2 passwd=%3 logdir=%4 instance=%5 echo Set environment call config_env.bat echo Call pre migration script call pre.migration.
PAGE 284
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm 3. Apply patch for migrateencryptedinfo.bat into Utilities.jar, refer to Chapter 11, “Migrating WebSphere Commerce components” on page 201 for more details on why this patch is applied 4. Call WebSphere Commerce V5.6 encrypted data migration script migrateencryptedinfo.bat to migrate the encrypted data 5. Execute choosemc.
PAGE 285
Draft Document for Review July 28, 2004 7:33 pm 6320ax01.fm D Appendix D. Moving from single to multi-node environment This appendix describes the steps needed to move from a single-node runtime implementation to a multi-node remote database runtime environment after the migration took place. Most of the steps described in this appendix are based on what we have already documented in previous chapters.
PAGE 286
6320ax01.fm Draft Document for Review July 28, 2004 7:33 pm Single-node environment In Part 3, “Production environment” on page 161 we discussed how to install WebSphere Commerce V5.6 on a single-node runtime environment and create a test instance to verify the installation. Later we migrated an entire application from WebSphere Commerce Suite V5.1 to WebSphere Commerce V5.6.
PAGE 287
Draft Document for Review July 28, 2004 7:33 pm 6320ax01.fm 12.Still in the Computer Management window, right-click on the user you just created and select Properties from the menu. 13.Click the Member Of tab and click the Add... button. 14.Select Administrators from the list of user groups and click Add. 15.Click OK to add the user to the group and then click OK to close the user properties window. 16.Close the Computer Management window. Installing DB2 To install DB2 Universal Database V8.
PAGE 288
6320ax01.fm Draft Document for Review July 28, 2004 7:33 pm If you are prompted to restart your computer, do so at this point. After a few seconds, the First Steps window will appear. Close this window. Moving the database In order to move the database to the remote database node it is necessary to backup, transfer and restore the current database into the remote node. These steps are summarized as follows: take the production WebSphere Commerce node offline.
PAGE 289
Draft Document for Review July 28, 2004 7:33 pm 6320ax01.fm create a local alias for the remote database DB2 catalog db at node Verify connectivity To verify the connectivity with the remote database node from the WebSphere Commerce node type the following command: DB2 connect to using using You should receive the Database Connection Information display with the database server version, user ID used in the connection and the database name.
PAGE 290
6320ax01.fm 272 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 291
Draft Document for Review July 28, 2004 7:33 pm 6320addm.fm E Appendix E. Additional material This redbook refers to additional material that can be downloaded from the Internet as described below. Locating the Web material The Web material associated with this redbook is available in softcopy on the Internet from the IBM Redbooks Web server. Point your Web browser to: ftp://www.redbooks.ibm.com/redbooks/SG246320 Alternatively, you can go to the IBM Redbooks Web site at: ibm.
PAGE 292
6320addm.fm Draft Document for Review July 28, 2004 7:33 pm sample.zip Zipped containing the rmPaymentsServer.bat script and a copy of the product.xml.51.sample file. How to use the Web material Create a subdirectory on your workstation, and unzip the contents of the Web material zip file into this folder. Detailed instructions on how to used these scritps are provided in Chapter 9, “Installing WebSphere Commerce V5.
PAGE 293
Draft Document for Review July 28, 2004 7:33 pm 6320abrv.fm Abbreviations and acronyms This abbreviations Use this file by adding names and acronyms file is and descriptions to it. Sort optional.
PAGE 294
6320abrv.fm 276 Draft Document for Review July 28, 2004 7:33 pm Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.
PAGE 295
Draft Document for Review July 28, 2004 7:33 pm 6320bibl.fm Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. IBM Redbooks For information on ordering these publications, see “How to get IBM Redbooks” on page 278. Note that some of the documents referenced here may be available in softcopy only. WebSphere Commerce V5.
PAGE 296
6320bibl.fm Draft Document for Review July 28, 2004 7:33 pm http://java.sun.com/products/ejb/docs.html J2EE Connector architecture http://java.sun.com/j2ee/connector/ WebSphere Payment Manager support http://www.ibm.com/software/genservers/commerce/paymentmanager/support.html DB2 Information Center http://publib.boulder.ibm.com/infocenter/db2help/index.
PAGE 297
6320IX.fm Draft Document for Review July 28, 2004 7:33 pm Index A access bean ibm-ejb-access-bean.
PAGE 298
6320IX.
PAGE 299
6320IX.fm Draft Document for Review July 28, 2004 7:33 pm instance start 240 status 240 stop 241 InterChange Server 28 interface custom 135 interfaces FinderHelper 151 inventory management 31 Inventory subsystem 20 isolation level change access 146 J J2EE Connector Architecture 152 java.rmi.RemoteException 150 JCA 152 K key merchant 214 SALT 214 L LDAP 14, 16, 19 Loader Package 27 logon command 132 looseconfig.
PAGE 300
6320IX.
PAGE 301
6320IX.
PAGE 302
6320IX.
PAGE 303
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50# smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5” spine. Now select the Spine width for the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your 285 (0.5” spine) 0.475”<->0.
PAGE 304
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50# smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5” spine. Now select the Spine width for the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your (2.5” spine) 2.5”<->nnn.
PAGE 305
PAGE 306
Back cover ® Draft Document for Review July 28, 2004 7:34 pm Keeping Commerce Applications Updated WebSphere Commerce Migration Strategy and Planning Production and Development Environments Step-by-Step Instructions This IBM Redbook will assist you in the migration of WebSphere Commerce V5.1 applications. The migration path includes the development and production environments. This guide presents a migration strategy and planning, migration tools, and practical migration examples.
Who We Are
About Us
Company
Careers
Terms & Privacy
Resources
List of Manufacturers
Support
For the Press
Media assets
FAQ
Get in touch
Blog
Email
DMCA
ManualShelf © 2013-2025