This section provides usage explanations and describes how to customize the user interface to facilitate upgrades and merges. The user interface (UI) for ENOVIA V6 applications is defined by a combination of configurable UI components residing in the database and JavaServer Pages (JSPs) packaged in the war file.
Ideally, the entire UI is modeled with configurable UI components using the Business modeling tool. In such a case, configuring the UI consists of simple modifications to the UI components. The results are then dynamically rendered by the system without having to restart the web application server. Since no edits are necessary to JSPs this form of configuration is easier to maintain when installing new releases.
There are cases where a configurable UI component is not available or a particular application has not yet fully migrated to using UI components. In these cases, configuration to the UI may involve editing one or more JSPs. Web application servers can dynamically compile modified JSPs and render the results without having to restart the server. To maintain these modifications across new releases the recommendation is to isolate any modified JSPs by making a copy and renaming them. The system provides a filter mechanism which will automatically render the modified JSPs instead of the original out-of-the-box (OOTB) JSPs.