Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Migrating
Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
Migrating WebSphere Commerce Developer
The following section outlines the high-level steps that must be completed to migrate your WebSphere Commerce Version 7.0 Developer environment to WebSphere Commerce Developer Version 8.0. Migrating WebSphere Commerce Developer includes completing the following steps in order.
Migrating custom assets
In this phase of the migration process, you migrate custom assets from WebSphere Commerce Version 7.0 to WebSphere Commerce Version 8.0.
... for WebSphere Commerce Search
If you customized the WebSphere Commerce Search or Search-REST modules in the programming environment, you must identify and reapply the earlier version's changes to the new version.
... from a BOD-based search deployment
Follow this procedure to migrate custom assets from a BOD-based search deployment to the WebSphere Commerce Version 8 REST-based model.
Migrating BOD-based WebSphere Commerce Search customization assets
You can migrate WebSphere Commerce Search customization assets to the REST-based search architecture.
Migrating custom index fields and indexing scripts
Any customization that is made to any of the index schemas, or to the preprocessing and indexing scripts can be reapplied.

User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
- Planning
  Creating a custom implementation of a WebSphere Commerce store requires a significant amount of planning. From gathering client needs, to deploying the live solution, much work is needed to successfully deploy a custom client store. Use the resources in here to help you plan every phase of store creation.
- Installing
  Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
- Migrating
  Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
  - Planning to migrate WebSphere Commerce
    Most businesses treat investments in technology updates and migrations as overhead expenses. Even though you might need to upgrade or migrate to the latest WebSphere Commerce version to take advantage of the technological offering, providing a business justification to do so requires outlining the business benefits, strategy, and migration plan.
  - Migrating WebSphere Commerce Developer
    The following section outlines the high-level steps that must be completed to migrate your WebSphere Commerce Version 7.0 Developer environment to WebSphere Commerce Developer Version 8.0. Migrating WebSphere Commerce Developer includes completing the following steps in order.
    - Preparing WebSphere Commerce Developer Version 7.0 for migration
      To prepare for migration from version 7.0 to version 8.0, commit customized code and published stores to a source control repository and back up the development database.
    - Preparing WebSphere Commerce Developer Version 8.0 for migration
      To migrate from WebSphere Commerce Developer Version 7.0 to WebSphere Commerce Developer Version 8.0, restore your version 7.0 development database to your version 8.0 development environment, and then update the database and its configuration.
    - Migrating the database
      You can migrate your WebSphere Commerce Developer Version 7.0 database to the WebSphere Commerce Developer Version 8.0 level by using either the Migration wizard or the command line.
    - Migrating custom assets
      In this phase of the migration process, you migrate custom assets from WebSphere Commerce Version 7.0 to WebSphere Commerce Version 8.0.
      - ... EJB projects
        Two types of EJB projects can be migrated: independent EJB projects, and dependent EJB projects. Independent EJB projects are projects that were originally created under the WebSphereCommerceServerExtensionsData module. Dependent EJB projects are projects that are built on top of existing projects.
      - ... custom Physical Service Data Objects
        Custom Physical Service Data Objects are migrated automatically when you migrate your WebSphere Commerce Server. However, these objects must be migrated in the development environment by running the Data Service Layer wizard.
      - ... command and data bean projects
        Migrating command and data bean projects involves several steps. The WebSphereCommerceServerExtensionsLogic project must be exported from your old development environment, and imported into WebSphere Commerce Developer Version 8.0 environment.
      - ... Stores dynamic web project
        To migrate your custom Stores project from WebSphere Commerce Version 7.0 to WebSphere Commerce Version 8.0. You need only to migrate custom projects.
      - ... for Accelerator, Administration Console, and Organization Administration Console
        There are no migration tools to migrate any customizations that you made to CommerceAccelerator, SiteAdministration, or OrganizationAdministration. If you customized any of these modules, review the following migration options available to you.
      - Migrating Management Center
        Run the Management Center Migration Utility to migrate your customized version 7.0 Management Center to version 8.0.
      - ... for WebSphere Commerce Search
        If you customized the WebSphere Commerce Search or Search-REST modules in the programming environment, you must identify and reapply the earlier version's changes to the new version.
        ... from a REST-based search deployment
        Follow this procedure to migrate custom assets from a REST-based search deployment to the WebSphere Commerce Version 8 REST-based model.
        ... from a BOD-based search deployment
        Follow this procedure to migrate custom assets from a BOD-based search deployment to the WebSphere Commerce Version 8 REST-based model.
        Importing and deploying previous search assets to the new version
        Your previous search customizations are required to complete some migration tasks in WebSphere Commerce Version 8. Therefore, you must move your search customizations from WebSphere Commerce Version 7 into source control in WebSphere Commerce Version 8.
        Migrating facetable attributes
        If you are migrating from WebSphere Commerce Version 7 Feature Pack 2, 3, or 4, migrate facetable attributes.
        Running the migrate Solr search utility
        Run the migrate Solr search utility to migrate your search index to the new version.
        Merging previous search assets to the new version
        Your previous search customizations must be merged back into WebSphere Commerce Version 8.
        Preprocessing the search index
        Preprocess the search index to ensure that your search index works in the new version.
        Building the search index
        Fully build the search index to ensure that your search index works in the new version.
        Updating your storefront JSP files
        If you are migrating from WebSphere Commerce Version 7 Feature Pack 6 or lower, update your storefront JSP files.
        Indexing price ranges
        Set price ranges to be indexed, so that they are displayed as facets and in advanced search results in the storefront.
        Migrating BOD-based WebSphere Commerce Search customization assets
        You can migrate WebSphere Commerce Search customization assets to the REST-based search architecture.
        Migrating custom index fields and indexing scripts
        Any customization that is made to any of the index schemas, or to the preprocessing and indexing scripts can be reapplied.
        Migrating custom configuration files
        Search-related configuration updates under the WebSphere Commerce EAR application extension directories can be moved into the corresponding extension directories under the WebSphere Commerce search EAR application. For example, the com.ibm.commerce.catalog-ext and com.ibm.commerce.foundation-ext directories.
        Migrating custom Java classes
        You can migrate custom Java classes either by reusing them where applicable, or reimplementing them in an alternative way.
        Migrating storefront services
        Any custom storefront pages that use any of the search-related CatalogNavigationView BOD services must be updated to use the corresponding new search server REST services.
        Mapping between BOD and REST services
        This topic shows the mapping between the search-related CatalogNavigationView BOD expression builders from the WebSphere Commerce server and the corresponding search REST services from the search server.
        Mapping between search profiles
        This topic shows the mapping between the search profiles that are used by the search-related CatalogNavigationView BOD services and the corresponding search profiles that are used by the search REST services from the search server.
        Mapping between search expression providers
        This topic shows the mapping between the search expression providers that are used by the related search CatalogNavigationView BOD services and the corresponding search expression providers that are used by the search REST services from the search server.
        Mapping between search preprocessors
        This topic shows the mapping between the search preprocessors that are used by the related search CatalogNavigationView BOD services and the corresponding search preprocessors that are used by the search REST services from the search server.
        Mapping between search result filters and postprocessors
        A description of the mapping between search result filters that are used by the related search CatalogNavigationView BOD services and the corresponding search postprocessors that are used by the search REST services from the search server.
        Mapping between search mediators and postprocessors
        This topic shows the mapping between the search mediators that are used by the related search CatalogNavigationView BOD services and the corresponding search postprocessors that are used by the search REST services from the search server.
    - Migrating site security for WebSphere Commerce Developer
      If you are migrating from WebSphere Commerce Developer Version 7.0 to WebSphere Commerce Developer Version 8.0, manually migrate your security configurations.
    - Updating the WebSphere Commerce XML configuration files
      Use the configMigration utility to update XML configuration files that were migrated from version 7.0 to version 8.0. The utility upgrades the configuration files while preserving your customizations.
    - Verifying the migrated WebSphere Commerce Developer application
      After you migrate your enterprise bean files into WebSphere Commerce Developer Version 8.0, the final step is to verify the migrated application. To test your migrated application, access a test JSP page in the migrated store as in the previous WebSphere Commerce Developer Version 7.0 development environment.
    - Taking your first steps after migrating WebSphere Commerce Developer
      After you migrate of WebSphere Commerce Developer to version 8.0, complete the following steps.
  - Migrating WebSphere Commerce
    The following section outlines the available migration paths for moving from WebSphere Commerce Version 7.0 to WebSphere Commerce Version 8.0.
- Deploying
  The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.
- Operating
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
- Administering
- Tutorials
  WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
- Samples
- Developing
  The topics in the Developing section describe tasks performed by an application developer.
- Compliance
  The following section describes how you can leverage WebSphere Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of WebSphere Commerce and how to configure these features.
- Performance
- Troubleshooting

Migrating custom index fields and indexing scripts

Any customization that is made to any of the index schemas, or to the preprocessing and indexing scripts can be reapplied.

Procedure

The search index schema and indexing scripts are shared between the WebSphere Commerce server and the WebSphere Commerce Search server, and are therefore compatible with no additional changes.

For example:

All of the following Solr configuration files
All of the index configuration files under WCDE_installdir\components\foundation\samples\dataimport\catalog