Quick start with Hybris Development

In the Hybris if you need to change the style you need to deal with .less files. .less file need to compile to .css then only you can see the changes applied to your storefront. Generally, hybris build (ant clean all) will take care of .less compilation. But if you are frequently dealing with .less files and you want to build it without restarting/building the platform. You can use the below ant command. 1) Open another CMD/Terminal at your platform directory (you don't need to stop your current running server) 2) Now set ant environment using  setantenv.bat 3) Compile your storefront ant <yourstorefrontextension>_compileuisrc     e.g. ant mystorefront_compileuisrc

  1) By navigating to folder/file You can check the hybris build information (Version) in  build.number  file located at hybris\bin\platform. You will find something like this below. #Ant properties #Tue Oct 06 14:59:00 CEST 2020 builddate=20201006 1444 releasedate=20201006 1444 vendor=hybris version=1811.28 version.api=1811 You can refer to  version  &  version.api  property for the Hybris version. 2) From HAC You can search the above version property from the HAC console. Go to HAC > Platform > Configuration. Now search with "verison"

In Hybris, all authentication and authorization configuration is stored in the security.json file. A sample security.json file is provided which contains the following users: below are the default usernames and passwords for Solr User Password Description solradmin admin123 admin user can perform any operation solrserver server123 for communication between server nodes solrclient client123 can perform search queries Read more about Solr Security

What is PartOf? PartOf modifier is used to define the aggregation relationship between Parent and Child objects. To explain it better I would say PartOf is used to defining cascade delete.  When we delete a Parent object then all its child objects(partOf) will be deleted automatically. Why or When to use PartOf? PartOf may make sense when the relationship involves "is part of" description. For example, an OrderEntry record(AbstractOrderEntry) is part of its parent Order(AbstractOrder), and older entries will never be shared between multiple orders. If the Order were to vanish, the OrderEntry should as well, and an order entry without an Order would be a problem. How to use PartOf? On the removal of an order, if we want to remove all associated order entries automatically, then we can define partOf in its relation like <relation code="AbstractOrder2AbstractOrderEntry" localized="false" generate="true" autocreate="true&qu