WebSphere Commerce V5.5 handbook customization and deployment guide
This IBM Redbooks publication provides IT architects, IT specialists, and developers with the critical knowledge to design, develop, implement, deploy, and manage a WebSphere Commerce V5.5 runtime environment and store. This book includes the following: Introduction to the WebSphere Commerce runtime...
Autor Corporativo: | |
---|---|
Otros Autores: | |
Formato: | Libro electrónico |
Idioma: | Inglés |
Publicado: |
[S.l.] :
IBM, International Technical Support Organization
c2003.
|
Edición: | 1st ed |
Colección: | IBM redbooks.
|
Materias: | |
Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626916206719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Introduction to WebSphere Commerce V5.5
- Chapter 1. Introduction
- 1.1 Platform support and product packaging
- 1.1.1 Supported platforms
- 1.1.2 IBM WebSphere Commerce V5.5 product editions
- 1.1.3 IBM WebSphere Commerce Studio V5.5 product editions
- 1.2 Features and benefits
- 1.2.1 IBM WebSphere Commerce V5.5, Professional Edition
- 1.2.2 IBM WebSphere Commerce V5.5, Business Edition
- 1.3 Target audience of this IBM Redbook
- 1.3.1 Roles and skills
- 1.3.2 Matching topics in this redbook to roles and skills
- 1.4 For more information
- 1.4.1 IBM WebSphere Commerce product documentation
- 1.4.2 Web sites
- 1.4.3 IBM Redbooks
- Chapter 2. Runtime architecture
- 2.1 Overview
- 2.2 WebSphere Commerce software components
- 2.2.1 Web server
- 2.2.2 WebSphere Application Server
- 2.2.3 Database Server
- 2.2.4 WebSphere Commerce Server
- 2.2.5 WebSphere Commerce Payments Server
- 2.2.6 Enablement software
- 2.3 WebSphere Commerce Server subsystems
- 2.3.1 Member subsystem
- 2.3.2 Catalog subsystem
- 2.3.3 Trading subsystem
- 2.3.4 Order subsystem
- 2.3.5 Merchandising subsystem
- 2.3.6 Marketing subsystem
- 2.3.7 Inventory subsystem
- 2.3.8 Messaging subsystem
- 2.4 Runtime topology selection
- 2.4.1 Runtime topology selection criteria
- 2.4.2 WebSphere Commerce runtime topologies
- 2.4.3 Topology mapping to implementation details
- 2.5 For more information
- Chapter 3. Business and store models
- 3.1 Business and store models
- 3.1.1 Direct sales
- 3.1.2 Hosting
- 3.1.3 Value chains
- 3.2 Business model infrastructure and architecture
- 3.2.1 Organization structure
- 3.2.2 Access control model
- 3.2.3 Business policy framework.
- 3.3 Store architecture
- 3.3.1 Store assets
- 3.3.2 Store architecture
- 3.3.3 Store packaging and models
- 3.3.4 Store data assets and architecture
- 3.3.5 Catalog data assets and concepts
- 3.3.6 Tools and store data
- 3.3.7 Customize a store
- 3.3.8 Publish a store
- 3.4 For more information
- Chapter 4. Programming model
- 4.1 Overview
- 4.2 WebSphere Commerce Server framework
- 4.2.1 Servlet engine
- 4.2.2 Protocol Listeners
- 4.2.3 Adapter manager
- 4.2.4 Adapters
- 4.2.5 Web controller
- 4.2.6 Commands
- 4.2.7 Entity beans
- 4.2.8 Data beans
- 4.2.9 Data Bean Manager
- 4.2.10 JavaServer Page (JSP) templates
- 4.2.11 WebSphere Commerce <
- instance>
- .xml configuration file
- 4.3 Application flow of an HTTP request
- 4.4 Design patterns
- 4.4.1 Model-view-controller design pattern
- 4.4.2 Command design pattern
- 4.4.3 Display design pattern
- 4.5 Persistent object model
- 4.6 Access control
- 4.7 Customizing application assets
- 4.7.1 Asset types to customize and development tooling
- 4.7.2 Matching skills to customization needs
- 4.8 For more information
- Chapter 5. Site and store administration
- 5.1 Administration tools
- 5.1.1 WebSphere Commerce Configuration Manager
- 5.1.2 WebSphere Commerce Administration Console
- 5.1.3 WebSphere Commerce Accelerator
- 5.1.4 WebSphere Commerce Organization Administration Console
- 5.1.5 WebSphere Commerce Loader Package
- 5.1.6 WebSphere Commerce Scheduler
- 5.1.7 WebSphere Commerce Payments Console
- 5.1.8 WebSphere Application Server Administration Console
- 5.1.9 DB2 Control Center
- 5.2 Key operational categories to manage
- 5.3 IT specialist roles and tools
- 5.3.1 System administrator
- 5.3.2 Site administrator
- 5.3.3 Store administrator
- 5.3.4 Database administrator
- 5.4 Line-of-business user roles and tools.
- 5.4.1 Business relationship roles
- 5.4.2 Customer service roles
- 5.4.3 Marketing manager role
- 5.4.4 Operational roles
- 5.4.5 Organizational management roles
- 5.4.6 Product management and merchandising roles
- 5.5 For more information
- Part 2 Development guidelines
- Chapter 6. WebSphere Commerce site development methodology
- 6.1 Systematic development methodology
- 6.2 Definitions
- 6.2.1 Phase
- 6.2.2 Work products
- 6.2.3 Deliverable
- 6.2.4 Customer
- 6.2.5 Customer IT team
- 6.2.6 Project team
- 6.2.7 Project database
- 6.2.8 Task
- 6.2.9 Strategy
- 6.3 Development methodology: phase and life cycle
- 6.3.1 Core development phases
- 6.4 Using the methodology
- 6.4.1 Customizing and adopting the methodology
- 6.4.2 New and transition sites
- 6.4.3 Project roles and skills requirements
- 6.4.4 Structuring information
- 6.4.5 Case studies
- 6.5 Related methodology concepts
- 6.5.1 IBM Method
- 6.5.2 Rational Unified Process® (RUP®)
- 6.6 Summary
- Chapter 7. Development environment and build cycle
- 7.1 WebSphere Commerce Studio overview
- 7.1.1 WebSphere Commerce Studio workspace
- 7.1.2 WebSphere Commerce Studio plug-ins
- 7.1.3 Custom code packaging and incremental deployment
- 7.2 Team development environment overview
- 7.2.1 Optimistic team model
- 7.2.2 Ideal work flow
- 7.2.3 Source control management
- 7.2.4 Defect tracking
- 7.3 Build environment overview
- 7.3.1 Benefits of daily build and smoke tests
- 7.3.2 Concepts of daily build and smoke tests
- 7.3.3 Build automation for daily builds and smoke tests
- 7.4 Deployment overview
- 7.4.1 Development environment
- 7.4.2 Test environment
- 7.4.3 Staging environment
- 7.4.4 Production environment
- 7.4.5 Practice deployment and create backup plan
- 7.4.6 Production debug vs development debugging
- Chapter 8. Globalization guidelines.
- 8.1 Introduction to globalization
- 8.2 Globalization in WebSphere Commerce
- 8.3 Cultural considerations
- 8.3.1 Date and time formatting
- 8.3.2 Currency and number formatting
- 8.3.3 Name and address formatting
- 8.4 WebSphere Commerce application model
- 8.4.1 Language table
- 8.4.2 Introduction to encoding
- 8.4.3 Unicode
- 8.4.4 WebSphere Commerce data model: input
- 8.4.5 WebSphere Commerce data model: output
- 8.5 Globalized catalog content
- 8.6 Globalized store design
- 8.6.1 Globalized page framework: one template for stores/languages
- 8.6.2 Support for bi-directional languages
- 8.6.3 Understanding the localized store assets
- 8.6.4 Creating a new display format for WebSphere Commerce
- 8.6.5 Adding a new currency to WebSphere Commerce
- 8.6.6 How to add/delete a language/currency for a store archive
- 8.7 Globalized tools framework
- 8.8 Globalization in the messaging system
- 8.9 Globalization tips
- 8.9.1 Handling apostrophes and special characters
- 8.9.2 Using locale-dependent Cascading Style Sheets (CSS)
- 8.9.3 National language-enabled alert/confirm/prompt boxes
- 8.9.4 Input field validation: UTF-8 Input validation
- 8.9.5 Submit NL command parameters using hidden forms
- Part 3 ITSO B2B working example
- Chapter 9. Requirements analysis and solution design
- 9.1 Business scenario
- 9.2 Requirements analysis
- 9.2.1 ITSO challenges and requirements
- 9.2.2 Initial context
- 9.2.3 System context
- 9.2.4 Use case model
- 9.3 Solution design
- 9.3.1 Systems architecture
- 9.3.2 Component model
- 9.3.3 ITSO store navigation
- 9.3.4 ITSO store catalog hierarchy
- 9.3.5 ITSO store organizational hierarchy
- Chapter 10. ITSO sample code
- 10.1 Description of sample code
- 10.2 Prepare DeployTool files
- 10.2.1 Copy WebSphere Commerce files
- 10.2.2 Copy WebSphere Application Server files.
- 10.2.3 Copy WebSphere Commerce Studio files
- Chapter 11. Implement a team development environment
- 11.1 Team development environment scenario
- 11.2 Build and SCM node implementation
- 11.2.1 CVS overview
- 11.2.2 CVSNT Server implementation
- 11.2.3 WebSphere Commerce Studio installation
- 11.2.4 Publish store archive within WebSphere Test Environment
- 11.2.5 CVS client configuration
- 11.3 Development node implementation
- 11.3.1 WebSphere Commerce Studio installation
- 11.3.2 CVS client configuration
- 11.4 Development Integration Test node implementation
- Chapter 12. Create a store
- 12.1 Overview
- 12.2 Package and verify store archive
- 12.2.1 Back up workspace and databases
- 12.2.2 Create the Packaging project
- 12.2.3 Package a store archive (SAR)
- 12.2.4 Publish the store archive (SAR)
- 12.2.5 Verify the store after publish
- 12.3 Import store assets into CVS
- 12.3.1 Create a CVS module from the project
- 12.3.2 Add the files to CVS
- 12.4 Required customization of basic store assets
- 12.4.1 Store directory and identifier
- 12.4.2 Hardcoded references
- 12.4.3 Store address
- 12.4.4 Catalog data
- 12.4.5 Store front-end assets
- 12.5 Further customization of basic store assets
- 12.5.1 Default and supported currencies
- 12.5.2 Default and supported locales
- 12.5.3 Organizations
- 12.5.4 Business accounts
- 12.5.5 Contracts
- 12.5.6 Taxes, shipping couriers and shipping prices
- 12.5.7 Payment information
- 12.6 Publish the store archive to the workspace
- 12.6.1 Package the customized store archive
- 12.6.2 Publish the customized store archive to runtime
- 12.6.3 Verify the customized store archive
- 12.6.4 Publish the store archive to the workspace
- 12.6.5 Verify customized store in the WebSphere Test Environment
- 12.7 Add the store front files to CVS.
- 12.8 Set up additional team development nodes.