Home » Upgrading B2C Accelerator from 6.7 to 1808

Upgrading B2C Accelerator from 6.7 to 1808

Standard Upgrade Steps

These upgrade steps are more or less the same between all releases.

Procedure

  1. Copy your existing 6.7 custom files into the 1808 project as follows:
    • Copy <old_version>/hybris/data/media to <new_version>/hybris/data
    • Copy <old_version>/hybris/data/hsqldb to <new_version>/hybris/data
    • Copy <old_version>/hybris/data/solr to <new_version>/hybris/data
    • Copy the localextensions.xml and local.properties files from <old_version>/hybris/config to <new_version>/hybris/config.
  2. Delete all of the 1808 extensions from the following locations:
    • <new_version>/hybris/bin/ext-template
    • <new_version>/hybris/bin/ext-data
    • <new_version>/hybris/bin/ext-addon

Note

There is one exception: do not delete the addonsupport extension from <new_version>/hybris/bin/ext-addon, because this is not a template extension. The addonsupport extension should stay in 1808, instead of being overwritten or copied from 6.7.

  1. Copy all the template extensions from 6.7 to 1808 as follows:
    • Copy all the template extensions from <old_version> /hybris/bin/ext-addon to <new_version> /hybris/bin/custom/ext-addon, except for the addonsupport extension.
    • Copy all the template extensions from <old_version> /hybris/bin/ext-data to <new_version>/hybris/bin/custom/ext-data
    • Copy all the template extensions from <old_version> /hybris/bin/ext-template to <new_version> /hybris/bin/custom/ext-template
  2. Copy your customized extensions from <old_version>/hybris/bin/custom to <new_version>/hybris/bin/custom.
  3. If your set-up includes the Assisted Service Module, complete the steps.
  4. Update the code to a compilable state.
  5. Run the following command: ant clean all.
  6. Run the system update with the following command: ant updatesystem
  7. Start your server with the following command: ./hybrisserver.sh or /hybrisserver.bat.

Release-Specific Upgrade Steps

These upgrade steps are specific to the upgrade to this release and need to be performed for out-of-the-box SAP Commerce functionality to work.

Context

There are no release-specific upgrade steps for upgrading Commerce B2C Accelerator from 6.7 to 1808.

Additional Information

These upgrade steps are intended to assist in the upgrade of custom-developed extensions and do not need to be performed for out-of-the-box SAP Commerce functionality.

If you are using the Sales Organization feature, the OrgUnit traversal paths for the OrgUnitModel item are generated when the system is initialized or updated. This may affect system performance during the initialization or update. It is recommended to turn off the path generation before you initialize or update, and then turn it back on once the initialization or update is completed.

You can turn the traversal path generation off by changing the following property to false in the project.properties file of the commerceservices extension:

commerceservices.org.unit.path.generation.enabled=false

  1. Run the following command: ant clean all.
  2. Run the system update with the following command: ant updatesystem
  3. Start your server with the following command: ./hybrisserver.sh or /hybrisserver.bat.

Release-Specific Upgrade Steps

These upgrade steps are specific to the upgrade to this release and need to be performed for out-of-the-box SAP Commerce functionality to work.

Context

There are no release-specific upgrade steps for upgrading Commerce B2C Accelerator from 6.7 to 1808.

Additional Information

These upgrade steps are intended to assist in the upgrade of custom-developed extensions and do not need to be performed for out-of-the-box SAP Commerce functionality.

If you are using the Sales Organization feature, the OrgUnit traversal paths for the OrgUnitModel item are generated when the system is initialized or updated. This may affect system performance during the initialization or update. It is recommended to turn off the path generation before you initialize or update, and then turn it back on once the initialization or update is completed.

You can turn the traversal path generation off by changing the following property to false in the project.properties file of the commerceservices extension:

commerceservices.org.unit.path.generation.enabled=false
  1. Run the following command: ant clean all.
  2. Run the system update with the following command: ant updatesystem
  3. Start your server with the following command: ./hybrisserver.sh or /hybrisserver.bat.