Components contain a number of artifacts that are used to build an application. All the artifacts in a single component have the same priority in the component order. The artifacts in one component may be used to customize the artifacts in a lower-priority component, or they may be entirely new artifacts that extend the application. The main type of artifacts are as follows:
- UIM Pages
- UIM pages are the principal artifacts of a web client application. Each UIM page describes a web page that users will see when accessing the web client application with their web browsers. The files for these artifacts use the .uim extension.
- UIM Views
- UIM views define portions of a page that may be re-used by many UIM pages. The files for these artifacts use the .vim extension.
- Properties Files
- Properties files store the natural language text for a page separately from the pages, views and page groups. When applications are localized into different languages, there will be a separate properties file for each language (or locale, see Application Locales). This allows a single UIM page, view or page group to be defined for all of the supported languages.
Note: UIM properties files do not support any form of visual layout or formatting capabilities such as using carriage returns or inserting HTML elements.
- Application Configuration Files
- Application configuration files define the layout of the user interface and how UIM pages are grouped into sections and tabs. The files for these artifacts are defined using the extensions .app, .sec, .tab, .nav, .mnu, and .ssp. Note, these files are located in the <server-dir> project. See Application Configuration for details.
- Image Files
- Images file referenced from your UIM pages or views can be added to your component's Images sub-folder. See Images for details.
- Configuration Files
- Configuration files are used to alter the behavior or appearance of the application or of elements of the application. There are a variety of different configuration files that can be used for different purposes.
- Custom Resources
- Custom resources are arbitrary files that you want to deploy with your application. For example, you may want to customize the appearance of a page to reference you own image file for a logo; this image file is a custom resource.