In Web Designer, database objects, such as modules, components, or styles, are saved as XML files in the database. They are shown as nodes in a tree structure in the Web Designer definition tree view. Different nodes are labeled with icons to provide a better overview and to distinguish between them more easily.
For more information, see the One Identity Manager Web Designer Object Model Documentation.
Web Portal is a web application. A web application is a published and live website on a web server, which interacts with the One Identity Manager database. For more detailed information, see the Web Portal in the One Identity Manager Web Portal User Guide.
A web application manages web projects and all other database objects. Functions, such as editing or saving colleague or order data are available. A web application is a published web project with its subprojects, if these have been defined.
Each web application has a dedicated intranet or Internet address.
In Web Designer you can define and manage as many web projects as you want. Generally, a web project includes a web application and a web portal. However, the link between the VI_StandardWeb and VI_RegistrationWeb web projects is a special case. These web projects are already in the database and are part of the business workflow. VI_RegistrationWeb becomes a subproject of VI_StandardWeb and must be published separately.
You can view a web project as a web application before publishing it in the Web Designer preview.
A web project is generally made up of modules, components and other database objects. You can add or edit database objects in Web Designer. Modules with and without parameters are linked in the web project.
To assign a web project to a web application that is on the web server, use the web application configuration file. For more detailed information about the web server, see the One Identity Manager Installation Guide.
In every web project there is a set of specific data to be maintained in the definition tree view. For more information, see Definition Tree View.
You can also select another web project as an additional web project. You can update or compile this project on the start page in the same way as the web project VI_StandardWeb. VI_RegistrationWeb is an example of a subproject. Subprojects are required to operate several web projects from within an installed web application. Without subprojects, you would need to install as many web applications as there are web projects. In addition, a subproject enables a part of the web application, for example with different authentications, to control another menu structure or layout.
A module is a logically closed unit within a web project. A module can only contain one web page with a short welcome text (as in the start page) but can also map a comprehensive workflow, which stretches over several web pages (such as, ordering products).
Modules contain at least one form or main page. They can contain components, which are required for defining nodes visible in the browser. This allow the contents of a form node to be rendered in a start-up module or on the browser’s start page if the start page is displayed to the user. The size of the module or number of modules is not limited.
NOTE: A good and structured mapping of a web application’s target functionality in modules, makes any debugging and later implementation of other functions easier.