For Hybris Upgrade, what does "Template extensions are not to be upgraded" mean?

[geffchang]

We are planning to upgrade Hybris from 5.7 to SAP Commerce Cloud 1808. In Upgrading SAP Hybris Commerce, there is a phrase which says "Template extensions are not to be upgraded".

What does "Template extensions" refer to? Are these the y extensions like "yempty" or "ycommercewebservices" under ext-template folder or like "ybackoffice" under ext-backoffice folder?

If yes, does this mean that when I upgrade fro 5.7 to 1808, all my non-y extensions will be from 1808 and my y extensions will be from 5.7. And when I create a new custom extension on Hybris 1808, the custom extension will be based on Hybris 5.7 template. Is this correct?

I think the "Upgrading SAP Hybris Commerce" page is not very clear. An actual example or (many different scenarios) would be useful.

[arvind-kumar_avinash]

All your doubts should be cleared after going through this.

[mpern · Accepted solution]

After reading the page and also the link by , I get your confusion.

IMHO, the documentation linked by Arvind is unfortunately wrong.

I assume you have the following setup:

• Accelerator-based project, properly set up sometime in the past with ant modulegen, so all your extensions are in hybris/bin/custom

• maybe a few more extensions in hybris/bin/custom

• This is crucial: None of your extensions depend on any of the y... template extensions

If the above is true for you, the upgrade boils down to:

1. Unpack new hybris version to have a clean starting point

2. copy your custom extension from your previous version

3. create default config using ant createConfig

4. add custom extensions and necessary dependencies to new localextensions.xml

5. migrate and adapt configuration to new version:

   • local.properties

   • solr configuration -> diff with the new solr configuration, decide what to migrate!

   • customize folder

   • license

   • languages

6. build and fix errors

7. repeat from 5.

If you depend on any of the template extensions, you will have a problem, as the templates evolved quite a lot over time. In that case, I would be pragmatic and run ant extgen on the old installation with the old template, to have a custom version that I than can use with the new hybris version.

[geffchang · Accepted solution]

When you say "depend on any of the y... template extensions", what do you mean by depend? If I have a custom extension that was generated using ant extgen using yempty, is this considered as "depend on any of the y..."? Or does "depend" refer to a custom extension where I define a requires-extension (for yempty) in extensioninfo.xml?

[mpern · Accepted solution]

By "depends on" I mean a extension dependency via requires-extension

[geffchang · Accepted solution]

Thanks for the clarification. In our case, all our custom extensions are generated using ant extgen based on yempty or ycockpit or ybackoffice. We haven't used "ant modulegen". In this case, do we need to use old templates (ytemplate or ybackoffice from 5.7) in our upgraded application (using Hybris 1808)? Assuming that we already have a custom ckoffice from using ybackoffice in 5.7, which template should we use in the upgraded application - from 5.7 or from 1808?

[mpern · Accepted solution]

If you already used ant extgen to generate your code, you will probably have a bunch of custom extension ( hybris/bin/custom/<something>), that do not depend on ( requires-extension) any other y... template extension (correct me if I'm wrong).

And those custom extension you can upgrade as outlined in my original answer, you "make them work" with the target version, 1808.

You do not need to generate new extensions using ant extgen or ant modulegen, just copy the folders to the new version and start fixing build errors.

But of course, it may help to check the new templates for hints ;)