Backoffice implementation on a clustered environment

[Former Member]

Hello,

We are running hybris 5.0.2 on a clustered environment.

We have configured certain components (e.g. the listview component by specifying the columns that we want) in the appropriate *-backoffice-config.xml file.

We first start the servers up and all seems fine.

After a short period of time (approx 5 minutes) the configuration resets and our custom implementation of the components (e.g. listview) is replaced with the default. We then click the 'Reset to Defaults' link in the Application Orchestrator and our implementation is restored.

We then notice that we lose our configuration again after about 5 minutes and the above observation is repeated.

We have noticed that when this is run in a single node implementation, we do not experience this issue.

Is this a known issue and is there a solution or approach we should take when implementing the backoffice application in a clustered environment?

Kind regards,

Aman

[Former Member]

Hi Aman,

We're facing the same issue in clustered environment. Did you get the solution for this one?

Thanks, Sandeep

[former_member578868]

@Sandeep & @Aman: We are experiencing the same issue on Hybris 5.4 . Did you find any solution for this?

Thanks Vinil

[former_member981644]

Hi, The same issue on Hybris 5.7. Did you guys find any solution?

[former_member721892]

Hi, We are experiencing the same issue with SAP version 2005.4. If your problem was resolved could you please help me here.

Thanks!!

[ravinder_pasula]

@khusboo shukla ... This is a known limitation.

You need to use sticky session in a clustered environment for Backoffice to work correctly as such Backoffice does not support the session failover mechanism

For further details see this 2005 help document

[Former Member]

there is a backoffice configuration file replication issue in cluster env. According to our support colleague:

We suggest to provide all changes only on one node then copy configuration file to another one. Files which must be copy : backoffice-widgets.xml, backoffice-config.xml placed in hybris-commerce-suite-5.2.0.2/hybris/bin/ext-backoffice/backoffice/resources directory. If you use your custom backoffice extension then the path will look like : hybris-commerce-suite-5.2.0.2/hybris/bin/custom/mycustombackoffice/resources

maintenance ticket has been raised to fix this issue in future patch release.

[former_member578868]

Can you comment in which version of Hybris we can expect it to be fixed? It persists even in Hybris 5.4

https://answers.sap.com/questions/12753758/backoffice-view-disappearing-in-hybris.html

[former_member632755]

Hi,

the most important is the change in com.hybris.cockpitng.util.CockpitUIFactory to extend the SerializableUiFactory that enforces using only Serializable objects within the session. Therefore for example LoginInformationConfigData had to be changed – you will easily figure out; the application will not work without appropriate changes related to Serialziable ojects stored in the session.

The rest of the changes in the mentioned jira tasks (PATCH-1671) seems not that important – for example you may totally disable and skip the tests.

Unfortunately most of the changes cannot be easily implemented in projects so it would be better to request a backport.

Cheers, Wojtek

[former_member632755]

Hi,

there was a significant change in version 5.3 (backported to 5.2.0.1) in regards to serializable sessions for clustered environments.

We would have to know the details of your set up to try to reporduce it, nevertheless my suggestion would be to migrate to the highest possible version since it is very likely that the issues are resolved by the fix I mentioned.

If you have no possibiulity to upgrade I would recommend creating a ticket at support@hybris.com to obtain a workaround and/or to request a backport.

Cheers, Wojtek

[rudolf_castelino]

Since we are going live soon, porting the code to the latest version of hybris is not an option unfortunately.

Is it possible for you to give some information on what code items we need to look at in hybris 5.3 to help with the resolution of the issue?