hybris Commerce Trail | internal use only

SAP hybris Commerce | v1.0 | Chapter 1 -SAP Commerce Cloud 1808

HYBRIS COMMERCE TRAIL | INTERNAL USE ONLY PRADEEPIT CONSULTING SERVICE PVT LTD

1

Contents SAP COMMERCE CLOUD 1808 .............................................................................................................. 1

CORE ACCELERATORS ............................................................................................................................ 2

ADDITIONAL ACCELERATORS ................................................................................................................... 2

UPGRADING B2C ACCELERATOR FROM 6.7 TO 1808 ................................................................................ 3

PREREQUISITES ................................................................................................................................. 3

PROCEDURE ..................................................................................................................................... 4

STANDARD UPGRADE STEPS ............................................................................................................... 4

PROCEDURE ................................................................................................................................. 4

RELEASE-SPECIFIC UPGRADE STEPS ...................................................................................................... 5

CONTEXT .................................................................................................................................... 5

ADDITIONAL INFORMATION ................................................................................................................ 5

CUSTOMIZING THE ACCELERATOR WITH EXTGEN AND MODULEGEN ............................................................... 6

CREATING A CUSTOMIZED ACCELERATOR.................................................................................................. 7

SAP Commerce Cloud 1808

SAP Commerce Cloud 1808 includes key enhancements to deliver contextual and real-time

personalization that drives conversion, raises order value and increases customer satisfaction and

loyalty. Further enhancements in this release give more control and flexibility to business users with

SmartEdit for web content management, Adaptive Search, and Promotion management. The Integration

APIs and SAP Cloud Platform Integration introduce a new and simplified way to integrate backend

applications with SAP Commerce Cloud

• Context-Driven Services integration provides real-time customer experience personalization for

SAP Commerce Cloud by capturing and analyzing contextual and behavioral data across each

customer’s commerce journey.



2

• SmartEdit for SAP Experience Management adds content versioning capability that gives more

power to the content managers to track changes made to pages and roll back to previous

versions.

• The new Commerce APIs for consent management, billing, and shipping improve the ability to

decouple Commerce storefronts from the platform and improve user experience.

• Introducing the new integration strategy based on public APIs (using Integration APIs) that

leverages SAP Cloud Platform Integration for master data synchronization and process

integration. SAP Commerce Cloud also offers pre-built integration packages for SAP S/4HANA

and SAP ERP with SAP Cloud Platform Integration.

Core Accelerators

This section contains the release notes for Accelerators that are delivered with this release of SAP Commerce Cloud.

No new features were introduced for the Core Accelerators in SAP Commerce Cloud 1808.

Additional Accelerators

These are the release notes for Accelerators that are delivered separately from SAP Commerce Cloud 1808.



3

The following additional Accelerators are available:

• Financial Services Accelerator

• Telco & Media Accelerator

Upgrading B2C Accelerator from 6.7 to 1808

Perform these steps to upgrade Commerce B2C Accelerator from 6.7 to 1808.

Prerequisites

To upgrade Commerce B2C Accelerator from 6.7 to 1808, you also need to upgrade Commerce

Platform and its dependencies (see Upgrading Platform from 6.7 to 1808).

https://help.hybris.com/1808/hcd/c69e196eb2814bf8aafb353799c76da7.html

https://help.hybris.com/1808/hcd/d99e7e459f4e4bbe8103b157b403e886.html

https://help.hybris.com/1808/hcd/71ce7fccfb3242c09690e8000e6e681f.html#loio71ce7fccfb3242c09690e8000e6e681f



4

Procedure

1. Carry out the standard upgrade steps (see Standard Upgrade Steps).

2. Carry out the release-specific steps (see Release-Specific Upgrade Steps).

3. If you have custom-developed extensions, consult Additional Information for information on

how to upgrade these.

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:

a. Copy <old_version>/hybris/data/media to <new_version>/hybris/data

b. Copy <old_version>/hybris/data/hsqldb to <new_version>/hybris/data

c. Copy <old_version>/hybris/data/solr to <new_version>/hybris/data

d. 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:

o <new_version>/hybris/bin/ext-template

o <new_version>/hybris/bin/ext-data

o <new_version>/hybris/bin/ext-addonNoteThere 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.

3. 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.

a. Copy all the template extensions from <old_version> /hybris/bin/ext-

data to<new_version>/hybris/bin/custom/ext-data

https://help.hybris.com/1808/hcd/bbac567ceb144102b67dffbf9a6616a6.html#loio295418c9fd334b03addce1738eb2f2d7

https://help.hybris.com/1808/hcd/bbac567ceb144102b67dffbf9a6616a6.html#loioe83f0c3670ca45eebca06b0f8e570841

https://help.hybris.com/1808/hcd/bbac567ceb144102b67dffbf9a6616a6.html#loioab6e64b3d1ea4e21a16d8bbb7e1596fe



5

b. Copy all the template extensions from <old_version> /hybris/bin/ext-

template to <new_version>/hybris/bin/custom/ext-template

4. Copy your customized extensions

from <old_version>/hybris/bin/custom to <new_version>/hybris/bin/custom.

5. If your set-up includes the Assisted Service Module, complete the steps described in Upgrading

Assisted Service Module from 6.7 to 1808.

6. Update the code to a compilable state.

For more information, see API, Data Model, and Spring Framework Changes.

7. Run the following command: ant clean all.

8. Run the system update with the following command: ant updatesystem

9. Start your server with the following command: ./hybrisserver.sh.

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:

https://help.hybris.com/1808/hcd/299aed4c6b3141b5947cd916d02251f6.html#loio299aed4c6b3141b5947cd916d02251f6

https://help.hybris.com/1808/hcd/299aed4c6b3141b5947cd916d02251f6.html#loio299aed4c6b3141b5947cd916d02251f6

https://help.hybris.com/1808/hcd/c955fc334bc8483fb5c7ed8fd7caa221.html



6

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

Customizing the Accelerator with extgen and

modulegen

This document describes how to customize the Accelerator using extgen and modulegen.

The modulegen tool is delivered with SAP Commerce and can be used to generate sets of dependent

extensions to quickly start new projects or create new applications. The modules shipped with SAP

Commerce help you to meet client requirements from the very beginning by allowing you to generate

fully functional applications that can then be customized. The modulegen tool replaces the schema,

package name, extension class prefixes, and some other properties across a set of extensions, all while

maintaining the relationships between them. The tool is run as an ant task, so it requires the ant

libraries to be present on the system.

SAP Commerce ships with an extension generator tool called extgen, which is short for extension

generator. Using the extgen tool, you can create new extensions based on extension templates. With

the extgen tool, you can create one new extension using one template extension. The modulegen tool is



7

a wrapper around the extgen tool that allows you to create a set of extensions from a set of template

extensions. From a technical perspective, any extension can be used as a template extension.

The extgen tool is basic in that it simply replaces the tokens configured in a properties file.

Creating a Customized Accelerator

The following procedure describes how to create a customized B2C Accelerator using the B2C

Accelerator installation recipe.

1. Navigate to the <HYBRIS_HOME>/installer directory.

2. Invoke the Installer with the b2c_acc recipe by entering the following command:

o On Windows: install.bat -r b2c_acc

o On Linux or Mac: ./install.sh -r b2c_acc

3. Navigate to the <HYBRIS_BIN_DIR>/platform directory.

4. Set your ant environment by entering the following command:

o On Windows: setantenv.bat

o On Linux or Mac: . ./setantenv.sh



8

5. Run the ant modulegen command and modify the input.name and input.package parameters as

required, for example:

ant modulegen -Dinput.module=accelerator -Dinput.name=training -

Dinput.package=de.hybris.training -Dinput.template=develop

Client Specific Extension

• Client : unieuro

• Country : Italy

• Shop : B2C Accelerator

• Recipe : b2c_acc

• Module : accelerator (B2C without Marketplace - HYBRISCOMM180800P_3-70003534\installer\recipes\b2c_acc) (B2C with Marketplace - HYBRISCOMM180800P_3-70003534\installer\recipes\marketplace_acc )

Examples : B2C – Business to Customer, B2B- Business to Business B2B - https://www.amazonbusiness.in/

B2C- http://amazon.in

https://www.amazonbusiness.in/

http://amazon.in/



9

ant modulegen -Dinput.module=accelerator -Dinput.name=unieuro -

Dinput.package=it.eshop.unieuro -Dinput.template=develop

Where:

o input.module parameter: Configures the modulegen task to use the accelerator module.

o input.name value: Indicates the prefix that is added to the new extensions generated

by modulegen.

o input.package value: Defines the default Java package prefix.



10

o input.template parameter: Defines how to use the default SAP Commerce configuration.

NoteThe training variable can be substituted for any string value.

6. After running the ant modulegen command, open the localextensions.xml file located

in <HYBRIS_HOME>/hybris/config folder.

7. Add the new extensions generated by modulegen to the localextensions.xml file. The exact XML

snippet to add is displayed in your console output. The following is an example:

8. trainingcore

9. trainingfacades

10. trainingstorefront

11. traininginitialdata

12. trainingtest

13. trainingcockpits

trainingfulfilmentprocess

Note

If you include the "trainingtest" extension, it imports test data which can be inaccurate in a real-

world scenario. Only include the "trainingtest" extension if you intend to perform tests with this

accelerator.

14. As instructed in the console output, remove any of the following extensions that might appear

in your localextensions.xml file:

15. yacceleratorcore

16. yacceleratorfacades



11

17. yacceleratorstorefront

18. yacceleratorinitialdata

19. yacceleratortest

20. yacceleratorcockpits

yacceleratorfulfilmentproces

21. Re-install the B2C Accelerator AddOns on the training storefront by running the

following ant command from the <HYBRIS_BIN_DIR>/platform folder:

ant reinstall_addons -Dtarget.storefront=trainingstorefront

22. Add the following properties to <HYBRIS_HOME>/hybris/config/local.properties file:

23. website.electronics.http=http://electronics.local:9001/trainingstorefront

24. website.electronics.https=https://electronics.local:9002/trainingstorefront

25. website.apparel-uk.http=http://apparel-uk.local:9001/trainingstorefront

26. website.apparel-uk.https=https://apparel-uk.local:9002/trainingstorefront

27. website.apparel-de.http=http://apparel-de.local:9001/trainingstorefront

website.apparel-de.https=https://apparel-de.local:9002/trainingstorefront

For b2c_acc_plus recipe, add the following properties:

website.electronics.http=http://electronics.local:9001/trainingstorefront

website.electronics.https=https://electronics.local:9002/trainingstorefront



12

website.apparel-uk.http=http://apparel-uk.local:9001/trainingstorefront

website.apparel-uk.https=https://apparel-uk.local:9002/trainingstorefront

website.apparel-de.http=http://apparel-de.local:9001/trainingstorefront

website.apparel-de.https=https://apparel-de.local:9002/trainingstorefront

piwik.tracker.url.electronics=http\://electronics.local\:9002/trainingstorefront/events

piwik.tracker.https.url.electronics=https\://electronics.local\:9002/trainingstorefront/events

piwik.tracker.url.apparel-uk=http\://apparel-uk.local\:9002/trainingstorefront/events

piwik.tracker.https.url.apparel-uk=https\://apparel-uk.local\:9002/trainingstorefront/events

piwik.tracker.url.apparel-de=http\://apparel-de.local\:9002/trainingstorefront/events

piwik.tracker.https.url.apparel-de=https\://apparel-de.local\:9002/trainingstorefront/events

28. Build and initialize SAP Commerce by running the following ant command from

the <HYBRIS_BIN_DIR>/platform folder:

ant initialize

29. Start the SAP Commerce server by running the following command from

the <HYBRIS_BIN_DIR>/platform folder:

o On Windows: hybrisserver.bat

o On Linux or Mac: ./hybrisserver.sh

Note

For more options on starting and stopping the SAP Commerce server, see Running SAP

Commerce.

https://help.hybris.com/1808/hcd/8bec32dc8669101484b9b1778f6352f1.html

https://help.hybris.com/1808/hcd/8bec32dc8669101484b9b1778f6352f1.html

13

30. Once the server is started, ensure the B2C Accelerator electronics and apparel storefronts are

working by loading the following URLs:

o http://electronics.local:9001/trainingstorefront/

o http://apparel-uk.local:9001/trainingstorefront/

o http://apparel-de.local:9001/trainingstorefront/

For the above URL to work, you must have the following entry in your computer's hosts file:

127.0.0.1 localhost electronics.local apparel-uk.local apparel-de.local



<extension dir="C:\Vinod\Clients\pradeepacademy\fullstackc4hana\HYBRISCOMM180800P_3-

70003534\hybris\bin/custom/unieuro/unieurofulfilmentprocess"/>


70003534\hybris\bin/custom/unieuro/unieurocockpits"/>


70003534\hybris\bin/custom/unieuro/unieurocore"/>


70003534\hybris\bin/custom/unieuro/unieurofacades"/>


70003534\hybris\bin/custom/unieuro/unieurotest"/>


70003534\hybris\bin/custom/unieuro/unieuroinitialdata"/>


70003534\hybris\bin/custom/unieuro/unieurostorefront"/>

hybris Commerce Trail | internal use only

Documents

Transcript of hybris Commerce Trail | internal use only