Open UI key components

It includes all elements of traditional Siebel Client, plus few Open UI specific components.

1. Application Object Manager (AOM)
2. Siebel Web Template (SWT) files.
3. JavaScript (JS) files.
4. Cascading Style Sheet (CSS) files.
5. anifest files.
6. Open UI Client.

• Proxy
• Presentation Model (PM)
• Physical Renderer (PR)

Application Object Manager (AOM)

1. This Server component in Open UI behaves exactly the same way like our traditional Siebel.
2. Process user requests with the help of other components like Data Manager, Siebel Web Engine.
3. 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.
4. Also do not forget to create new Virtual Directories on Siebel Web Server to support Open UI object manager.
5. For Dedicated Client, add the above two parameters in [InfraUIFramework] section of the client .cfg file.
6. 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

1. HTML file with Siebel tags, provides empty placeholder for views, applets, controls and other objects of Siebel.
2. 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.
3. Open UI uses newer version of SWT files which no longer contain any explicit layout information.
4. 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.
5. For Siebel developer web client path is client\WEBTEMPL.
6. 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.

JavaScript (JS) Files

1. Enhance the interactivity features of web pages.
2. Extensively used in Open UI to render the application is web browser.
3. 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.
4. For Siebel developer web client, path is Client\<lang>\<build>\SCRIPTS.
5. 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.

Note

1. Traditional browser scripts are separate from JS files that are part of Open UI framework.
2. 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

1. Style language that defines the layout of web pages, example like font, color, height, width and many more.
2. Open UI uses CSS to build layout of HTML files using ‘div’ tag.
3. CSS file path on the web server under \Webmaster\files\<lang> and \eappweb\PUBLIC\<lang>\FILES
4. CSS file path for the Siebel developer client, path is client\PUBLIC\<lang>\files.
5. 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

1. 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

1. Client proxy
2. Presentation Model (PM)
3. Physical Renderer (PR)

Client Proxy

1. Provide the interface to back end Siebel data.
2. Get runtime data and metadata from Siebel server whenever required.
3. Provided data back to Siebel server.
4. Provided by Oracle and must not be modified by customers.

Presentation Model (PM)

1. It is a Java script file to handle metadata and runtime data, coming from Siebel server and displays those in applets in the client.
2. It determine what logic should be applied.
3. It is Client side script without requiring the needs of the Siebel server.
4. Captures the client interaction like E.g: Did the user leave the control, Did the user click a link.
5. Supports different logic for different platform.
6. 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.

Physical Renderer

1. Java script file to build the enhanced user interface.
2. Can display the same set of records in different ways (like List applet, Carousal, Calendar, Mind Map etc.)
3. Supports different behavior for Desktop versus Mobile devise.

Manifest File

1. Uses an unique key to determine which java script file/s to download to the client browser.
2. 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.
3. Earlier version Open UI innovation pack 2013 (8.1.1.11) 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