Best practices and tools for creating WebSphere Commerce sites / / [Hernan Cunico, Nicolai Nielsen, Sanjeev Sharma]

• Record Nr.: UNINA9910816216003321
• Autore: Cunico Hernan
• Pubbl/distr/stampa: [S.l.], : IBM, International Technical Support Organization, c2005
• Edizione: [1st ed.]
• Descrizione fisica: 1 online resource (274 p.)
• Collana: WebSphere software; IBM redbooks
• Altri autori (Persone): NielsenNicolai; SharmaSanjeev (Information technology executive)
• Disciplina: 658.8/72
• Soggetti: Electronic commerce; Web sites - Design
• Lingua di pubblicazione: Inglese
• Formato: Materiale a stampa
• Livello bibliografico: Monografia
• Note generali: "March 2005."; "SG24-6699-00."
• Nota di bibliografia: Includes bibliographical references and index.
• Nota di contenuto: Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Summary of changes -- March 2005, First Edition -- Part 1 Systematic project development method -- Chapter 1. Introduction -- 1.1 Method overview -- 1.2 Further information -- Chapter 2. Method for project development -- 2.1 Systematic development method -- 2.2 Definitions -- 2.2.1 Work product -- 2.2.2 Deliverable -- 2.2.3 Phase -- 2.2.4 Activity -- 2.2.5 Task -- 2.2.6 Work unit -- 2.2.7 Work breakdown structure -- 2.2.8 Strategy -- 2.2.9 Customer -- 2.2.10 Customer IT team -- 2.2.11 Project team -- 2.2.12 Project repository -- 2.3 Project life cycle -- 2.3.1 Core development phases -- 2.4 Using the method -- 2.4.1 Customizing and adopting the method -- 2.4.2 Project roles and skills requirements -- 2.4.3 Structuring information -- 2.4.4 Case studies -- 2.5 Summary -- Chapter 3. Design phase -- 3.1 Purpose of the design phase -- 3.2 The design phase -- 3.2.1 Creating the site design -- 3.3 Solution outline activity -- 3.3.1 Gathering the functional requirements -- 3.3.2 The solution outline workshop -- 3.3.3 The solution outline document -- 3.3.4 Analyzing current site assets -- 3.3.5 Design-based sizing -- ; 3.4 Macro design activity -- 3.4.1 Methods of approaching design activities -- 3.4.2 The data model -- 3.4.3 Creating interaction diagrams and class diagrams -- 3.4.4 JSPs templates -- 3.4.5 Creating a WebSphere Commerce site database -- 3.5 Micro design activity -- 3.6 Design review -- 3.6.1 Data analysis review -- 3.7 Summary -- Chapter 4. Build phase -- 4.1 The project build phase -- 4.2 Build and team work assignment -- 4.2.1 Assigning team members to tasks -- 4.2.2 Tracking progress -- 4.2.3 Regular builds and systematic integration testing.; 4.3 Integrated development and test infrastructure -- 4.3.1 The team development environment -- 4.3.2 The shared test environment -- 4.3.3 Configuring a development process -- 4.3.4 Configuring a simulated production environment -- 4.3.5 Source code management -- 4.3.6 The build process -- 4.3.7 Build and deployment automation -- 4.3.8 Build deployment status -- 4.4 The problem determination process -- 4.4.1 Component installation and configuration -- 4.4.2 Build deployment -- 4.4.3 Runtime problems -- 4.4.4 Application or customization defects -- 4.4.5 Performance problems -- 4.5 Subsystem integration test activity -- 4.6 Handling errors -- 4.6.1 Handling each aspect in a real project -- 4.7 Summary -- Chapter 5. Site test phase -- 5.1 Site testing activities -- 5.1.1 Creating the site testing infrastructure and processes -- 5.1.2 Executing test cases -- 5.2 Functional Verification Test (FVT) -- 5.2.1 Team organization during testing -- 5.3 System Integration Test (SIT) -- 5.4 System Verification Test (SVT) -- 5.5 User Acceptance Test (UAT) -- 5.6 Summary -- Chapter 6. Launch phase -- 6.1 Site deployment and launch activities -- 6.2 Summary -- Part 2 Development and migration best practices -- Chapter 7. Development and migration tools -- 7.1 Development tools -- 7.1.1 Lightweight WebSphere Commerce test environment -- 7.1.2 Full WebSphere Commerce test environment -- 7.1.3 Comparison between the test environments -- 7.1.4 Command line utilities -- 7.2 Migration tools -- 7.2.1 Database migration (migratedb) -- 7.2.2 Encrypted data migration (migrateEncryptedInfo) -- 7.2.3 Instance migration (wcim) -- 7.3 Additional tools -- 7.3.1 Lightweight Object Query System -- 7.3.2 Auto-deploy tool -- 7.3.3 CommerceQA test tool -- Chapter 8. Developing new sites -- 8.1 Basing development on a starter store -- 8.2 Using a separate database server.; 8.3 EJB and data bean best practices -- 8.3.1 Customizing WebSphere Commerce tables -- 8.3.2 Customizing WebSphere Commerce EJBs -- 8.3.3 SQL security considerations -- 8.3.4 Using well-formed ejbCreate constructors -- 8.3.5 Lazy fetch data retrieval -- 8.3.6 Handling database vendor specific code -- 8.3.7 Using session beans -- 8.3.8 Managing concurrent updates -- 8.3.9 Flush remote method -- 8.3.10 Generating primary keys -- 8.4 Best practices for JSP programming -- 8.4.1 Using JSTL in place of Java code -- 8.4.2 Using WebSphere Commerce activation tags -- 8.4.3 Using WebSphere Commerce maps to get request parameters -- 8.4.4 Using StoreErrorDataBean for error handling -- 8.4.5 Using an appropriate includes mechanism -- 8.4.6 Using the JSPF file extension for JSP segments -- 8.4.7 Using the escapeXml attribute to preserve HTML formatting -- 8.4.8 Ensuring XHTML compliance -- 8.4.9 Using CSS to separate layout from content -- 8.4.10 Adding id attributes to links and form elements -- 8.4.11 Invoking controller commands from within a JSP page -- 8.4.12 Using the post method for form submission -- 8.5 Command best practices -- 8.5.1 New command naming and hierarchy -- 8.5.2 Using constants to hold class and method name -- 8.5.3 Command error handling -- 8.5.4 Tracing -- 8.6 General security considerations -- 8.6.1 Access ; control -- 8.6.2 Encrypting sensitive information -- 8.6.3 Protecting sensitive configuration files -- 8.6.4 Protecting sensitive parameters -- 8.6.5 Avoiding default credentials and port numbers -- Chapter 9. Migrating existing sites -- 9.1 Why migrate? -- 9.1.1 Business benefits of new products -- 9.1.2 Business benefits of new capabilities -- 9.1.3 Preparing for end-of-service of your product -- 9.2 Migration strategy considerations -- 9.2.1 Getting help -- 9.2.2 Migrating the different environments -- 9.2.3 Handling complexity.; 9.2.4 Component view -- 9.2.5 Minimizing customizations -- 9.2.6 Performance optimization with dynamic caching -- 9.2.7 Scalability -- 9.2.8 Database cleanup -- 9.2.9 Basing development on starter stores -- 9.2.10 Store archive (SAR) migration -- 9.2.11 Delta migration -- 9.2.12 How custom code impacts the process -- 9.2.13 How database customizations impacts the process -- 9.2.14 Migrating your WebSphere Commerce instance or recreating it -- 9.3 Migration approach considerations -- 9.3.1 Switchover migration -- 9.3.2 Coexistence migration -- 9.3.3 In-place migration -- 9.4 Migration planning -- 9.4.1 Planning activities -- 9.4.2 Gathering migration requirements -- 9.4.3 Planning the migration activities -- 9.4.4 Preparing for migration -- 9.4.5 Migrating the site -- 9.4.6 Testing the migrated site -- 9.4.7 Going live -- 9.5 Planning and sizing templates -- Chapter 10. Integration with existing systems -- 10.1 WebSphere Commerce integration capabilities -- 10.1.1 Messaging architecture -- 10.1.2 Predefined messages -- 10.2 Web services -- 10.2.1 Overview -- 10.2.2 Why use Web services? -- 10.2.3 Web services architecture -- Part 3 Appendixes -- Appendix A. Project team creation and common roles -- Creating the project team -- The core competency strategy -- The holistic strategy -- Guidance for selecting the strategy -- Project roles -- Appendix B. Analysis, site maintenance and enhancement phases -- Analysis phase -- Analysis phase sizing -- Site maintenance and enhancement phase -- Appendix C. Additional methods -- Deciding the method and terminology -- IBM methods -- The Rational® Unified Process® (RUP®) -- Summary -- Related publications -- IBM Redbooks -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.
• Sommario/riassunto: This IBM Redbooks publication is an update to the IBM Redpaper Best Practices and Tools for Creating IBM WebSphere Commerce Sites, REDP-3616. It introduces a systematic project development method that was specifically adapted for the creation of e-commerce sites using the WebSphere Commerce family of software products. This book provides examples on the best practices for developing new sites or migrating existing ones. The objective is to document how the tools can be combined with the systematic development method to streamline a WebSphere Commerce project.