WebSphere commerce V5.4 catalog design and content management
Autor Corporativo: | |
---|---|
Otros Autores: | |
Formato: | Libro electrónico |
Idioma: | Inglés |
Publicado: |
[S.l.] :
IBM, International Technical Support Organization
2003.
|
Edición: | 1st ed |
Colección: | IBM redbooks.
|
Materias: | |
Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009644317806719 |
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 catalog and content management
- Chapter 1. Introduction
- 1.1 Overview
- 1.1.1 Target audience and prerequisite knowledge
- 1.1.2 Defining asset types
- 1.1.3 Information aggregation, transformation and load
- 1.1.4 Catalog management
- 1.1.5 Content management
- 1.1.6 Catalog data propagation
- 1.1.7 Exchanging data with other systems and industry standards
- 1.1.8 Big picture architecture for catalog and content management
- 1.2 Patterns for e-business
- 1.2.1 Information Aggregation business pattern overview
- 1.2.2 Information Aggregation business general guidelines
- 1.3 Structure of the redbook
- Chapter 2. WebSphere Commerce store and data architecture
- 2.1 WebSphere Commerce store architecture
- 2.1.1 Store assets
- 2.1.2 Store architecture
- 2.1.3 Store models
- 2.1.4 Store packaging
- 2.1.5 Store data assets
- 2.1.6 Tools and store data
- 2.1.7 Customizing a store
- 2.2 Store data architecture
- 2.2.1 Store data architecture overview
- 2.2.2 WebSphere Commerce instance data (site data)
- 2.2.3 Core data
- 2.2.4 Configuration data
- 2.2.5 Managed data
- 2.2.6 Operational data
- Chapter 3. Methods and tools for managing catalog data
- 3.1 WebSphere Commerce Accelerator
- 3.1.1 Overview of the Accelerator for managing catalogs
- 3.1.2 Pros and cons of using the Accelerator
- 3.1.3 Where to find more information
- 3.2 WebSphere Commerce Catalog Manager
- 3.2.1 Overview of Catalog Manager
- 3.2.2 Pros and cons of using the Catalog Manager
- 3.2.3 Where to find more information
- 3.3 WebSphere Commerce catalog commands
- 3.3.1 Catalog commands
- 3.3.2 Where to find more information
- 3.4 WebSphere Commerce search.
- 3.5 IBM MQSeries integration
- 3.5.1 MQSeries runtime implementation
- 3.5.2 MQSeries basic flow
- 3.5.3 MQSeries MQProductCreate example
- 3.5.4 Where to find more information
- 3.6 ISV Partner Solutions
- Chapter 4. WebSphere Commerce and content management
- 4.1 Content management overview
- 4.1.1 What is content?
- 4.1.2 How is content used with WebSphere Commerce?
- 4.1.3 What value does a content management system provide?
- 4.1.4 Content management life cycle
- 4.2 CMS integration with WebSphere Commerce
- 4.2.1 Common integration questions
- 4.2.2 Store archive (SAR) deployment using Stores Services
- 4.2.3 Serving static content using the Web server
- 4.2.4 File system content included in WebSphere Commerce JSPs
- 4.2.5 Database content retrieved from CMS and included in WebSphere Commerce JSPs
- 4.3 Where to find more Information
- Chapter 5. ISV Partner Solutions for catalog and content management
- 5.1 divine Inc. Content Server
- 5.2 A2i xCat
- 5.2.1 A2i xCat value proposition
- 5.2.2 A2i xCat components
- 5.2.3 A2i xCat integration with WebSphere Commerce
- 5.2.4 A2i and IBM contact information
- 5.3 Trigo Product Center for eCommerce
- 5.3.1 Trigo Product Center for eCommerce value proposition
- 5.3.2 Trigo Product Center for eCommerce components
- 5.3.3 Trigo integration with WebSphere Commerce
- 5.3.4 Trigo and IBM contact information
- 5.4 Interwoven TeamSite
- 5.4.1 Interwoven TeamSite components
- 5.4.2 Interwoven TeamSite integration with WebSphere Commerce
- 5.4.3 Where to find more information
- Chapter 6. IBM WebSphere Commerce for Digital Media
- 6.1 Overview and key concepts
- 6.2 Solution components and software packaging
- 6.2.1 Supported operating systems
- 6.2.2 Prerequisite software
- 6.2.3 WebSphere Commerce for Digital Media software components
- 6.3 Features and functionality.
- 6.4 Architecture
- 6.4.1 Components and subsystems
- 6.4.2 Runtime patterns and product mapping
- 6.5 Customization
- 6.5.1 WebSphere Commerce for Digital Media store
- 6.5.2 Customization skills
- 6.5.3 Common customizations
- 6.6 Where to find more information
- Part 2 Architecture, design and development guidelines
- Chapter 7. Catalog architecture and design guidelines
- 7.1 Target audience and skills
- 7.2 XML representation in the catalog
- 7.3 Tools for managing reference identifiers
- 7.3.1 KEYS and SUBKEYS database tables
- 7.3.2 WebSphere Commerce catalog documents and the ID Resolver
- 7.3.3 Enterprise Java Beans and the ECKeyManager class
- 7.4 WebSphere Commerce catalog assets
- 7.4.1 Catalog (CATALOG)
- 7.4.2 Catalog description (CATALOGDSC)
- 7.4.3 Catalog group (CATGROUP)
- 7.4.4 Catalog group attribute (CATGRPATTR_ID)
- 7.4.5 Catalog group description (CATGRPDESC)
- 7.4.6 Catalog catalog group relation (CATTOGRP)
- 7.4.7 Catalog group relation (CATGRPREL)
- 7.4.8 Catalog entry (CATENTRY)
- 7.4.9 Catalog entry attribute (CATENTATTR)
- 7.4.10 Catalog entry description (CATENTDESC)
- 7.4.11 Attribute (ATTRIBUTE)
- 7.4.12 Attribute value (ATTRVALUE)
- 7.4.13 Catalog entry relation (CATENTREL)
- 7.4.14 Catalog group catalog entry relation (CATGPENREL)
- 7.5 Catalog assets and offering assets (prices)
- 7.5.1 Trading position container (TRADEPOSCN)
- 7.5.2 Catalog group trading position relation (CATGRPTPC)
- 7.5.3 Offer (OFFER)
- 7.5.4 Offer description (OFFERDESC)
- 7.5.5 Offer price (OFFERPRICE)
- 7.6 Catalog assets and store assets
- 7.6.1 Store catalog (STORECAT)
- 7.6.2 Store catalog group (STORECGRP)
- 7.6.3 Store catalog entry (STOREENT)
- 7.6.4 Display catalog group relation (DISPCGPREL)
- 7.6.5 Display catalog entry relation (DISPENTREL)
- 7.7 Catalog assets and inventory assets.
- 7.8 Catalog assets and merchandising associations
- 7.8.1 Merchandising association (MASSOC)
- 7.8.2 Merchandising association type (MASSOCTYPE)
- 7.8.3 Related catalog group (MASSOCGPGP)
- 7.8.4 Related catalog entry (MASSOCCECE)
- 7.9 Catalog subsystem controller commands
- 7.9.1 Commands that display catalog assets
- 7.9.2 Commands for catalog objects
- 7.9.3 Commands for catalog groups
- 7.9.4 Commands for catalog entries
- 7.9.5 Commands for offers (prices)
- 7.9.6 Commands for relations
- 7.10 Integrating catalogs with other business systems
- 7.10.1 Integration of reference identifiers
- 7.10.2 Integration of catalog asset management
- Chapter 8. Aggregate and transform data for commerce catalogs
- 8.1 Overview
- 8.2 Aggregating data
- 8.2.1 Design guidelines
- 8.2.2 Aggregating the ITSO data
- 8.3 Converting data
- 8.3.1 Converting the CSV data
- 8.3.2 Transforming XML data
- 8.3.3 Transformation principles
- 8.3.4 Transforming ITSO sample elements: Example 1
- 8.3.5 Transforming ITSO sample elements: Example 2
- 8.3.6 Transformed file sizes
- 8.4 Catalogs and product sets
- 8.4.1 Product sets
- 8.5 Exchanging data with other systems
- 8.5.1 UCCnet
- 8.5.2 UCCnet and WebSphere Commerce
- 8.5.3 RosettaNet
- Chapter 9. Resolving and loading data
- 9.1 Overview
- 9.2 Generating a DTD and schema
- 9.2.1 Extending the commerce database schema
- 9.2.2 The DTDgen tool
- 9.2.3 DTDgen tool connection configuration
- 9.2.4 DTDgen tool source table specification
- 9.2.5 Running the DTDgen tool
- 9.3 Resolving reference numbers
- 9.3.1 Creating and using aliases
- 9.3.2 Methods of resolving reference numbers
- 9.3.3 The ID Resolver tool
- 9.3.4 ID Resolver tool connection configuration
- 9.3.5 Using a properties file to modify resolution technique
- 9.3.6 Optimizing the resolution process.
- 9.3.7 Running the ID Resolver tool
- 9.3.8 Issues with the generated reference numbers
- 9.3.9 Checking the result
- 9.4 Loading data
- 9.4.1 Product Advisor search space synchronization
- 9.4.2 Configuring the MassLoader tool
- 9.4.3 Running the MassLoader tool
- 9.4.4 MassLoader performance considerations
- Chapter 10. Data propagation
- 10.1 WebSphere Commerce staging utilities
- 10.1.1 WebSphere Commerce staging server components
- 10.1.2 How the staging server works
- 10.1.3 Configuring a staging server
- 10.1.4 Examples using staging server commands
- 10.2 Native database data propagation utilities
- Chapter 11. Manage content and catalog data using the divine Inc. Content Server
- 11.1 Introduction
- 11.1.1 Definitions and conventions
- 11.1.2 Target audience
- 11.2 Environment and architecture
- 11.2.1 Staging environment
- 11.2.2 Production environment
- 11.3 Integration features and assumptions
- 11.3.1 Single enterprise application - who is driving?
- 11.3.2 Replicated catalog content
- 11.3.3 Initial load extracted from WebSphere Commerce
- 11.3.4 Content Server holds the master catalog
- 11.3.5 Real-time catalog replication
- 11.3.6 Synchronized reference identifiers
- 11.4 Development tasks
- 11.5 Installing the divine Content Server in a WebSphere Commerce enterprise application
- 11.6 Customizing WebSphere Commerce
- 11.6.1 Developing scripts to deploy commands and views
- 11.6.2 Extracting a catalog from WebSphere Commerce
- 11.6.3 Updating the registry and access control tables
- 11.6.4 Copying class files into WebSphere Commerce
- 11.6.5 Copying JSPs into WebSphere Commerce
- 11.6.6 Restarting the WebSphere Commerce instance
- 11.6.7 WebSphere Commerce JSP template modifications
- 11.6.8 Post-update processing
- 11.7 WebSphere Commerce integration components.
- 11.7.1 ExtractContentServerCatalogCmd.