Creating Multiple storefronts in Hybris

0
votes

Hybris Version used: 6.5

Current Scenario We have an implementation that has the following implemented

  1. SAP to Hybris connector (datahub) (manage customers, products, prices, stock levels)

  2. One storefront ( product, carts)

  3. Integration with payment system

Everything works fine .

The questions:

  1. Ability to create multiple new storefronts (apart from the main one) on the fly => event based storefronts that stay online for a pre-defined period and then shut down(based on some rule/trigger)
  2. Reuse the SAP to Hybris connector from above(to manage products, prices, stock levels etc).
  3. Reuse the integration with payment system from above.
  4. The main storefront operates as usual

Is this functionality supported in Hybris? If yes, how is it achieved? What needs to be done? Any suggestions?

2
hybris
I reformatted your question so that the layout can be more easily read. Also, I removed the "thanks" and signature, which are not allowed. – Bob Dalgleish

2 Answers

1
votes

You can create multiple CMSSite without development, details are in this answer.
If there are static context/url exist in design or code, you need to make changes on code. For example payment callback url.
If you plan to split products by site, maybe you need changes on datahub for using separate product catalog.

1
votes

Possible solutions-

  1. New storefronts-

    You can create multiple storefronts in a project just the same way you create a new extension using extegen. Select default template as yacceleratorstorefront. If multiple controller methods have same URL and type (GET, POST, etc.) then add the annotation @RequestMappingOverride on top of the method in your main storefront. You need to do this ONLY if you want to implement different business logic for same URL and type. To shutdown a storefront you have to remove the storefront entry from localextensions.xml and run the build before starting server. There is no way to do this on the fly.

  2. Reuse the SAP to Hybris connector-

    Product, prices and stock levels are saved in the databse. These values can be used by different CMSSite and different storefronts without any extra customization.

  3. Reuse payment integration system-

    A popular way of doing this is creating a dedicated addon for each payment type using a common payment addon template. Eg- cybersourcepaymentaddon, paypaladdon, etc.

Each storefront will operate independently.