I’ve been working on an agile development framework to improve the development and deployment agility for Hybris Backoffice functions, such as data management and reporting. I am happy with the progress so far, and excited to share the results with you. In this article, I will introduce the HybrisArchitect.com Dashboard (HAD) for SAP Hybris Commerce.
A Little Background
Before commencing on the HAD development journey, I established several key objectives for this platform.
- Enable agile development: Code may be modified in real-time on the server, if necessary, without a build to deploy changes
- Reduce startup time to less than ten seconds
- Minimal memory footprint
- Mobile responsive design – ability to manage Hybris Commerce storefronts from mobile devices
- Enhanced data entry capabilities in comparison to Hybris Backoffice
- Create a UI theme-able design architecture that enables complete UI design flexibility
HybrisArchitect.com Dashboard Architecture
HAD uses Groovy’s SimpleTemplateEngine as its template engine, and calls Hybris Commerce’s facades and services directly in the same manner as Java Spring beans. As a result, HAD provides a powerful, yet lightweight, development environment.
With this architecture, the development teams are are able to quickly build applications that leverage Hybris Commerce's services. All code modifications are real-time, and picked up by the HAD embedded Tomcat server immediately!
HybrisArchitect.com Dashboard Orders View
With the HAD Orders View, the end user is able to quickly search, view and modify orders from any Hybris Commerce implementation. The grid itself is an AngularJS data grid.
HybrisArchitect.com Dashboard Configuration Readiness View
The following screenshot contains the deployment readiness report using HAD, which verifies the "readiness" of your local.properties file for production usage. The Readiness Evaluation report scans the local.properties for performance, security and configuration best practices.
The following screenshot displays the readiness Groovy controller that drives the HAD Readiness Evaluation Report.
The following displays the client-side AngularJS code leveraging Groovy's SimpleTemplateEngine used for the HAD Readiness Evaluation Report.
HybrisArchitect.com Dashboard Results
As I mentioned in the opening paragraph, I am pleased with HAD's progress. The following are several of the HAD's benefits:
- A decoupled front-end from Hybris core and custom code
- Starts up in less than eight seconds
- Possible to develop serverless applications
- Reduced the monolithic nature of existing Hybris Commerce
- Ability to deploy new code without Hybris builds
- Code changes are available immediately
- Works great on mobile devices
- No external dependencies
If I learned anything from building the HybrisArchitect.com Dashboard, it’s quite possible to rapidly develop and deploy applications on top of Hybris Commerce, and SAP Hybris Commerce licensees shouldn’t settle for less. With HAD, Hybris development teams will be able to develop applications that rival the development speed found mainly in interpreted-based digital commerce platforms, such as Magento. After reading this article, I hope you are curious to try the HybrisArchitect.com Dashboard for your Hybris reporting and data management activities. If you are interested in learning more about the HybrisArchitect.com Dashboard, please reach out to me at firstname.lastname@example.org for licensing details. As in regards to next steps, I will be releasing a series of HAD development tutorials.