- App. page has no content and is used just as application controller
- "Main" page is declared and loaded from manifes based on empty pattern
- Navigation to "Product" page uses "Globals" to read odata path instead of hash
- Navigation to "Product" page requires additional "target" and "pattern" to be declared in manifest. "Pattern" should not be empty, as it is for the "Main" page.
- In case application is being started from "Product" page, router returns to "Main" page
- npm install --global @ui5/cli (To load UI5 tools, like component preload, upload to server and renaming of debug files)
- npm install
- node server.js
- Open url "http://localhost:8005/index.html"
Maintain "connection.json" file:
- "mainPort": defines which port is used to serve static files
- "proxyPort": defines port through which final app is consumed
- "services": proxy searches for entity name ("Northwind" in this case) in "connection.json" and replaces the name with configured path in server request.
Setting different combination of mainPort and proxyPort for different apps will allow you to have multiple instances of applications running at same time.
Optionally: target in connectionJson should point to the same location as datasource uri in manifest.json
-
Design guidelines. Contains general rules. Also allows to select, which element is used in which case.For example, search for element "Switch" and read "Usage" section.