# Entando Standard Banking Demo
This tutorial will take you through installing a demonstration application using the Entando Component Repository and a set of Entando bundles. This solution template includes microservices, micro frontends, many pages, and CMS content. The goal of this install is to demonstrate how Entando bundles can be used to quickly install and create functionality in an Entando application, enable portable business capabilities, and can enable developers to re-use full stack functionality via a bundle.
Some of the key elements of the template are reviewed in the application details section below.
- An Entando application on any Kubernetes provider. Follow one of the tutorials for your platform to install the Entando platform
- The ent command line tool installed and connected to your Kubernetes instance.
# Installation Steps
- Apply the definitions for the four bundles that make up the Standard Banking Demo. You'll need to adjust the
-n entandooption in each command to match your namespace or project.
ent bundler from-git -d -r https://github.com/entando-samples/standard-demo-banking-bundle.git | ent kubectl apply -n entando -f -
ent bundler from-git -d -r https://github.com/entando-samples/standard-demo-customer-bundle.git | ent kubectl apply -n entando -f -
ent bundler from-git -d -r https://github.com/entando-samples/standard-demo-manage-users-bundle.git | ent kubectl apply -n entando -f -
ent bundler from-git -d -r https://github.com/entando-samples/standard-demo-content-bundle.git | ent kubectl apply -n entando -f -
Log into your App Builder instance
Select Repository from the menu on the left. Your bundles will be visible in the repository as shown in the screenshot below
Installfor each bundle. The
sd-customer bundleswill take a few minutes since they include microservices that require starting up containers. The
standard-demobundle will need to be installed last since it depends on MFEs from the other bundles in order to set up each of the pages.
You should not see any conflicts in an initial installation but if there are any conflicts you will be presented with an Installation Plan like the one shown below.
Update All in the upper right after making your selections.
- Each installation can take a few minutes as the application downloads the Linux images for the microservices and installs all of the related assets.
(Entando 6.3.2) There is a cache issue when deploying the
sd-content bundle which means not all widgets or MFEs initially appear on some pages, particularly the Dashboard page. Restarting the quickstart-server pod (which holds the Entando App Engine) will clear the cache. This is only necessary on the initial install.
- (Option 1) If you'd like to make the Standard Banking Demo your default home page, go to
App Builder → Pages → Settings. In the dropdown for Home Page select
Home / Home SDand click
You can now navigate to your applications home page using the home icon in the upper right of the app builder to view the application homepage
- (Option 2) Alternatively, you can simply view the Standard Banking Demo home page by going to
Pages → Management, finding
Home SDin the page tree, and clicking
View Published Pagefrom its actions.
There are many assets installed as part of the Standard Banking Demo. Entando Bundles can include many components like the
sd-content bundle or smaller depending on the goals of your team. It is recommended that organizations develop guidelines for bundle sizing that fit the goals of their applications and teams.
# Application Details
The Entando Standard Banking Demo application demonstrates a number of the major features in the Entando platform including:
- Keycloak integration for role based access controls
- Micro frontends implemented using React and Angular and co-existing on the same dashboard page
- Micro front communication techniques
- Microservices run via Spring Boot
- Entando Content Management
# Micro Frontends (MFE)
The application includes six custom micro frontends which are described below.
# 1. Card
- The Card MFE is a React micro frontend that is visible on the My Dashboard page. The MFE makes an API call to the banking microservice to fetch a numeric result depending on the configured card type. The value displayed will change as the configuration is changed.
- The MFE is authorization-aware and will pass the bearer token to the microservice for authorization and authentication. If you render the dashboard page and you aren't authenticated the widget shows an error message.
- This widget emits events that are consumed by the Transaction Table widget.
# 2. Card NG
- The Card NG MFE is an Angular widget that is similar to the Card widget above except for the choice of front end technology.
- This MFE communicates with Transaction Table widget which is implemented in React.
# 3. Manage Users
Not Authorized View
- The Manage Users MFE makes an API call to Entando Identity Management to fetch user information. The MFE is visible under the dropdown under the username when the user is logged into the app.
- By default the users provisioned in the application do not include the authorization required to manage users in
Entando Identity Management. This is used to demonstrate role based access control for an MFE using Keycloak. To
enable the Manage Users widget login to Keycloak and assign the
manage-usersroles from the realm-management client to the desired user.
# 4. Transaction Table
- This MFE is a React micro frontend that consumes events from the Card MFEs detailed above.
- The Transaction Table widget makes an API call to the banking microservice to fetch transaction data for the logged in user.
# 5. Signup
- The Sign Up MFE is a form widget that makes an API call to the customer microservice to create a new user. The Signup MFE is visible on the sign up page and can be accessed from any page when a user is not authenticated.
# 6. Alert Icons
- The Alert Icon MFE displays an icon on the dashboard page and includes a configuration MFE to allow the user to select the appropriate icon and datatype to display.
- The Alert Icon MFE makes an API call to the banking microservice to fetch data in the default deployment.
# Configuration Micro Frontends
Many of the MFEs detailed above include configuration screens visible in the App Builder when the MFE is placed on a page. In the App Builder navigate to
Components → Micro frontends & Widgets to see the configured MFEs. To see the rendered config screen place the MFEs above on a new page.
The application includes two microservices (service paths:
/customer) to support the data visible in the MFEs detailed above. Both microservices demonstrate the automated deployment and linking of a microservice to an Entando application via the Entando operator.
The data for the microservices is created using Liquibase and demonstrates using the operator and Liquibase + Spring Boot to automatically provision data into an environment. The demo data is available in the source code for the microservices on GitHub.
# Static Widgets
images and other content in the application. To view the static widgets log into the App builder and
Components → Micro frontends & Widgets
# Static CMS Content
The application makes extensive use of the Entando CMS. This includes the creation of content templates, content types, and content. If you want to learn more about the Entando CMS in the application log into the App Builder and select
Content → Templates,
Content → Management, or
Content → Types as good starting points to view the content and static assets.
# Source Code
The source for the Entando Standard Banking Demo can be found with our other open source examples and tutorials on GitHub at: