on 05-19-2022 9:35 PM
Upgrade from V6.4 to V2105 On public Cloud
Doing some SOLR testing, we discovered that we can not run the backoffice solr index, we get errors.
I did some research, and it looks like we are missing a few extensions. So I organized and added them:
<!-- modules/search-and-navigation -->
<extension name='solrfacetsearchbackoffice' />
<extension name='solrserver' />
<extension name='solrfacetsearch' />
<extension name='backofficesolrsearch' />
<!-- modules/search-services -->
<extension name='backofficesearchservices' />
<extension name='searchbackoffice' />
<extension name='searchprovidercssearchbackoffice' />
<extension name='searchprovidercssearchservices' />
<extension name='searchservices' />
I then followed the instructions found here: Configuring Commerce Update Parameters
I did a new deployment, and then when I go to open up backoffice I get the following errors:
Failed to render widget [id='quickToggleLocale', definitionId='com.hybris.cockpitng.widgets.common.quickToggleLocale', message='type code 'BackofficeIndexedTypeToSolrFacetSearchConfig' invalid']
Cloud not execute searchThis item. BackofficeIndexedTypeToSolrFacetSearchConfig is supposed to be created from backofficesolrsearch, but it is not getting created.Am I incorrect in adding these extensions so that SOLR search works for the backoffice? Any upgrade guidance that one can point me to address these issues.Have you tried searching for this item type under Backoffice -> System -> Types? If it does not appear in the list, then most likely the backofficesolrsearch extension is not loaded. This can be checked in hac.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can see in HAC backofficesolrsearch extension - so this appears that it has been loaded.
Now when I access backoffice, I get the following error: Failed to render widget [id='quickToggleLocale', definitionId='com.hybris.cockpitng.widgets.common.quickToggleLocale', message='type code 'BackofficeIndexedTypeToSolrFacetSearchConfig' invalid']
This prevents me from accessing any menu option in backoffice.
Looking in the log file I see
com.hybris.backoffice.widgets.advancedsearch.AdvancedSearchController
type code 'BackofficeIndexedTypeToSolrFacetSearchConfig' invalid
no composed type with code BackofficeIndexedTypeToSolrFacetSearchConfig found.
de.hybris.platform.persistence.EJBItemNotFoundException
It seems that things are centered around the fact that when dong cloud deployments that the items.xml is not being read and loaded.
But, so far my search of the code base has turned up nothing of where this is defined.
Now I am questioning if I am going down some rabbit hole
Hi David,
I do remember adding missing backofficesolrsearch extension during an upgrade to 2105. It is definitely not required to add solrserver extension because a solr instance is automatically provisioned by SAP Commerce Cloud. You will still need solrserver extension for your local development. If you still want to keep it in the localextensions.xml file and use this file for local as well as Cloud deployment, you can add "exclude" element to the manifest.json file to exclude solrserver extension from becoming active in the Cloud.
Things to try to resolve the error related to BackofficeIndexedTypeToSolrFacetSearchConfig:
I hope that help.
Regards,
Viktor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for you assistance here -
So following the above steps and running the .impex files located on the backofficesolrsearch extension - still run into the issue in which the item: BackofficeIndexedTypeToSolrFacetSearchConfig item is not created.
Short of doing an init on my systme - which would be bad - as we are in production - I am not sure as to how to get this item type created.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.