Before understanding the basic structure Fiori, we first look at several types Fiori APP (mainly has the following three).
1, transactional applications (Transactional APP)
Such as employee travel needs, staff leave demand, create purchase orders, sales orders and other general business creation type operation we can all be achieved through transactional applications. Transactional APP way to start is to tile (Tile), then here's another tile is what is it? Here we see the figure might Fiori main interface, wherein a portion of one of the square it is called "tiles."
Such APP can not only run on HANA database platform that can also run on other database platforms (such as Oracle, SQLServer, etc.).
2, forms applications (Fact-sheet App)
APP such as display information such major supplier contracts, after which point you can go in to see more detailed information, such as details of the supplier, the rise of the contract details, contracts and other project details. Its start-up mode and the above mentioned transactional APP vary by searching Launchpad at the top right or by entering other transactional APP. Such APP operating platform has limitations and can only run on HANA database platform.
3, analytic applications (Analytical App)
Such APP can be used to display real-time information (HANA database) large amounts of data, closely monitor key performance indicators (KPI), it is also a way to start the "tile" and can only be run on HANA database platform.
After understanding the above three mentioned Fiori APP types, it allows us to understand the architecture below said Fiori.
There are usually two ways to deploy SAP Fiori, center deployment (front-end servers and back-end servers separation) and integrated deployment (front-end servers and back-end servers together), here we show that SAP recommended "center deployment" way (full production environment).
First, it will contain a variety of device / client (such as mobile phones, tablets, computers, etc.).
When we issued operational instructions on the "client / browser", it receives a corresponding Http / Https requests to the SAP Web Dispatcher above, it would make a deal with the request, decided to enter these requests APP which server.
Fiori架构里面还包含“前端服务器”，它包含Fiori系统的UI组件，以及NetWeaver gateway，UI组件包含SAPUI5控件库，以及Fiori Launchpad，NetWeaver gateway用于搭建与后台服务器的连接，以及添加后端创建好的Gateway Service。
前端服务器会向后端服务器发出数据处理的请求，包含具体的取数逻辑，另外还包含实施Fact Sheet Apps所需要的Search Model。
当然Fiori架构中也必须包含数据库层，这个数据库可以是一般数据库也可以是HANA内存数据库。
在“后端服务器”和“数据库层”之间会有一个“ABAP CDS”，它是用来将ABAP里面的数据逻辑下推到数据库层，这里的话可以提高APP的运行效率。
上面这一套完整的业务流程就是主要针对“事务型应用”而言的，如果是“表单型应用”呢？它会直接把请求发送到“后端服务器”的“Search Model”上面，由这个“Search Model”直接调用HANA数据库的数据，显示在客户端。
同样的，如果是“分析型应用”的话，它会直接把请求发送到“SAP HANA XS Engine”（HANA扩展应用服务器）上面，它是内置在HANA数据库里面的Web应用服务器，这个服务器是用来运行所有分析型应用的，分析型应用的所有相关开发（包含前端工程、OData服务、控制业务逻辑）都是在这个XS引擎上实现的。
上面所说的就是SAP Fiori的基本架构。
