Skip to Content
author's profile photo Former Member
Former Member

Backoffice implementation on a clustered environment

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Nov 24, 2014 at 11:34 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 10, 2014 at 08:37 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 16, 2014 at 04:00 AM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.