Uniface Runtime Objects

Uniface runtime objects, or resources, are the compiled application components of a Uniface application. They can include executable components and application shells, runtime libraries of global objects, and component descriptors.

Runtime resources are usually packaged into Uniface archive files (.uar) and executed by the platform-specific Uniface executable or Uniface Server.

These resurces are generated from development objects during compilation. For more information, see Uniface Development Objects.

Runtime Components

Components are platform-independent executable files that have a file extension reflecting the component type:

Uniface Component Types
Component Runtime File Extension Purpose
Dynamic Server Pages .dsp Browser-based user interface component for web applications. It enables users to view, create, and modify data. Data in the component can be partially and dynamically updated. Some processing can be done in the browser using JavaScript.
Static Server Pages .usp Browser-based user interface component for web applications. It only supports updates to the whole page, so it is less interactive than dynamic server pages.
Forms .frm Presentation component for a desktop or mobile application. It is executed locally as a modal or non-modal component and provides the user interface so users can view, create and change data.
Reports .rpt Presentation component used only to print data. It can be run locally or remotely, but it has no user interface and cannot be used to update the database.
Services .svc Business logic component that can be run locally or remotely to provide application processing that does not require user interaction.
Session Services .ssv Business logic component that provides task-specific processing, such as complex calculations or database I/O for multiple entities (database tables).
Entity Services .esv Business logic component for handling data I/O for a single entity (database table).

Runtime Libraries and Global Objects

Runtime libraries hold collections of objects that are used globally across the application, and are resolved in the application at runtime. They can include messages, global ProcScript, and global variables; for desktop applications, they can include menus, panels, drag-and-drop formats, and more.

As the name implies, global objects can be used to provide common, application-wide functionality. Some global objects, such as messages, are language specific. This makes it possible to conditionally switch the language of the application if it is required to run in different locales. For more information, see Global Objects.

Resources for a Web Application

For example, the runtime objects for a web application could include:

  • Dynamic and Static Server Page components for displaying, creating, and modifying data.
  • Service components for calculations, data access, or other data processing that doesn't require user input.
  • JavaScript and CSS files to provide in-browser processing and layout control.
  • Component and data descriptors so components can communicate with each other and with databases (via the Uniface Router, Uniface Server, and database drivers).

Runtime Objects for a Desktop Application

The runtime objects for a desktop client/server application can include:

  • Application shell for starting the application and executing application level menus and processing
  • Form components for the user interface and local processing
  • Report components for printing data output
  • Service components for remote data processing
  • Libraries containing menus, messages, global ProcScript modules
  • Component and data descriptors

Related Topics