Open UI – Overview, Features and Benefits Part 2
Open UI Posts
- Overview, Features and Benefits #1
- Overview, Features and Benefits #2
- How Open UI processes the user request
Open UI key components
It includes all elements of traditional Siebel Client, plus few Open UI specific components.
- Application Object Manager (AOM)
- Siebel Web Template (SWT) files.
- Cascading Style Sheet (CSS) files.
- anifest files.
- Open UI Client.
- Presentation Model (PM)
- Physical Renderer (PR)
Application Object Manager (AOM)
- This Server component in Open UI behaves exactly the same way like our traditional Siebel.
- Process user requests with the help of other components like Data Manager, Siebel Web Engine.
- For creating new OM component for Open UI, copy any existing Object Manager component and add the above two Open UI specific parameters under that.
- Also do not forget to create new Virtual Directories on Siebel Web Server to support Open UI object manager.
- For Dedicated Client, add the above two parameters in [InfraUIFramework] section of the client .cfg file.
- The only difference is that we need to set the following two parameters for enabling Open UI, under Open UI object manager component for Siebel web client.
- EnableOpenUI = TRUE
- HighInteractivity = TRUE
Siebel Web Template (SWT) Files
- HTML file with Siebel tags, provides empty placeholder for views, applets, controls and other objects of Siebel.
- This SWT files are registered in the Siebel Repository, and each object displayed in UI is mapped to an empty place holder in the web template.
- Open UI uses newer version of SWT files which no longer contain any explicit layout information.
- Original SWT files has explicit tags like tables, boundaries where Open UI SWT files has ‘div’ tag, which allows CSS files to control the layout.
- For Siebel developer web client path is client\WEBTEMPL.
- SWT files are on Siebel server are under \siebsrvr\WEBTEMPL.
- WEBTEMPL folder contains original SWT files.
- OUIWEBTEMPL folder, under WEBTEMPL folder contains Open UI specific SWT files.
- CUSTOM folder, under OUIWEBTEMPL folder contains all custom SWT files.
- Enhance the interactivity features of web pages.
- Extensively used in Open UI to render the application is web browser.
- Oracle provided JS files to deliver Open UI functionalities, customers can also add their own JS files to leverage the functionalities. With Java script, JQuery also can be used.
- For Siebel developer web client, path is Client\<lang>\<build>\SCRIPTS.
- JS files are on Siebel server under \siebsrvr\public\<lang>\<build>\SCRIPTS
- SCRIPTS folder contains original (High Interactivity) JS files.
- Siebel folder, under SCRIPTS folder contains Open UI related vanilla JS files.
- Custom folder, under \SCRIPTS\Siebel folder contains all custom JS files.
- 3rd party folder, under SCRIPTS folder contains all 3rd party provided JS files.
- Traditional browser scripts are separate from JS files that are part of Open UI framework.
- These traditional browser scripts can run side by side with Open UI JS files though it is not recommended by Oracle.
Cascading Style Sheet (CSS) Files
- Style language that defines the layout of web pages, example like font, color, height, width and many more.
- Open UI uses CSS to build layout of HTML files using ‘div’ tag.
- CSS file path on the web server under \Webmaster\files\<lang> and \eappweb\PUBLIC\<lang>\FILES
- CSS file path for the Siebel developer client, path is client\PUBLIC\<lang>\files.
- Benefits of CSS file
- Reusable – One CSS file could be used for multiple web pages.
- Modify style definition in one place and changes will be reflected in all web pages. Easy to build.
- Different layout for different media types like print, mobile and desktop.
Open UI Client
- The Open UI client is an engine which runs within the browser on the client to provide better and enhanced user interface.
- Binds data to presentation layout.
- Caches data locally.
- Applies client side business logic.
Open UI Client Components
- Client proxy
- Presentation Model (PM)
- Physical Renderer (PR)
- Provide the interface to back end Siebel data.
- Get runtime data and metadata from Siebel server whenever required.
- Provided data back to Siebel server.
- Provided by Oracle and must not be modified by customers.
Presentation Model (PM)
- It is a Java script file to handle metadata and runtime data, coming from Siebel server and displays those in applets in the client.
- It determine what logic should be applied.
- It is Client side script without requiring the needs of the Siebel server.
- Captures the client interaction like E.g: Did the user leave the control, Did the user click a link.
- Supports different logic for different platform.
- Collection of
- Properties: Contains information about current state of each user interaction. E.g. Open UI currently shows of hides a field.
- Method: Important characteristic that modifies the state of an object. E.g. If user chooses a field value, then apply method to hide another field.
- Java script file to build the enhanced user interface.
- Can display the same set of records in different ways (like List applet, Carousal, Calendar, Mind Map etc.)
- Supports different behavior for Desktop versus Mobile devise.
- Uses an unique key to determine which java script file/s to download to the client browser.
- From Open UI innovation pack 2013, instead of modifying the manifest file, we will configure it in Open UI client, under Administration-Application Manifest Administration.
- Earlier version Open UI innovation pack 2013 (22.214.171.124) has three manifest files under \siebsrvr\OBJECTS.
- Core_manifest.xml : As delivered listing of JS files and should not be modified by customers.
- Custom_manifest.xml : Specifies key name and java script file mappings.
- Manifest_extensions.map: place to register Applet\key combination.
ActiveX Vs Open UI Architecture