In the previous chapters, you uploaded your modules to the PDS Embedded Server. This is an application server with the LSPS Application already deployed. The server runs on your computer locally and its LSPS Application cannot be modified.
In real-world scenarios, such a solution is obviously not sufficient since it is not possible to cstomize the LSPS Application User Interface: You cannot change its look or implement custom business logic.
To perform such customization, you need to modify the EAR of the LSPS Application and deploy it to a supported application server with the required setting (to set up such an application server, refer to the deployment instructions).
Important: Before you start customizing the Application User Interface, analyze your business processes thoroughly: extract the knowledge into a systematic description with happy flows and all border cases.
To generate the maven archetype of the LSPS Application and related resources, you need LSPS Enterprise Edition with SDK installed: from a PDS with SDK, you can generate your application. The maven archetype of the application along with the SDK Embedded Server, and launch and build configurations will be created and added to your workspace. Note that LSPS Application is a standard enterprise application: To deploy it on a supported application server, all you need to do is to build the application's sole EAR and deploy it to a supported application server as described here.
Using the generated resources, you can do the following:
Create a theme derived from the lsps-valo theme for your Application User Interface. You will need to:
<YOUR_APP>-vaadin-war/src/main/webapp/VAADIN/themes/
.com.eko.ekoapp.vaadin.util.Constants
class and set it as DEFAULT.styles.scss
theme, recompile it with the Sass Compiler run and check the changes in your browser.Typically, you do not want the end user to have access to all their documents and to-dos: remove and add navigation items from the menu as instructed here. You can do much more with your Application User Interface: basic procedures are described in the SDK guide.