40
1 Best Practices: Deployment Guide for Siebel Open UI, HI and SI clients: Document 1499842.1 February 18, 2013 Holger Herbert, Siebel CRM Oracle

Siebel Open UI Best Practices - Deployment Guide v1.34h

Embed Size (px)

Citation preview

Page 1: Siebel Open UI Best Practices - Deployment Guide v1.34h

1

Best Practices Deployment Guide for Siebel Open UI HI and SI clients Document 14998421

February 18 2013

Holger Herbert Siebel CRM

Oracle

2

Table of Contents Revision History 5

Overview 6

User Experience 6

Modern Design 6

New Look and Feel Setting End User Preferences 7

Deployment and Integration 7

Deployment amp Integration Features 7

True standards based Web Based client 8

High-Level Migration Tasks 8

User Experience Providing a Highly Optimized User Experience through Design 9

Development Configuration and extension of the UI 9

Summary 9

Features and Roadmap of Siebel Open UI 9

Features Enabled in Siebel Open UI 9

Feature Roadmap for Open UI 13

Standard Interactivity Client (SI) Roadmap for Open UI 16

Deployment Characteristics 16

Siebel Open UI Client Security 16

Siebel Open UI Server Side Memory Footprint for Clients 17

Siebel Open UI Client-Server Communication 17

Siebel Open UI Client Performance 18

JavaScript Framework 18

Best Practices Tuning customized applications for virtual screen space 18

Siebel Open UI Accessibility 19

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA 19

Accessibility features 19

Screen Reader Support 20

Accessibility Implementation 20

3

Siebel CRM Releases Supporting Siebel Open UI 21

Client Requirements 21

Open UI Browser Standards Conformance Requirements 21

Use of Popup Blockers 22

Open UI Browser Performance 22

Si Client UI Requirements 23

HI Client UI Requirements 23

Installation 24

Choosing a UI for Siebel CRM 24

Mitigating Deployment Risks 25

Overview High Level Installation steps 25

Installing Open UI and Siebel Mobile 25

Installing Siebel HI Web Client and Client Topics related to Open UI 26

Installation of SI Web Client and Client Topics related to Open UI 26

Configuration 26

Overview High level configuration steps 26

Configuration of Open UI 27

Importing Application Configuration (SIF files) 27

Adding Siebel Open UI Object Managers 28

Enabling and Disabling Open UI on clients 28

Backing up configuration and setting Environment variables 29

Adding Virtual Directories for Siebel Open UI 29

Enabling Accessibility for an Object Manager or Mobile Web Client 29

Performance tuning for Siebel Open UI 29

Migrating SRF and SWT files 30

Migrating browser scripting 30

Behavior of SI Views inside RIA Mode 30

Portal Integration 31

Configuration of Siebel Mobile 32

Configuration Options for SI Portal Customers 32

Configuration of HI Web Client and Client Topics related to Open UI 32

Developing in Open UI 32

4

Customizations in Open UI 33

Development and Support Impact of Open UI Customization 34

Siebel Tools 34

The Public JavaScript API 34

Migrating Existing COM Integration 34

CSS Changes 35

CODE suggestions Examples templates 35

Reference Information 35

Other Resources 35

Data Sheets 35

Siebel Bookshelf 35

Standards supported by Siebel CRM Open UI 35

Capabilities of Siebel CRMOpen UI 36

Common Criteria Certification Evaluation Assessment Level 2 36

Portal Standards 36

FIPS-140-2 standard 37

Open Web Application Security Project (OWASP) 37

Oracle Software Security Assurance (OSSA) guidelines and policies 37

Payment Card Industry Data Security Standard (PCI-DSS) 37

Accessibility and VPAT 37

VPAT information 37

EU privacy directives 37

Infrastructure Capabilities 38

IPV6 38

Lightweight Directory Access Protocol and Active Directory Services Interfaces 38

SAML and Single Sign-On 38

Third-Party products in Open UI 39

5

Revision History Version Change

134h Revision history added User experience topic Table captions

134i Feature table Siebel Tools Requirements performance topic

134j Added COM integration section updated SI section Updated Table12 and features amp Roadmap section

134h Tables and Open UI features section intro paragraph

6

Overview To respond to the need for broad support of clients and devices to ease deployment and to improve

the user experience for end users Oracle will be providing a new standards based open client Open UI

uses a single framework to meet the demand for a variety of use cases

Oraclersquos Open UI client was delivered in December of 2012 with Siebel Innovation Pack 2012 It will work

on any modern browser and will be easy to deploy for employee and partner-facing rich internet

applications (RIAs) providing a more modern alternative to high-interactivity (HI) applications

User Experience Users continue to leverage the familiarity gained through prior Siebel versions but supplement usability

from modern JavaScript consumer applications used by roughly 60 of all leading web based

applications Many aspects of the UI have been redesigned to bring new highly intuitive features to the

client

Modern Design

bull Device Driven Layout for tabs forms and other UI elements to match the browserdevice form factor

bull Left Hand or Tab Navigation personalization option bull Fully accessible without configuration bull Native browser integration for Browser history Printprint preview Call email via hyperlink Zoom

Find bull New personalization options for Left handtab navigation and themes

Figure 1 Modern user experience on any device

7

bull Modern Controls bull Grid with ability to support forms bull Map Integration ability (requires configuration)

bull URL Integration ability bull Date and time fields bull Can be used keyboard only or tablet only bull WAI-ARIA Navigation model bull Calculator bull Lists aamp Forms with image support bull Multiple file uploaddownload Control bull Analogous Pick lists and MVGrsquos bull New Menus and toolbars bull Calendar

bull New Look and Feel bull SmartScript bull Task Based UI bull Customer Order Management

bull Native Features

bull Browser history management

bull Print and print preview

bull Zoom

bull Search

bull Save Page

bull Development features

bull Ability to Extend Siebel UI using standard web development techniques

New Look and Feel Setting End User Preferences

Open UI provides new user preferences under Tools Preferences and then Behavior Users can set left-

hand navigation or tabbed UI options as well as setting themes for the UI

Deployment and Integration The age of the plug-in is rapidly coming to a close Flash Silverlight ActiveX and to some degree Java

(for UI use) are reduced in use because they do not run on all mobile devices and create deployment

and security concerns With the release of Windows 8 Microsoft will not fully support ActiveX

The new client will provide true Web-based client deployment To log in users must have a URL and

credentials There will be no requirement for browser configuration

Deployment amp Integration Features

bull Supports full extension of the presentation model and physical renderer to meet any CRM use case bull Application Focus State management capabilities bull Full branding capabilities bull Hierarchical embeddable Presentation Model bull Partial refresh

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 2: Siebel Open UI Best Practices - Deployment Guide v1.34h

2

Table of Contents Revision History 5

Overview 6

User Experience 6

Modern Design 6

New Look and Feel Setting End User Preferences 7

Deployment and Integration 7

Deployment amp Integration Features 7

True standards based Web Based client 8

High-Level Migration Tasks 8

User Experience Providing a Highly Optimized User Experience through Design 9

Development Configuration and extension of the UI 9

Summary 9

Features and Roadmap of Siebel Open UI 9

Features Enabled in Siebel Open UI 9

Feature Roadmap for Open UI 13

Standard Interactivity Client (SI) Roadmap for Open UI 16

Deployment Characteristics 16

Siebel Open UI Client Security 16

Siebel Open UI Server Side Memory Footprint for Clients 17

Siebel Open UI Client-Server Communication 17

Siebel Open UI Client Performance 18

JavaScript Framework 18

Best Practices Tuning customized applications for virtual screen space 18

Siebel Open UI Accessibility 19

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA 19

Accessibility features 19

Screen Reader Support 20

Accessibility Implementation 20

3

Siebel CRM Releases Supporting Siebel Open UI 21

Client Requirements 21

Open UI Browser Standards Conformance Requirements 21

Use of Popup Blockers 22

Open UI Browser Performance 22

Si Client UI Requirements 23

HI Client UI Requirements 23

Installation 24

Choosing a UI for Siebel CRM 24

Mitigating Deployment Risks 25

Overview High Level Installation steps 25

Installing Open UI and Siebel Mobile 25

Installing Siebel HI Web Client and Client Topics related to Open UI 26

Installation of SI Web Client and Client Topics related to Open UI 26

Configuration 26

Overview High level configuration steps 26

Configuration of Open UI 27

Importing Application Configuration (SIF files) 27

Adding Siebel Open UI Object Managers 28

Enabling and Disabling Open UI on clients 28

Backing up configuration and setting Environment variables 29

Adding Virtual Directories for Siebel Open UI 29

Enabling Accessibility for an Object Manager or Mobile Web Client 29

Performance tuning for Siebel Open UI 29

Migrating SRF and SWT files 30

Migrating browser scripting 30

Behavior of SI Views inside RIA Mode 30

Portal Integration 31

Configuration of Siebel Mobile 32

Configuration Options for SI Portal Customers 32

Configuration of HI Web Client and Client Topics related to Open UI 32

Developing in Open UI 32

4

Customizations in Open UI 33

Development and Support Impact of Open UI Customization 34

Siebel Tools 34

The Public JavaScript API 34

Migrating Existing COM Integration 34

CSS Changes 35

CODE suggestions Examples templates 35

Reference Information 35

Other Resources 35

Data Sheets 35

Siebel Bookshelf 35

Standards supported by Siebel CRM Open UI 35

Capabilities of Siebel CRMOpen UI 36

Common Criteria Certification Evaluation Assessment Level 2 36

Portal Standards 36

FIPS-140-2 standard 37

Open Web Application Security Project (OWASP) 37

Oracle Software Security Assurance (OSSA) guidelines and policies 37

Payment Card Industry Data Security Standard (PCI-DSS) 37

Accessibility and VPAT 37

VPAT information 37

EU privacy directives 37

Infrastructure Capabilities 38

IPV6 38

Lightweight Directory Access Protocol and Active Directory Services Interfaces 38

SAML and Single Sign-On 38

Third-Party products in Open UI 39

5

Revision History Version Change

134h Revision history added User experience topic Table captions

134i Feature table Siebel Tools Requirements performance topic

134j Added COM integration section updated SI section Updated Table12 and features amp Roadmap section

134h Tables and Open UI features section intro paragraph

6

Overview To respond to the need for broad support of clients and devices to ease deployment and to improve

the user experience for end users Oracle will be providing a new standards based open client Open UI

uses a single framework to meet the demand for a variety of use cases

Oraclersquos Open UI client was delivered in December of 2012 with Siebel Innovation Pack 2012 It will work

on any modern browser and will be easy to deploy for employee and partner-facing rich internet

applications (RIAs) providing a more modern alternative to high-interactivity (HI) applications

User Experience Users continue to leverage the familiarity gained through prior Siebel versions but supplement usability

from modern JavaScript consumer applications used by roughly 60 of all leading web based

applications Many aspects of the UI have been redesigned to bring new highly intuitive features to the

client

Modern Design

bull Device Driven Layout for tabs forms and other UI elements to match the browserdevice form factor

bull Left Hand or Tab Navigation personalization option bull Fully accessible without configuration bull Native browser integration for Browser history Printprint preview Call email via hyperlink Zoom

Find bull New personalization options for Left handtab navigation and themes

Figure 1 Modern user experience on any device

7

bull Modern Controls bull Grid with ability to support forms bull Map Integration ability (requires configuration)

bull URL Integration ability bull Date and time fields bull Can be used keyboard only or tablet only bull WAI-ARIA Navigation model bull Calculator bull Lists aamp Forms with image support bull Multiple file uploaddownload Control bull Analogous Pick lists and MVGrsquos bull New Menus and toolbars bull Calendar

bull New Look and Feel bull SmartScript bull Task Based UI bull Customer Order Management

bull Native Features

bull Browser history management

bull Print and print preview

bull Zoom

bull Search

bull Save Page

bull Development features

bull Ability to Extend Siebel UI using standard web development techniques

New Look and Feel Setting End User Preferences

Open UI provides new user preferences under Tools Preferences and then Behavior Users can set left-

hand navigation or tabbed UI options as well as setting themes for the UI

Deployment and Integration The age of the plug-in is rapidly coming to a close Flash Silverlight ActiveX and to some degree Java

(for UI use) are reduced in use because they do not run on all mobile devices and create deployment

and security concerns With the release of Windows 8 Microsoft will not fully support ActiveX

The new client will provide true Web-based client deployment To log in users must have a URL and

credentials There will be no requirement for browser configuration

Deployment amp Integration Features

bull Supports full extension of the presentation model and physical renderer to meet any CRM use case bull Application Focus State management capabilities bull Full branding capabilities bull Hierarchical embeddable Presentation Model bull Partial refresh

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 3: Siebel Open UI Best Practices - Deployment Guide v1.34h

3

Siebel CRM Releases Supporting Siebel Open UI 21

Client Requirements 21

Open UI Browser Standards Conformance Requirements 21

Use of Popup Blockers 22

Open UI Browser Performance 22

Si Client UI Requirements 23

HI Client UI Requirements 23

Installation 24

Choosing a UI for Siebel CRM 24

Mitigating Deployment Risks 25

Overview High Level Installation steps 25

Installing Open UI and Siebel Mobile 25

Installing Siebel HI Web Client and Client Topics related to Open UI 26

Installation of SI Web Client and Client Topics related to Open UI 26

Configuration 26

Overview High level configuration steps 26

Configuration of Open UI 27

Importing Application Configuration (SIF files) 27

Adding Siebel Open UI Object Managers 28

Enabling and Disabling Open UI on clients 28

Backing up configuration and setting Environment variables 29

Adding Virtual Directories for Siebel Open UI 29

Enabling Accessibility for an Object Manager or Mobile Web Client 29

Performance tuning for Siebel Open UI 29

Migrating SRF and SWT files 30

Migrating browser scripting 30

Behavior of SI Views inside RIA Mode 30

Portal Integration 31

Configuration of Siebel Mobile 32

Configuration Options for SI Portal Customers 32

Configuration of HI Web Client and Client Topics related to Open UI 32

Developing in Open UI 32

4

Customizations in Open UI 33

Development and Support Impact of Open UI Customization 34

Siebel Tools 34

The Public JavaScript API 34

Migrating Existing COM Integration 34

CSS Changes 35

CODE suggestions Examples templates 35

Reference Information 35

Other Resources 35

Data Sheets 35

Siebel Bookshelf 35

Standards supported by Siebel CRM Open UI 35

Capabilities of Siebel CRMOpen UI 36

Common Criteria Certification Evaluation Assessment Level 2 36

Portal Standards 36

FIPS-140-2 standard 37

Open Web Application Security Project (OWASP) 37

Oracle Software Security Assurance (OSSA) guidelines and policies 37

Payment Card Industry Data Security Standard (PCI-DSS) 37

Accessibility and VPAT 37

VPAT information 37

EU privacy directives 37

Infrastructure Capabilities 38

IPV6 38

Lightweight Directory Access Protocol and Active Directory Services Interfaces 38

SAML and Single Sign-On 38

Third-Party products in Open UI 39

5

Revision History Version Change

134h Revision history added User experience topic Table captions

134i Feature table Siebel Tools Requirements performance topic

134j Added COM integration section updated SI section Updated Table12 and features amp Roadmap section

134h Tables and Open UI features section intro paragraph

6

Overview To respond to the need for broad support of clients and devices to ease deployment and to improve

the user experience for end users Oracle will be providing a new standards based open client Open UI

uses a single framework to meet the demand for a variety of use cases

Oraclersquos Open UI client was delivered in December of 2012 with Siebel Innovation Pack 2012 It will work

on any modern browser and will be easy to deploy for employee and partner-facing rich internet

applications (RIAs) providing a more modern alternative to high-interactivity (HI) applications

User Experience Users continue to leverage the familiarity gained through prior Siebel versions but supplement usability

from modern JavaScript consumer applications used by roughly 60 of all leading web based

applications Many aspects of the UI have been redesigned to bring new highly intuitive features to the

client

Modern Design

bull Device Driven Layout for tabs forms and other UI elements to match the browserdevice form factor

bull Left Hand or Tab Navigation personalization option bull Fully accessible without configuration bull Native browser integration for Browser history Printprint preview Call email via hyperlink Zoom

Find bull New personalization options for Left handtab navigation and themes

Figure 1 Modern user experience on any device

7

bull Modern Controls bull Grid with ability to support forms bull Map Integration ability (requires configuration)

bull URL Integration ability bull Date and time fields bull Can be used keyboard only or tablet only bull WAI-ARIA Navigation model bull Calculator bull Lists aamp Forms with image support bull Multiple file uploaddownload Control bull Analogous Pick lists and MVGrsquos bull New Menus and toolbars bull Calendar

bull New Look and Feel bull SmartScript bull Task Based UI bull Customer Order Management

bull Native Features

bull Browser history management

bull Print and print preview

bull Zoom

bull Search

bull Save Page

bull Development features

bull Ability to Extend Siebel UI using standard web development techniques

New Look and Feel Setting End User Preferences

Open UI provides new user preferences under Tools Preferences and then Behavior Users can set left-

hand navigation or tabbed UI options as well as setting themes for the UI

Deployment and Integration The age of the plug-in is rapidly coming to a close Flash Silverlight ActiveX and to some degree Java

(for UI use) are reduced in use because they do not run on all mobile devices and create deployment

and security concerns With the release of Windows 8 Microsoft will not fully support ActiveX

The new client will provide true Web-based client deployment To log in users must have a URL and

credentials There will be no requirement for browser configuration

Deployment amp Integration Features

bull Supports full extension of the presentation model and physical renderer to meet any CRM use case bull Application Focus State management capabilities bull Full branding capabilities bull Hierarchical embeddable Presentation Model bull Partial refresh

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 4: Siebel Open UI Best Practices - Deployment Guide v1.34h

4

Customizations in Open UI 33

Development and Support Impact of Open UI Customization 34

Siebel Tools 34

The Public JavaScript API 34

Migrating Existing COM Integration 34

CSS Changes 35

CODE suggestions Examples templates 35

Reference Information 35

Other Resources 35

Data Sheets 35

Siebel Bookshelf 35

Standards supported by Siebel CRM Open UI 35

Capabilities of Siebel CRMOpen UI 36

Common Criteria Certification Evaluation Assessment Level 2 36

Portal Standards 36

FIPS-140-2 standard 37

Open Web Application Security Project (OWASP) 37

Oracle Software Security Assurance (OSSA) guidelines and policies 37

Payment Card Industry Data Security Standard (PCI-DSS) 37

Accessibility and VPAT 37

VPAT information 37

EU privacy directives 37

Infrastructure Capabilities 38

IPV6 38

Lightweight Directory Access Protocol and Active Directory Services Interfaces 38

SAML and Single Sign-On 38

Third-Party products in Open UI 39

5

Revision History Version Change

134h Revision history added User experience topic Table captions

134i Feature table Siebel Tools Requirements performance topic

134j Added COM integration section updated SI section Updated Table12 and features amp Roadmap section

134h Tables and Open UI features section intro paragraph

6

Overview To respond to the need for broad support of clients and devices to ease deployment and to improve

the user experience for end users Oracle will be providing a new standards based open client Open UI

uses a single framework to meet the demand for a variety of use cases

Oraclersquos Open UI client was delivered in December of 2012 with Siebel Innovation Pack 2012 It will work

on any modern browser and will be easy to deploy for employee and partner-facing rich internet

applications (RIAs) providing a more modern alternative to high-interactivity (HI) applications

User Experience Users continue to leverage the familiarity gained through prior Siebel versions but supplement usability

from modern JavaScript consumer applications used by roughly 60 of all leading web based

applications Many aspects of the UI have been redesigned to bring new highly intuitive features to the

client

Modern Design

bull Device Driven Layout for tabs forms and other UI elements to match the browserdevice form factor

bull Left Hand or Tab Navigation personalization option bull Fully accessible without configuration bull Native browser integration for Browser history Printprint preview Call email via hyperlink Zoom

Find bull New personalization options for Left handtab navigation and themes

Figure 1 Modern user experience on any device

7

bull Modern Controls bull Grid with ability to support forms bull Map Integration ability (requires configuration)

bull URL Integration ability bull Date and time fields bull Can be used keyboard only or tablet only bull WAI-ARIA Navigation model bull Calculator bull Lists aamp Forms with image support bull Multiple file uploaddownload Control bull Analogous Pick lists and MVGrsquos bull New Menus and toolbars bull Calendar

bull New Look and Feel bull SmartScript bull Task Based UI bull Customer Order Management

bull Native Features

bull Browser history management

bull Print and print preview

bull Zoom

bull Search

bull Save Page

bull Development features

bull Ability to Extend Siebel UI using standard web development techniques

New Look and Feel Setting End User Preferences

Open UI provides new user preferences under Tools Preferences and then Behavior Users can set left-

hand navigation or tabbed UI options as well as setting themes for the UI

Deployment and Integration The age of the plug-in is rapidly coming to a close Flash Silverlight ActiveX and to some degree Java

(for UI use) are reduced in use because they do not run on all mobile devices and create deployment

and security concerns With the release of Windows 8 Microsoft will not fully support ActiveX

The new client will provide true Web-based client deployment To log in users must have a URL and

credentials There will be no requirement for browser configuration

Deployment amp Integration Features

bull Supports full extension of the presentation model and physical renderer to meet any CRM use case bull Application Focus State management capabilities bull Full branding capabilities bull Hierarchical embeddable Presentation Model bull Partial refresh

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 5: Siebel Open UI Best Practices - Deployment Guide v1.34h

5

Revision History Version Change

134h Revision history added User experience topic Table captions

134i Feature table Siebel Tools Requirements performance topic

134j Added COM integration section updated SI section Updated Table12 and features amp Roadmap section

134h Tables and Open UI features section intro paragraph

6

Overview To respond to the need for broad support of clients and devices to ease deployment and to improve

the user experience for end users Oracle will be providing a new standards based open client Open UI

uses a single framework to meet the demand for a variety of use cases

Oraclersquos Open UI client was delivered in December of 2012 with Siebel Innovation Pack 2012 It will work

on any modern browser and will be easy to deploy for employee and partner-facing rich internet

applications (RIAs) providing a more modern alternative to high-interactivity (HI) applications

User Experience Users continue to leverage the familiarity gained through prior Siebel versions but supplement usability

from modern JavaScript consumer applications used by roughly 60 of all leading web based

applications Many aspects of the UI have been redesigned to bring new highly intuitive features to the

client

Modern Design

bull Device Driven Layout for tabs forms and other UI elements to match the browserdevice form factor

bull Left Hand or Tab Navigation personalization option bull Fully accessible without configuration bull Native browser integration for Browser history Printprint preview Call email via hyperlink Zoom

Find bull New personalization options for Left handtab navigation and themes

Figure 1 Modern user experience on any device

7

bull Modern Controls bull Grid with ability to support forms bull Map Integration ability (requires configuration)

bull URL Integration ability bull Date and time fields bull Can be used keyboard only or tablet only bull WAI-ARIA Navigation model bull Calculator bull Lists aamp Forms with image support bull Multiple file uploaddownload Control bull Analogous Pick lists and MVGrsquos bull New Menus and toolbars bull Calendar

bull New Look and Feel bull SmartScript bull Task Based UI bull Customer Order Management

bull Native Features

bull Browser history management

bull Print and print preview

bull Zoom

bull Search

bull Save Page

bull Development features

bull Ability to Extend Siebel UI using standard web development techniques

New Look and Feel Setting End User Preferences

Open UI provides new user preferences under Tools Preferences and then Behavior Users can set left-

hand navigation or tabbed UI options as well as setting themes for the UI

Deployment and Integration The age of the plug-in is rapidly coming to a close Flash Silverlight ActiveX and to some degree Java

(for UI use) are reduced in use because they do not run on all mobile devices and create deployment

and security concerns With the release of Windows 8 Microsoft will not fully support ActiveX

The new client will provide true Web-based client deployment To log in users must have a URL and

credentials There will be no requirement for browser configuration

Deployment amp Integration Features

bull Supports full extension of the presentation model and physical renderer to meet any CRM use case bull Application Focus State management capabilities bull Full branding capabilities bull Hierarchical embeddable Presentation Model bull Partial refresh

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 6: Siebel Open UI Best Practices - Deployment Guide v1.34h

6

Overview To respond to the need for broad support of clients and devices to ease deployment and to improve

the user experience for end users Oracle will be providing a new standards based open client Open UI

uses a single framework to meet the demand for a variety of use cases

Oraclersquos Open UI client was delivered in December of 2012 with Siebel Innovation Pack 2012 It will work

on any modern browser and will be easy to deploy for employee and partner-facing rich internet

applications (RIAs) providing a more modern alternative to high-interactivity (HI) applications

User Experience Users continue to leverage the familiarity gained through prior Siebel versions but supplement usability

from modern JavaScript consumer applications used by roughly 60 of all leading web based

applications Many aspects of the UI have been redesigned to bring new highly intuitive features to the

client

Modern Design

bull Device Driven Layout for tabs forms and other UI elements to match the browserdevice form factor

bull Left Hand or Tab Navigation personalization option bull Fully accessible without configuration bull Native browser integration for Browser history Printprint preview Call email via hyperlink Zoom

Find bull New personalization options for Left handtab navigation and themes

Figure 1 Modern user experience on any device

7

bull Modern Controls bull Grid with ability to support forms bull Map Integration ability (requires configuration)

bull URL Integration ability bull Date and time fields bull Can be used keyboard only or tablet only bull WAI-ARIA Navigation model bull Calculator bull Lists aamp Forms with image support bull Multiple file uploaddownload Control bull Analogous Pick lists and MVGrsquos bull New Menus and toolbars bull Calendar

bull New Look and Feel bull SmartScript bull Task Based UI bull Customer Order Management

bull Native Features

bull Browser history management

bull Print and print preview

bull Zoom

bull Search

bull Save Page

bull Development features

bull Ability to Extend Siebel UI using standard web development techniques

New Look and Feel Setting End User Preferences

Open UI provides new user preferences under Tools Preferences and then Behavior Users can set left-

hand navigation or tabbed UI options as well as setting themes for the UI

Deployment and Integration The age of the plug-in is rapidly coming to a close Flash Silverlight ActiveX and to some degree Java

(for UI use) are reduced in use because they do not run on all mobile devices and create deployment

and security concerns With the release of Windows 8 Microsoft will not fully support ActiveX

The new client will provide true Web-based client deployment To log in users must have a URL and

credentials There will be no requirement for browser configuration

Deployment amp Integration Features

bull Supports full extension of the presentation model and physical renderer to meet any CRM use case bull Application Focus State management capabilities bull Full branding capabilities bull Hierarchical embeddable Presentation Model bull Partial refresh

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 7: Siebel Open UI Best Practices - Deployment Guide v1.34h

7

bull Modern Controls bull Grid with ability to support forms bull Map Integration ability (requires configuration)

bull URL Integration ability bull Date and time fields bull Can be used keyboard only or tablet only bull WAI-ARIA Navigation model bull Calculator bull Lists aamp Forms with image support bull Multiple file uploaddownload Control bull Analogous Pick lists and MVGrsquos bull New Menus and toolbars bull Calendar

bull New Look and Feel bull SmartScript bull Task Based UI bull Customer Order Management

bull Native Features

bull Browser history management

bull Print and print preview

bull Zoom

bull Search

bull Save Page

bull Development features

bull Ability to Extend Siebel UI using standard web development techniques

New Look and Feel Setting End User Preferences

Open UI provides new user preferences under Tools Preferences and then Behavior Users can set left-

hand navigation or tabbed UI options as well as setting themes for the UI

Deployment and Integration The age of the plug-in is rapidly coming to a close Flash Silverlight ActiveX and to some degree Java

(for UI use) are reduced in use because they do not run on all mobile devices and create deployment

and security concerns With the release of Windows 8 Microsoft will not fully support ActiveX

The new client will provide true Web-based client deployment To log in users must have a URL and

credentials There will be no requirement for browser configuration

Deployment amp Integration Features

bull Supports full extension of the presentation model and physical renderer to meet any CRM use case bull Application Focus State management capabilities bull Full branding capabilities bull Hierarchical embeddable Presentation Model bull Partial refresh

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 8: Siebel Open UI Best Practices - Deployment Guide v1.34h

8

bull iframe based portal integrations bull Full support for Siebel Remote and Mobile web client deployments

True standards based Web Based client

bull URL amp Credentials only bull HTML 4 ndashminimum requirement bull HTML5 - optional bull CSS21 CSS30 bull JavaScript (Standard ECMA-262 conformant)

The latest versions of Internet Explorer such as Internet Explorer 910 Google Chrome and Mozilla

Firefox are fully supported via standards This platform supports Android and IOS platforms such as

IPad IPhone Android phones and tablets RIM Windows Phone as well as other standards compliant

client and mobile platforms It should be noted that Open UI is not optimized for Gesturing but does

take advantage of the native gesturing features in mobile browsers Siebel Mobile provides the

optimized mobile solution that tightly integrates with mobile device features using standards

High-Level Migration Tasks

The migration to Open UI can be achieved in parallel to the existing environment without a significant

development effort The user experience will be similar enough not to require retraining of end users

(It is recommended that this is verified during the deployment process) Open UI can be added in

parallel to the regular upgrade so that it does not affect the existing environment if planned properly

The migration consists of adding object managers with the open UI parameter which becomes available

as part of the deployment of Siebel Innovation Pack 2012 Once enabled the customer can start

offering the Open UI option to a subset of the user population to test the new client to ensure the

readiness for the customerrsquos specific functional requirements As the features enabled by Open UI meet

acceptance requirements of the test population other users can start using the new client with the

enablement of a sufficient number of Open UI enabled Object Managers This activity has no bearing on

the functioning of the existing ActiveX client or SI user population The URL for Open U will be different

from the standard URL and available in parallel to the existing ActiveX client

The advised high-level roadmap for customers follows

Upgrades to a release compatible with Open UI

Implement Siebel 8119 or 8222 or above

Apply QFrsquos applicable to the release

Migrate from SEA to SIA if on a SEA release

Import Open UI related SIF files

Read FAQs and other release documentation provided for the migration

Add an object manager for the UI and set it to Open UI using the Open UI enablement settings

Test the upgraded deployment on HI and SI

Test the Open UI client rich internet application (RIA) deployment This can be tested in parallel when running the environment because it runs on a separate object manager)

Perform user-acceptance testing for all the deployed client UI options

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 9: Siebel Open UI Best Practices - Deployment Guide v1.34h

9

SI applications will not be supported with Open UI customers using SI templates will need to convert them to HI prior to rendering in Open UI

User Experience Providing a Highly Optimized User Experience through

Design Open UI enables implementing highly tuned design patterns to help our customers envision the design

possibilities and simplification they can bring to their Siebel implementations UX Direct

httpwwworaclecomwebfolderuxapplicationsUXDirectindexhtml introduces a User Centered

Design Implementation process providing tools and resources to get started Open UI allows for a highly

optimized user experience through its rich extensibility features when combined with those design best

practices Oracle also provides content ont the usable apps site at

httpwwworaclecomwebfolderuxapplicationsindexhtml

Development Configuration and extension of the UI To achieve the best possible user experience Open UI provides a fully published JavaScript API to build

powerful CRM solutions That API allows customers to easily extend the capabilities of Oracle provided

features The new API supports anything from simple validations to replacement of whole UI

components that require rendering in special ways In addition Siebelrsquos new implementation of CSS

allows extreme ease of branding the user experience Literally any aspect of colors fonts layout and

styling can easily be manipulated in Siebel

Customers can continue to use tools they are accustomed to or use the new web development

extensibility to build features previously unachievable using traditional means

Summary These changes enable the ability to provide improved usability deployment development and integration options Customers implementing Siebel today can expect many benefits of deploying Open UI

Features and Roadmap of Siebel Open UI The initial version of Siebel Open UI will have limitations in functionality compared with the existing

Siebel HI clients Customers are advised to carefully review the feature mappings provided in the tables

below Siebel Open UI can reside side-by-side on the same server with existing Siebel CRM

implementations and can run against the same SRF as existing SI or HI deployments to remediate any of

these limitations

Features Enabled in Siebel Open UI The following table provides a list of features that are available and provides the high level overview of

how they change in Open UI The NotesLimitations column will indicate if the feature does not have

feature parity with the ldquoHIrdquo equivalent feature If the ldquoNotesLimitationsrdquo column indicates that the

Siebel Open UI Roadmap should be reviewed please see table 2 for a targeted feature release

Additional data will be made available in the Siebel Bookshelf with the standard bookshelf updates

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 10: Siebel Open UI Best Practices - Deployment Guide v1.34h

10

Table 1 Features Enabled

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Application Menu Menu selection All

Eliminate duplicate features support keyboard use and accessibility

see Siebel Open UI Roadmap for missing features

Application Toolbar Buttons

Buttons in the Application Menu For information on Buttons see the associated features All

supports keyboard and accessibility na

Browser History amp Bookmarking

Browser History implements in URL and back forward button of browser All

Creating shortcuts to Siebel records has changed to implement native support for bookmarking Browser history is fully supported with browser forward back button enhanced features in HTML5 na

Calculator Calculator All

supports additional features such as percentages keyboard use and accessibility na

Calendar Calendar related functions All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Charts Charts All same function na

Checkbox Checkbox All supports keyboard and accessibility na

Date picker Date features

Date picker Date features All

supports keyboard and accessibility na

CTI Toolbar

CTI communications toolbar in Call Call center

OUI allows easy layout look and feel changes

na

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 11: Siebel Open UI Best Practices - Deployment Guide v1.34h

11

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

center

COM integration

JavaScript API to support client-side integrations across Browsers All

Open UI supports JavaScript API for extension which works withal browsers rather than COM na

Outbound Mail Email response

Client-side email integration service

Supports W3C RFC standard rather than proprietary integration

see Siebel Open UI Roadmap for additional information

Spellcheck Spellchecker All

now supported natively via browser (IE requires plugins to support spellcheck) na

Dialogs and Custom Rendered Popups

Dialogs and Custom Rendered Popups All

supports keyboard and accessibility na

Drag and Drop Drag and Drop All

File upload controls support drag and drop

see Siebel Open UI Roadmap for additional information

File upload and download

File upload and download All

multiple file drag and drop na

Grid View Grid View All

supports arrow key navigation tabshift tab and accessibility can save state for column order

see Siebel Open UI Roadmap for additional information

Images (BMPPNGGIF)

Images (BMPPNGGIF) All

improved accessibility through accessibility metadata higher image quality na

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 12: Siebel Open UI Best Practices - Deployment Guide v1.34h

12

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Message Notification

View message broadcast to users as a scrolling message All

Notification UI comprising Notification counter Summary Pane and Detail Pane Distinguish ReadUnread notifications and dismiss notifications

workaround Administration Requires HI

MVGPick list MVGPick list All

MVGs and pick lists now provide a similar look and feel to make feature easier to use

see Siebel Open UI Roadmap for additional information

Siebel Reports BI Publisher Basic Integration

Run basic and selected records reports using multilingual templates without administration scheduling or parameterization

Reports Marketing Loyalty

Basic iframe integration

see refer to MOS Doc ID 15013781 and Siebel Open UI Roadmap for additional information

PrintPrint Preview Print Preview All

native browser print dialog Moved from Siebel specific feature to browser native support na

Rich Text EditorHTML Editor

Rich Text EditorHTML Editor All

supports both HTML and Rich Text provides na

Search Find Applet level find PDQ All

Binocular button is not required as each applet has a search

see Siebel Open UI Roadmap for additional information

SmartScript Player

SmartScript UI Renders the questions answers and input controls All

OUI allows easy layout look and feel changes

see Siebel Open UI Roadmap for additional information

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 13: Siebel Open UI Best Practices - Deployment Guide v1.34h

13

Product Feature Product Functionality Delivered

Product Modules affected

New Features NotesLimitations

Tabs Tabs All

supports dynamic resizing keyboard use and accessibility na

Task Based UI Provides the Task Based UI All

Equivalent Features

see Siebel Open UI Roadmap for additional information

Time Picker Time Features

Time Picker Time Features All

supports keyboard and accessibility na

Tooltips Tooltips All

used for keyboard use and accessibility na

Tree Control Tree Control All supports keyboard and accessibility na

Zoom Zoom All

zoom features are now fully supported via browser na

Feature Roadmap for Open UI Features that are currently unavailable in the Open UI client are listed in the following table These

features are planned in future releases specified in the roadmap target column The product impact of

these controls is listed Many of these entries have practical workarounds for remediation Customers

may continue to use the ActiveX client for features unavailable in Open UI

Note Some of the features not available will still have artifacts present in the user interface to maintain

consistency with the existing user interface rendering and to provide a basis for delivering the features

in the list below Examples of these are home page applet artifacts and buttons for features listed

below in the application toolbar Customers have the option to remove those UI elements by

manipulating Siebel configuration via Siebel tools or using supported web development methods

Planned target releases of the related features are shown below in the ldquoRoadmap Targetrdquo column

Table 2 Feature Roadmap

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110 8223FP ETA

Customer Dashboard amp associated Button

Customer Dashboard and associated button Call center

81110 8223FP ETA

Customer Order Management (COM) Catalog Navigator

Customer Order Management

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 14: Siebel Open UI Best Practices - Deployment Guide v1.34h

14

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81110

8223FP ETA

Siebel Reports BI

Publisher Advanced

Integration

Reports scheduling

parameterized reports

Reports notifications using

notification ui

Reports Marketing

Loyalty

81110 8223FP ETA Remote

Windows 8 support for Remote Mobile Web Client

81110 8223FP ETA

Search Search Center Advanced Search and Search button All

81111 8224FP ETA Business Service Simulator Simulates business services All

81111 8224FP ETA Applet Location Editor

Applet Location Editor and Applet Hide feature All

81111 8224FP ETA Barcode Toolbar Reads barcodes Sales

81111 8224FP ETA Chat Call center chat API Call center

81111 8224FP ETA Calendar

Drag and Drop Features Validation Results All

81111 8224FP ETA Online Help System

Searchable context sensitive help All

81111 8224FP ETA

Customer Order Management (COM)

Sum total for list view Contact Hierarchy View tag renderer

Customer Order Management

81111 8224FP ETA

Outbound Mail Email response

Plain text email format with internal email client improved tracking service

81111 8224FP ETA Signature Capture Control

Signature Capture on the desktop Life Science

81111 8224FP ETA Dispatch Board

Dashboard feature for read only use case Field service

81111 8224FP ETA Drag and Drop Calendar Calendar

81111 8224FP ETA ExpressionRules Designer

Design Time Personalization business rules designer All

81111 8224FP ETA Funnel Chart

Design amp run Time sales and sales-phases pipeline analysis charts Sales

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 15: Siebel Open UI Best Practices - Deployment Guide v1.34h

15

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Gantt Chart

Gantt Charts and Gantt chart applets Hospitality function-space diary

Consumer Goods Hospitality Field Service Life Science

81111 8224FP ETA Grid View

Lock on list columns save state for column options Settable Column width All

81111 8224FP ETA HTML amp Rich Text Editor

Marketing campaign designer for HTML email offers Web offers and event web banners Marketing Loyalty

81111 8224FP ETA

IHELP and How Do I Application toolbar button IHelp Applet

Player panel to display iHelp information iHelp applet on the home page Call center

81111 8224FP ETA

Interaction Detailer amp Interaction detailer menu button

Interaction Detailer and interactive Detailer button Life science

81111 8224FP ETA Marketing Allocation

Manages marketing programs and Campaigns and segmentation Marketing Loyalty

81111 8224FP ETA Marketing Calendar

Used to render the Event schedule Marketing Loyalty

81111 8224FP ETA Marketing Flow chart

Organization charts flow charts Call center

81111 8224FP ETA Program Designer Designs programs Marketing Loyalty

81111 8224FP ETA

Right to Left Language support

RTL Language support for ARA and HEB languages All

81111 8224FP ETA Siebel Alerts Siebel Alerts All

81111 8224FP ETA SmartScript Designer Ability to design SmartScript Call center

81111 8224FP ETA Task Based UI

Portlet integration for TBUI TBUI Simulator All

81111 8224FP ETA

Customer Order Management (COM) Product Selector

Hidden control to render the SI applets for HI Product selection UI views

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Configurator Configurator

Customer Order Management

81111 8224FP ETA

Customer Order Management (COM) Edit Promotion UI Editing of promotions

Customer Order Management

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 16: Siebel Open UI Best Practices - Deployment Guide v1.34h

16

Roadmap Target

Product Feature Product Functionality in Roadmap

Product Modules impacted

81111 8224FP ETA Universal Inbox Universal Inbox feature Call center

Standard Interactivity Client (SI) Roadmap for Open UI SI client deployment features are not supported for automatic conversion to Open UI and not all SI

features have equivalent HI Open UI features to allow manually migrating to Open UI Migrating

applets or views to open UI requires HI equivalent applets or views in Siebel Tools If that is the case the

HI Features outlined for Open UI can be used to render the views and user interface

Self-Registration is a feature only available in SI and to register users in self-service a SI object manager

will be required as outlined in the table below

SI equivalent features will be provided based on the roadmap below

Table 3 SI Roadmap

Roadmap Target

Product Feature Product Functionality delivered

Product Modules impacted

Notes

81111 8224FP ETA

Customer facing applications amp self-registration

Used for customer and partner portals and self- registration salutation applet Real Time Shopping Cart View

Customer facing apps Customer Order Management

Workaround SI Registration Portal SI apps

81111 8224FP ETA

Customer facing service application

Customer facing service apps

Customer facing apps

Can be rendered via Open UI by converting to HI then rendering as Open UI

Deployment Characteristics

Siebel Open UI Client Security Siebel Open UI uses only three technologies to render the client code CSS HTML and JavaScript

Because of the small set of underlying technologies used to render the client it provides the least

possible attack surface Because the Open UI client is a scripted client it is compatible with DEPNX

features and many other browser and operating-system related security features The lack of third-party

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 17: Siebel Open UI Best Practices - Deployment Guide v1.34h

17

plug-ins such as ActiveX and Java further reduce the attack surface In addition to these security

measures the server provides sophisticated session security to provide a very secure end user

experience

Oracle tests JavaScript Controls from third parties to the same rigorous standards that are performed for

Oracle code The fact that all of the code consists of standards based solutions simplifies thorough

testing because client code is well understood by inspection tools Oracle uses industry-leading Web

application security assessment solutions to validate that the Open UI is secure Oracle also validates

security through its security-architecture teams and internal oversight organizations Oracle works with

the ethical hacking community to put code to the practical test of security

Siebel CRMrsquos UI can support the FIPS-140-2 standard as well as Common Criteria Certification for Siebel

CRM version 81 and later to level Evaluation Assessment Level 2 See the following link

httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf for additional information

Oracle takes part in Open Web Application Security Project (OWASP) and Oraclersquos OSSA (Software

Security Assurance) guidelines and policies (including required developer training) are in line with the

guidelines provided by OWASP documentation and recommendations These are guidelines policies

and secure coding standards that all Oracle product development teams are mandated to follow

To protect data integrity and system security multiple browser tabs running the Siebel application in a

browser is un-supported The application provides a list of options when this condition is detected

Siebel Open UI Server Side Memory Footprint for Clients Resource use for Open UI is very similar to the ActiveX UI The work done on the server is similar for

Open UI because it is for the HI object managers Because end users tend to use only one client at a

time the two object managers if used in parallel for the same users do not necessarily require

additional hardware resources

Siebel Open UI Client-Server Communication Because the client server communication is very similar for both UIs the networking characteristics are

similar In support of reduced network traffic Open UI client supports

A partial refresh feature that allows only small regions of the UI to be refreshed rather than the

entire UI This feature saves network bandwidth

Push notifications which eliminate polling for communications server messages such as CTI and

other messages

These features improve bandwidth requirements and in some cases reduce power consumption on

mobile devices by reducing ldquochattinessrdquo Siebel CRM can be run on modern wired or wireless networks

and it supports use over low-bandwidth connections

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 18: Siebel Open UI Best Practices - Deployment Guide v1.34h

18

Siebel Open UI Client Performance Though Siebel Open UI uses an interpreted JavaScript to render the client it performs extremely well on

modern browsers New features such as partial refresh that support new granularity in updating the UI

efficiently and asynchronous operation improve performance characteristics in specific features of the

client

Open UI caches client files and static Web templates using different implementations but similar

mechanisms as the HI client It is expected that performance will be largely similar although customers

are advised to test for performance in user-acceptance testing efforts

To enable a broad variety of platforms Siebel Open UI runs on code interpreted on the browser or JIT

compiled in the browser There are performance differences dependent on customization of the

interface when running cross platform code inherent to Open UI

JavaScript Framework

The performance of underlying JQuery components and the Siebel provided application are evolving

very quickly As it does performance of the application will continue to converge on the same key

performance indicators as the HI client

Hardcoding amp Flexibility

bull The HI client is effectively a monolithic client colors borders fonts cannot easily be changed and

there is no ability to easily modify the behavior of the UI This monolithic design enables a compact

client although not being very flexible

bull In Open UI client all aspects of rendering can be controlled Colors fonts borders backgrounds

the controls themselves used for rendering can be exchanged to offer just about any user experience

desired This creates somewhat more overhead in regard to performance when combining this

attribute with improper application tuning It is recommended to tune customized applications to take

this into consideration

Compiled Vs Interpreted

bull HI The fact that it is built in ActiveX which is essentially Win32 compiled and proprietary code

this can be processed extremely efficiently

bull Open UI Open UI has a strong dependency on the performance of the browserrsquos rendering

engine The section on Browser performance provides guidance on choosing the best performing

clients

Best Practices Tuning customized applications for virtual screen space

A web application can render easily beyond the limits of the data displayed on the screen effectively

increasing the amount of work done to render content It is recommended not to build UIs that render

only content used Between the larger rendered surface the interpreted nature and the ability to adjust

any of the functionality these factors can compound to reduce performance from methods used in the

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 19: Siebel Open UI Best Practices - Deployment Guide v1.34h

19

past It is recommended to review the deployment with needless content in mind to optimize the

performance In light of this there are several considerations that can be followed as a best practice

bull Applets It is recommended both from a performance and usability perspective not to add

more applets to a screen than the typical user can consume without scrolling Scrolling interrupts work

does not work well on some mobile devices and the content not displayed still requires rendering on

screen refresh

bull Displayed columns in list views Consider limiting columns available and set good defaults for

columns displayed For most desktops no more than 7 columns should be displayed by default as a rule

of thumb Even the components hidden have to be processed by the Rendering engine

Siebel Open UI Accessibility Siebel CRM has added the benefit of keyboard-only support which can be leveraged by high-

performance keyboard users and accessible users in conjunction with screen readers and other assistive

technologies

W3C Accessibility Standards WAI-ARIA amp WCAG20 AA

Open UI has been designed from the start to meet WCAG20 AA accessibility standards where possible

and practical Section 508 and draft mandate 376 are covered in large part via WCAG20 AA

conformance Oracle has taken leadership in not only attempting to meet mandates but to provide

very practical and usable business solutions for accessibility enabled business users and consumers

WAI-ARIA httpwwww3orgWAI is an initiative by W3C for rich internet applications in regard to

accessibility WAI-ARIA aims to systematize the design of Web-page accessibility for rich internet

applications Open UI aggressively meets web standards from W3C including WAI-ARIA markup and is a

leading enterprise application in adopting accessible technologies from the W3C

Note To use Siebel Accessibility end users must use WAI-ARIA compliant Browsers and Screen readers and accessibility aides if needed

Accessibility features

Open UI has many features designed specifically for accessibility A brief list follows

Always on accessibility Accessibility is always enabled for all users not just accessible users No

action is required to enable accessibility

Dynamically generated accessibility data for the entire rich internet application

Full screen reader compatibility through use of WAI-ARIA metadata for labels images and other

application information

Enablement of accessibility for dynamic content within the application WAI-ARIA markup for

dynamic events like notifications popups and dynamic visual clues such as flashing buttons or

hourglass-type indicators

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 20: Siebel Open UI Best Practices - Deployment Guide v1.34h

20

Screen Reader Support

Siebel Open UI allows the use of screen readers WAI-ARIA compliant screen readers provide facility to

show the navigable regions and to interpret WAI-ARIA markup present in the Siebel application WAI-

ARIA provides a role attribute to mark Landmark regions

Accessibility Implementation

WAI-ARIA markup in Siebel Landmark Roles in WAI-ARIA

WAI-ARIA provides a collection the landmark roles that can be applied to each of the navigable regions

identified for the Siebel application Disabled users can navigate directly to the various application

widgets like Application Menu Toolbar Applet and so on by using Assistive Technology shortcut keys

Open UI has marked up the following landmarks

Application Page identifies the Application Page Region

Application Menu identifies the Application Menu Region

Application Toolbar identifies the Application Toolbar Region

Application Screen Bar identifies the Application Screen Bar Region for navigation to views

Predefined Queries identifies the region that contains the Predefined Queries

Visibility Dropdown identifies the region that contains the Visibility Dropdown

Main View identifies the Main View Region that contains the various applets

Applet identifies the Applet Region

To understand landmarks in more detail see

httpwwww3orgTRwai-aria-practiceskbd_layout

Application Wide Navigation and Landmark Roles

WAI-ARIA improves Siebel CRM navigation features To understand WAI-ARIA guidelines for tabbed

navigation between widgets see httpwwww3orgTRwai-aria-practiceskbd_general_between

The Tab and Shift+Tab keys move focus among widgets and standard HTML controls As an example a

typical List Form view the tabbing sequence would be

Application Menu Bar -gt PDQ dropdown -gt Toolbar -gt Visibility Dropdown -gt List Applet Menu -gt List

Applet Buttons (one by one) -gt List Applet Column Headers (one by one) -gt List Applet Grid First Row

First List Column Control -gt Form Applet Menu -gt Form Applet Buttons -gt Form Applet Controls (one by

one)

Keyboard Navigation within Widgets

Once within the widget use the following keys to handle tasks

The arrow keys to navigate

The enter key to drill in

The escape key to back out

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 21: Siebel Open UI Best Practices - Deployment Guide v1.34h

21

Top Level composite widgets such as the Application Menu Bar the Applet Menu Tabs at any of the

four possible levels the List Applet Grid and so on have complex navigation requirements between

their constituent elements and widgets There are a set of general recommended principles to follow for

such navigation Details are available at httpwwww3orgTRwai-aria-practiceskbd_general_within

Keyboard Shortcuts

Siebel CRM continues to support keyboard shortcuts and it supports shortcuts found in both the HI and

SI client In some cases the shortcut combinations have changed in particular in cases where they

interfere with common browser shortcuts by browser vendors for browsers now supported via

standards support or where they interfere with accessibility standards In general the new keyboard

navigation model is simplest to use but keyboard shortcuts can be very useful for performing of

repetitive and frequently used tasks More information can be found at httpwwww3orgTRwai-

aria-practiceskbd_shortcuts

Siebel CRM Releases Supporting Siebel Open UI Siebel Open UI requires the adoption of the Siebel Innovation Pack 2012 which will be delivered via

Siebel 8119 fix pack and Siebel 8222 fix pack with Siebel CRM version 81 and Siebel CRM version82

To deploy Open UI customers must upgrade to the fix pack levels indicated using Siebel Industry

Applications Customers using Siebel Enterprise Application (SEA) versions of Siebel CRM must migrate

to Siebel Industry Applications These fix packs continue to support the high interactivity and standard

interactivity clients in addition to the new Open UI

Client Requirements

Open UI Browser Standards Conformance Requirements Siebel Open UI will perform best on modern browsers that comply with W3C standards Oracle is

committed to supporting Web standards to ensure a problem-free user experience while using Siebel

CRM in Open UI A recommended measure of W3C browser standards compliance is the ACID3 series of

tests The higher a browser scores on ACID3 the higher the likelihood that a great user experience can

be provided on the client browser ACID3 tests can be run at httpacid3acidtestsorg Many modern

browsers meet a level higher than 50 out of 100 on the ACID3 test and it is recommended to run the

application on the best performing enterprise browsers many of which score close to 100 for employee-

facing applications

Siebel Open UI supports browsers if they conform to accepted browser standards

HTML Though HTML401 is the minimum requirement for the desktop HTML5-capable browsers are recommended to take full advantage of the features in Open UI on the desktop Mobile browsers generally support HTML5 HTML5-capable browsers provide additional functionality in the application over HTML4 clients Bookmark features are an example of a feature where behavior is improved using HTML5 features

JavaScript Siebel Open UI supports JavaScript (ECMA-262) and above both on the desktop and for mobile browsers

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 22: Siebel Open UI Best Practices - Deployment Guide v1.34h

22

CSS CSS 21 is the minimum requirement but CSS30 provides an improved end user experience

WAI-ARIA Accessible users accessing the browser must use a WAI-ARIA compliant screen reader technology and browser

To validate a Siebel pages against the W3C standard a number of W3C hosted validation services are

available These validations services include

W3C Html validator httpvalidatorw3org

the CSS validator httpjigsaww3orgcss-validator

The Html5 validator httphtml5validatornu

LINT JSLINT and derivatives httpwwwjslintcom

Use of Popup Blockers

Open UI is compatible with popup blocker use Ensure Siebel application servers and third party iframes

are whitelisted or excluded if popup blockers are used

Open UI Browser Performance The performance of the chosen client browser or device has a large impact on client performance It is

recommended that customers perform user acceptance testing on the browser of choice To get an

understanding of the performance of a variety of browsers on different devices a simple test of the Sun

Spider benchmark is recommended for clients under consideration The Sun Spider benchmark is found

at httpwwwwebkitorgperfsunspidersunspiderhtml Example data for a variety of browsers is

listed in the following table It provides a means of comparing relative computing performance in a

normalized manner

Table 4 HardwareClient Benchmarks

Browser Time Hardware

Internet Explorer 6 86 seconds Dell Latitude E6410

Internet Explorer 7 18 seconds Dell Latitude E6410

Internet Explorer 8 36 seconds Dell Latitude E6410

Android ICS browser 28 seconds Galaxy S2

Safari 22 seconds iPad 2

Chrome for Android 21 seconds Galaxy S2

Internet Explorer 9 06 seconds Dell Latitude E6410

Internet Explorer 10 03 seconds Dell Latitude E6410

Firefox 029 seconds Dell Latitude E6410

Safari (latest) 028 seconds Dell Latitude E6410

Chrome (latest) 023 seconds Dell Latitude E6410

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 23: Siebel Open UI Best Practices - Deployment Guide v1.34h

23

As can be seen by the performance times some browsers are not as well suited to high performance

and optimized characteristics as others

Open UI on Legacy Browsers

Customers may review the following options for deployments using Internet Explorer 6 and 7 and

possibly for Internet explorer 8 due to their performance and conformance limitations

Deploy a second modern and standards based browser for use with Open UI because of

performance and standards conformance considerations

Continue to deploy HI object managers for users that only have Internet Explorer 6 and 7

available

Consider use of a web browser layout engine plug-in that meets

standards and performance requirements to update browsers

to be more performant Chrome frame

httpwwwgooglecomchromeframeprefersystemlevel=true

may provide such an option if it meets user acceptance criteria

for Siebel and other enterprise applications

For additional information on deploying Chrome Frame for specific applications please see

httpwwwchromiumorgdevelopershow-toschrome-frame-getting-startedchrome-frame-faq

Note Plug-in solutions are solely dependent on the third parties building them and customers are

advised that Oracle has no part in support of those solutions

Si Client UI Requirements The Siebel SI client is also a standards-based client only requiring support for HTML401 CSS21 and

JavaScript (ECMA-262) Since it does not make liberal use of JavaScript it does not have performance

requirements for browsers It also lacks the WAI-ARIA requirement for accessible users though Open UI

client provides a far superior user experience

HI Client UI Requirements The following lists the requirements for high interactivity (HI) clients used for employee applications For

an explanation of employee applications

32-bit versions of Internet Explorer 60 Internet Explorer 70 and Internet Explorer 80 are

supported for employee applications

64-bit versions of Microsoft Internet Explorer 60 Internet Explorer 70 and Internet Explorer

80 are not supported for use with the ActiveX client

For information about the recommended settings for the web client see Siebel System Administration

Guide on the Siebel Bookshelf

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 24: Siebel Open UI Best Practices - Deployment Guide v1.34h

24

Each supported browser requires installation of the Oracle Java Runtime Environment (JRE) version 142

or above For more information about the high-interactivity client see Siebel Deployment Planning

Guide on the Siebel Bookshelf

NOTE Tabbed browsing is supported with Siebel applications for one active session Multiple Web

pages may be opened using tabbed browsing but only one tab can have a live connection to a Siebel

application at a given time

Installation

Choosing a UI for Siebel CRM Siebel CRM supports side-by-side use of all user interfaces in a single deployment and on a single server

SI HI and Open UI However each user interface must each have a configured object manager This

allows running Open UI in parallel to existing Siebel client instances It should be noted that each UI

type SI HI and Open UI will receive its own URL as well

Siebel Open UI supports the existing SRF without any change to it and Siebel Web Templates that have

been customized When using Open UI it is recommended that any customized Web templates are

moved to the newly created customer files locations as described in the bookshelf documentation

ldquoConfiguring Open UIrdquo

Open UI provides benefits for specific deployments It allows the migration to Open UI without any

change in the developed content This is a good option to use when migrating with minimal effort

Customers can continue to use existing browser scripting as used in HI mode without requiring any

changes

The new JavaScript API provides a more modern means of achieving what can also be performed using

client-side browser scripting Customers can write JavaScript using their own IDE and extend the

provided JavaScript API Guidance on converting browser scripting to JavaScript API content is

provided in the ldquoConfiguring Siebel Open UIrdquo document in Siebel Bookshelf

When using the new file deployment structure Open UI allows customers to get dynamically updated

Web templates from Oracle without the possibility of overwriting customer file content This allows for

maintenance and improvement of templates for issues related to performance usability and standards

compliance of out of box templates as part of maintenance releases Customers are able to lock

templates from being upgraded by moving them to the customer directory structure Customers

migrating existing HI mode Web templates will be required to physically move the files into the new

directory structure Guidance for this activity is provided in the ldquoConfiguring Siebel Open UIrdquo document

in Siebel Bookshelf

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 25: Siebel Open UI Best Practices - Deployment Guide v1.34h

25

Mitigating Deployment Risks The migration to Open UI can be achieved in parallel with the existing environment with minimal

development effort Because the migration can be performed and the addition of Open UI does not

affect the existing deployment it does not impact the existing environment if planned properly

Customers must take into account the constraints of what browsers are supported by each client for

example standards compliant browsers for Open UI while the Siebel HI client requires IE version 8 or

below Meeting both requirements allows switching back to the legacy deployment as needed using

the same browser

If browser constraints are considered properly then there is no risk in maintaining both environments

until user acceptance tests are completed with successful results

Note Before getting started please review the list of features unavailable in the Siebel Innovation Pack

2012 referred to earlier in the document

Overview High Level Installation steps To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf for the GA

release

1 Apply Fix Pack for 81 or 82 based on the base installation used (Databases should be standard

811 or 822 GA version and of one of these three varieties DB2UDB Oracle or MSSQL)

2 Apply Quick Fixes and associated Repository changes

3 If running on a Siebel Enterprise application Build please consult with migration steps to Siebel

Industry Applications Information on this can be found at SEASIA Repository Strategy and

Migration Guide An overview of the same can be found in the Siebel Upgrade Technical

Overview

Installing Open UI and Siebel Mobile To implement Open UI Siebel Innovation Pack 2012 must be installed Instructions for Siebel Innovation

Pack 2012 are found in Siebel Maintenance Release Guides and in the Siebel Bookshelf

1 Download Innovation pack 2012 for your release 8119 or above (for 81 release) and 8222 or

above for (82 release)

2 Run the Installers for the fix pack

a For Server

i The installation follows a standard pattern for a fix pack installation as described

in the ldquoMy Oracle Supportrdquo article at Siebel 8118 or 8221 Fix Pack Release

Using Oracle Universal Installer (OUI) Framework [ID 14616401] This

document serves as a high level example for these installation steps

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 26: Siebel Open UI Best Practices - Deployment Guide v1.34h

26

ii Databases should be standard 811 or 822 GA version and of one of these

three varieties DB2UDB Oracle or MSSQL

b For Siebel Mobile Web Client or dedicated web client install only

i Run base web client

ii Run Innovation Pack 2012 Siebel Web Client fix pack

3 Apply the latest applicable Quick Fixes for your release generally available from Oracle

Installing Siebel HI Web Client and Client Topics related to Open UI Siebel HI is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Note If deploying HI object managers on a server customers must unzip the images in IE8Imageszip

provided in httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=15114481

into the SWEAPPpublicltLANGgtimages directory Symptoms of not doing so are several missing tabs

in the user interface This applies to all Siebel HI web clients including dedicated web client and Mobile

Web Client and is a known issue and will be resolved in the future

The images in the zip file are of a lower resolution (8 bit) that is compatible with both Open UI and HI

Clients Images native to Open UI provide 32 bit resolution for crisper image quality and a better user

experience

Note It is strongly recommended to import the SIF file as described in the section ldquoImporting Application

Configuration (SIF files)rdquo below even if not using the Open UI client as there is no adverse impact to a HI

environment This reduces regression testing efforts on HI Clients if adding Open UI clients at a later

time

Installation of SI Web Client and Client Topics related to Open UI Siebel SI Web Client is unaffected by running in parallel to Open UI or on Siebel Innovation Pack 2012

Oracle recommends that customers may want to add modern user agents to their SI deployment to

optimize the ability to render on modern browsers

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=11593351

Configuration

Overview High level configuration steps To deploy Siebel Open UI several steps must be followed

Download the Innovation pack 2012 release

1 Import your seed data using the provided batch files

2 SIF files for import are provided to enable Open UI and Siebel Mobile features These must be

imported

3 Compile amp deploy the new SRF

4 Please bounce your server (or restart your mobile web client) after completion of the import

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 27: Siebel Open UI Best Practices - Deployment Guide v1.34h

27

5 Add or clone an object manager depending on use of Siebel Mobile or Open UI

6 Add Virtual directories as needed

7 Set the image files based on deployment requirements

8 Use EnableOpenenUI= TRUE (or FALSE) to change between HI and Open UI mode Set this

parameter in the client CFG file or in the object manager parameter as needed

9 Tune Web Server performance for your environment and web server type

Note For Siebel Mobile please follow the steps in the ldquoConfiguring Siebel Mobilerdquo Section below

Configuration of Open UI Please follow the steps in each section below only if they apply to your use case

Importing Application Configuration (SIF files)

To deploy Siebel Open UI or Siebel Mobile application configuration SIF files must be imported using a

simple batch file The SIF files must be imported into the repository via tools and should not affect

existing repository objects adversely Based on which clients you use you will need to import the Siebel

Mobile andor the Siebel Open UI SIF file It is strongly recommended to use Unicode code page

databases when importing SIF files because of superior import performance For non -Unicode

Databases please refer to MOS Doc (11985341) for additional instructions

Siebel Tools contains the following zip files in the REPPATCH folder

OpenUI_Base_8119zip or OpenUI_Base_8222zip

OpenUI_Mobile_8119zip or OpenUI_Mobile_8222zip

Note If you have run previous versions of Seed or SIF data import run the steps below to update the

information

To import the Sif file compile and deploy the SRF with the components in the applicable SIF file (named

openUI_zip) based on the instructions in the readmetxt file contained within it

1 Back up your target database

2 Create an ODBC entry for the database where you plan to import the seed data into

3 Open your toolscfg file and change SymStrPrefix=X to SymStrPrefix=SBL

4 Create new projects as specified in the beginning of projects_and_objectstxt

5 Check out or lock the projects specified in the Projects to LockCheck Out section in

projects_and_objectstxt

6 Ensure languagetxt contains the language codes of the languages you need with each code in a

separate line

7 This step is optional but recommended Specify environment information in preferencetxt 8 You will be prompted for the information for entries that are left blank

REPOTOOLSBIN=ltpath where to find siebdevexe eg Csiebeltoolsbingt REPODATASOURCE=ltDataSrc entry from toolscfg where to import the objects intogt REPOUSERNAME=ltUser Namegt

REPOPASSWORD=ltPasswordgt DBTYPE=ltORACLE|MSSQL|DB2UDBgt (ie the data base vendor)

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 28: Siebel Open UI Best Practices - Deployment Guide v1.34h

28

DDLPATH=ltpath that contains ddldictexe and ddlimpexe usually ltSiebsrvrgtbingt

SIEBUSER=ltSiebel Usernamegt SIEBPW=ltSiebel Passwordgt ODBCDATASOURCE=ltODBC DataSource Namegt (ie the name of the ODBC data

source reated in step 2) TBLO=ltTable Ownergt TBLOUSER=ltTable Owner Usergt (only needed for MSSQL) TBLOPW=ltTable Owner Passwordgt

Run importbat

9 Verify the import logs in ltpackagegtLog for all imported packages

10 Compile the repository to create a new srf with the new and modified objects which are listed

in projects_and_objectstxt

11 Open your toolscfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X

12 Verify the import logs for the seed data in ltpackagegtSeedltDBTYPEgt

13 Please bounce your server (or restart your mobile web client) after completion of deployment of

the new SRF file

14 Perform configurations according to the ldquoAdditional Instructionsrdquo documents in the subfolders

if such documents exist

Adding Siebel Open UI Object Managers

To set configuration for Siebel Web Client via server object managers set the parameters in Application

Server Configurationgt Component Parameters as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

Enabling and Disabling Open UI on clients

To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration set

the client parameter in uagentcfg in the [InfraUIFramework] section as follows

To render as High Interactivity client

EnableOpenUI=FALSE

HighInteractivity=TRUE

To render as Open UI client

EnableOpenUI=TRUE

HighInteractivity=TRUE

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 29: Siebel Open UI Best Practices - Deployment Guide v1.34h

29

Backing up configuration and setting Environment variables

1 Stop Siebel Server 2 Stop Gateway Server and make backup of siebnsdat file 3 Restart Gateway Server 4 Set SIEBEL_HOME environment variable to SES_HOMEsiebsrvr directory 5 Start Siebel Server and make sure that components are online (assumption Srf used by Siebel

Server is the resulting SRF after SIF import)

Adding Virtual Directories for Siebel Open UI

Note The following steps must be followed if you are cloning a HI object manager or installing a new

virtual directory or your Open UI client or Siebel Mobile client

1) Stop the Web Server

2) Back up files eappcfg eapps_siacfg and web server config file (objconf httpdconf etc)

3) From EAPPWEB_HOMEconfig directory execute new_virdirssh new_virdirssh or new_vdirsbat

script with following parameters Keep in mind the script on UNIX platforms accepts 2 parameters

ltLANGgt ltWEBSERVER_LOCATIONgt according to the Siebel installation guide for your platform

a) Unix newvirdirssh ltLANG COMMA SEPERATEDgt ltWEB SERVER LOCATIONgt

b) Windows only one parameter is required eappwebconfig gt new_virdirsbat ltlanggt

4) Restart Web Server

5) You should be able to access the new components using the URL

Note for every failed execution of the above script you must restore all necessary files from the backup

For customers using Open UI or SI clients no steps need to be taken in supporting images

Enabling Accessibility for an Object Manager or Mobile Web Client

Accessibility for the Siebel Application is enabled out of the box No settings are required to enable it It

provides the following added benefits for accessibility

Performance tuning for Siebel Open UI

Though Siebel Web Server installations attempts to perform some amount of optimization it is

recommended that customers run performance tuning plugins such as YSLOW (which runs on Firefox) to

verify good configuration tuning of the web server More information can be found at the following

location httpsaddonsmozillaorgen-USfirefoxaddonyslow YSLOW for well configured system

will generally provide a ldquograderdquo of 85 or above More information about performance rules can be

found at httpdeveloperyahoocomperformanceruleshtml Settings that should be made for the

web server platforms used are

Minify customization using a tool such as YUI compression for customer JavaScript and CSS

Enabling gzip compression on the web server Instructions as available are below

o Microsoft IIS 6 IIS 7 IIS75

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Disabling ETag on the web server This will generally improve performance on multi-server

deployments

o Microsoft IIS6 IIS7 IIS75

o Oracle IPlanet 61 70

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 30: Siebel Open UI Best Practices - Deployment Guide v1.34h

30

o IBM HTTP Server 20471 70

Header Expiration should b set to 5 days for production deployments Do not set this for

development environments

o Microsoft IIS 6 IIS7

o Oracle IPlanet 61 70

o IBM HTTP Server 20471 70

Migrating SRF and SWT files

There should be no requirement to change the SRF to run Siebel Open UI Siebel Web templates remain

in the same location for migration mode but they are moved to a new location in the ldquonative mode of

Open UI Moving the files to their new location is detailed in the ldquoConfiguring Siebel Open UIrdquo

document in Siebel Bookshelf

Migrating browser scripting

There should be no requirement to change the client side browser scripting to run Siebel Open UI

Customer must ensure however that no browser specific JavaScript is implemented in existing browser

scripts to ensure function beyond the traditionally supported browsers Examples of such are the use

COM related functions win32 specific calls or other IE specific hooks

Behavior of SI Views inside RIA Mode

The HI client displays certain SI mode applets When converting HI applications to Open UI there are

specific rules for converting those SI applets because Open UI does not support SI mode applets Open

UI Framework will support the following scenarios only when EnableOpenUI=TRUE If this parameter is

FALSE (Open UI is disabled) then all legacy checks will apply

Applets in Open UI will automatically be promoted to ldquoHIrdquo in the following Scenarios

1) Contains one or more Applets which are not bound to a Business Component 2) Contains one or more Applets whose ldquoClassrdquo properties points to a Class which derives from classes

that implement the base functionality of Standard Interactivity 3) Contains one or more Applets whose associated Class have ldquoHigh Interactivityrdquo set to 1 4) Contains one or more Applets with User property High Interactivity Enabled = N 5) Contains one or more Applets outside of a View ie not associated to a view web template other

than standard popups (MVGPickAssoc) eg ldquoAbout Recordrdquo 6) Contains one or more Applets with a portlet in it 7) Product Catalog style layouts

Applets will not render in Open UI in only one scenario

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 31: Siebel Open UI Best Practices - Deployment Guide v1.34h

31

In this use case the image shown with a tooltip explanation will be rendered to inform the applet cannot

be rendered

Portal Integration

Open UI is not a Portal framework as such and hence it supports Portal Standards via the ability of the

hosting component to be based on one of the two standards

bull JSR268 As a Portlet API would allow for the creation of a simple portlet containing the appropriate

iFrame container used to call the Open UI as well as containing the appropriate Java lt=gt JavaScript

interface (Open UI allows for client side interaction via a JavaScript interface)

bull WSRP 20 As the more generic messaging standard support for WSRP would allow for the use of

ADF based components In this case Open UI is again hosted within a web Container within the

component and the portlet Bridge technology is used to expose the Task-Flow to the consuming

portal as a WSRP portlet

In either case the choice will be dependent on the nature of the consuming Portal and its support for

either JPS20 or WSRP20

In the case of Open UI it is really the hosting container that is exposed via the Portlet interfaces rather

than the UI itself This is a hybrid app model similar to modern HTML5 based mobile applications The

Portlet is acting as a wrapper to generate the required URL to Open UI as well as maintaining the

interactions with the currently loaded screens so as not to lose context via the JavaScript API Note the

Portal server and the Open UI hosted within it would need to be on the same domain (to avoid issues

with JavaScript cross-domain policies) HTML5 JavaScript hassome support for cross domain

capabilities thatmay be implemented

Integrating Open UI in WebCenter (at least from a simple view perspective is quite easy) Given

WebCenter natively supports the use of ADF task-flows one can create a task flow which takes input

parameters and internally build the required URL to call Open UI hosted within an ADF frame

component with the source based on the managed bean used to construct the URL ADF supports the

use of a Client Side Listener (and corresponding Server Side Listener) which allows for the execution of

JavaScript in the client from code within the task flow (and also the reverse JavaScript calling Java) One

can pass information to Open UI via Custom Attributes (Java side variables which are accessible in the

ADF client objects and hence via JavaScript)

If it is required this Task-flow can then be consumed via other Portals supporting WSRP20 (such as

Oracle portal Weblogic Portal etc) through the use of Portlet Bridge technology (JSR329) which

surfaces the JSF components as a WSRP based portlet There are a number of Portlet bridges on the

market from different vendors (Oracles allows for Portletizing ADF Task-Flows) It should be noted

that some vendors have extended the standard with proprietary extensions such as JSF20 which limit

the platform compatibility of the solution

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 32: Siebel Open UI Best Practices - Deployment Guide v1.34h

32

If the consumer is WebCenter use of pure Task-Flows is recommended unless it is necessary to have the

portlet run remotely from the Portal In that case Oracle Portlet Bridge can be deployed For other

Portals a custom JPS based portlet can act as a wrapper or a native portlet bridge technology for the

Portal vendor in question may be deployed

Configuration of Siebel Mobile Siebel Mobile Configuration is covered in KM document 15114451 on My Oracle Support

Setup steps for Siebel Connected Mobile Applications - Object Managers and Virtual Directories (Doc ID

15114451)

Configuration Options for SI Portal Customers Customers using SI portals wishing to use Open UI features have several alternatives SI Applets and

functionality can with a little effort be switched to HI in which case it can be rendered in Open UI as the

conversion process is seamless from HI to Open UI Some SI features cannot be converted today such as

self-registration Self-registration is very important for customer facing deployments Support for

these additional items will be completed in the future

Customers will decide between the following options

Perform manual tasks to get to HI once all the needed pieces are in place

Use new features extending customer facing options in Open UI

Continue use of SI Each option will have advantages and disadvantages but open UI will make customer facing

deployments easy to deploy

Configuration of HI Web Client and Client Topics related to Open UI Siebel HI Web Client is configured with information found at

httpssupportusoraclecomoipfacessecurekmDocumentDisplayjspxid=4769521

Developing in Open UI Developing in Open UI enables a lot of new possibilities for customers Configuration can be performed

using Siebel Tools or with standards based Web development tools to create a unique and pleasant user

experience adapted to business use cases for end users using Siebel applications

Though Open UI does not require Web development activities developing with the new JavaScript API

provides a powerful tool to extend the platform

Open UI continues to work much like the current client If you want to customize the SRF and Web

templates or write browser scripting or just leave it in a standard deployment then you continue to

have that option Additional information will be provided in ldquoConfiguring Open UIrdquo in Bookshelf

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 33: Siebel Open UI Best Practices - Deployment Guide v1.34h

33

Customizations in Open UI Siebel supports flexible options for development in Open UI Customers should be aware of the

implications of developing in each supported development style This includes understanding the

support for development and the implications on the deployment

bull Open UI allows the ability to use previously defined or existing repository and render it in Open UI

without further development The UI will be rendered in the Open UI paradigm and does require

User Acceptance Testing to validate full utility

bull Siebel Tools can be used to configure Siebel Open UI so that it fits in your business environment and

meets specific user requirements Siebel Tools configuration works the same for Open UI as for

existing client types like HI and SI to configure the SRF Siebel Web templates

bull Web development skills to extend Siebel using the new public JavaScript API The new JavaScript

API that Siebel Open UI uses replaces browser scripting for environments using proprietary browser

scripting for HI implementations Though Browser scripting continues to be supported Oracle

strongly recommends converting browser script to features built on the JavaScript API It also allows

Including Siebel Open UI or individual Siebel Open UI objects such as views or applets in a third

party user interface or integrating external content in the Siebel Open UI client

bull The ability to easily and fully customize CSS Style sheets provided as part of Siebel Open UI for ease

of branding of the user experience

bull You can combine traditional Siebel Tools development with development on the JavaScript API as

needed

Customers can use your preferred Integrated Development Environment (IDE) to write native JavaScript

code on top of the public API that Siebel CRM uses or with the JavaScript API that it uses For more

information see Chapter 5 ldquoCustomizing Siebel Open UIrdquo

You can use HTML CSS or JavaScript to add features For example you can do the following

bull Build user interfaces on any technology that can integrate with Oraclersquos public JavaScript API

bull Use your preferred open-source JavaScript frameworks such as JQuery from the open-source

development community or use the framework that Siebel Open UI provides Use a plug-in

proprietary development environment or native development environment that you choose to

create a custom rendering architecture that resides top of the public JavaScript API

bull Use intra-workspace communication and DOM (Document Object Model) access and manipulation

through standard JavaScript programming

bull Do a limited pilot User acceptance test of your configuration in your current Siebel Server

implementation while most of your users continue to use the high interactivity Siebel client

bull Preserve your existing configurations and customizations

For more information see ldquoOverview of Customizing Siebel Open UIrdquo in Siebel Bookshelf

Note Before considering development of applications on Open UI please carefully review support policies

for Open UI below

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 34: Siebel Open UI Best Practices - Deployment Guide v1.34h

34

Development and Support Impact of Open UI Customization

Siebel Tools Siebel Tools development and changes in Siebel Web Templates can typically be deployed to both client

types the HI client and the Open UI client Support for these modifications follows the convention that

has always been in place for Tools development on Siebel

Note Systems running Siebel Tools have a requirement t run Internet Explorer67 or 8 IE9 or other

browsers are currently unsupported for Tools development Code developed on IE8 will run on other

browsers

The Public JavaScript API The JavaScript API extension is a very powerful method for experienced web developers familiar with

JavaScript to extend Siebel features in Open UI HI or SI clients do not benefit from these changes

Oracle only supports the published JavaScript API and its documented features and ensures the APIrsquos

proper function The implementer systems integrator is fully responsible for support of the code that

is written against or extends this API For product issues related to the API support may request for a

minimal test case exercising the API in question

Oracle is supportive of customers using the Integrated Development Environment (IDE) of their choice

to write native JavaScript code on top of the public API but Oracle cannot support features or quality of

third party IDErsquos

Oracle is supportive of use of the JavaScript API with the rendering framework of the implementer

System integrators choice Oracle has implemented Open UI in HTML and this can serve as a template

for implementations on other technologies allowing for expedited development for advanced

development organizations Oracle can in no way support such customizations as this falls outside the

scope of Oraclersquos support for customization It is recommended that customers work with Oracle

consulting on implementation issues related to the JavaScript API

Migrating Existing COM Integration COM integration is a proprietary interface for the Windows platform COM interface function in Open

UI is replaced by the JavaScript API provided as part of the release Many desktop products such as

Office support JavaScript Interfaces to allow building similar features to the web browser

The Siebel Bookshelf Guide for configuring Siebel Open UI is a helpful reference in such integrations General best practice suggests that the JavaScript API can be implemented with other web based

interfaces or proprietary platforms supporting JavaScript APIs

It is recommended to move integrations that have been traditionally on the desktop that do not readily

support JavaScript integration to the server side or integrate with the server side via web service

integration This allows for staying with the design of modern web based deployments

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 35: Siebel Open UI Best Practices - Deployment Guide v1.34h

35

CSS Changes Oracle implements CSS for styling and layout Open UI and HISI clients use different implementations

of CSS Open UI CSS changes only benefit the Open UI client and no other clients

The implementer and systems integrator is fully responsible for any changes in CSS in regard to impact

on the rendering of the application Oracle has taken great care in providing a high level of standards

compliance in the provided CSS code to ensure proper function

CODE suggestions Examples templates Oracle makes the best attempt to provide development examples and templates that can be used in

understanding development on Open UI Oracle only provides these examples to assist in gaining an

understanding of the extensibility API The code provided is not supported by Oracle Only the

documented function of the API is supported For more information on the JavaScript API refer to the

Siebel Bookshelf guide ldquoConfiguring Siebel Open UIrdquo

Additional info on Support can be found in Scope of Service for Siebel Configuration and Scripting - Siebel Open UI (Doc ID 15133781) on My Oracle Support

Reference Information

Other Resources Additional Information can be found at the links below and through Oracle University

Data Sheets

Open UI Data Sheet

Siebel Mobile Data Sheet

Siebel Bookshelf

Siebel Bookshelf Guide for customizing Siebel Open UI great for web developers

httpdocsoraclecomcdE14004_01booksconfig_open_uiconfig_open_uiTOChtml

Siebel Bookshelf End User Fundamental Guide for end users

httpdocsoraclecomcdE14004_01booksFundamentalsFundamentalsTOChtml

Siebel Mobile Guide for mobile app developers

httpdocsoraclecomcdE14004_01booksConnMobAppsConnMobAppsTOChtml

Standards supported by Siebel CRM Open UI The following list provides the standards implemented in Siebel Open UI Many of these assist in

meeting commercial of-the-shelf procurement practices

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 36: Siebel Open UI Best Practices - Deployment Guide v1.34h

36

Table 5Supported Standards

Standards Body Std Spec Detailed Description Notes

W3C CSS 21 httpwwww3orgTRCSS21

rendering of clients

W3C CSS30 httpwwww3orgStyleCSS

rendering of clients

W3C HTML 50 httpwwww3orgTR2011WD-html5-20110525

rendering of clients

W3C HTML 401 httpwwww3orgTRREC-html40

Rendering of clients

W3C HTTP 11 RFC-2616 httpwwww3orgProtocolsrfc2616rfc2616html

Rendering and data communications

W3C XML 10 httpwwww3orgTRREC-xml

Rendering and data communications

W3C XMLHTTpRequest

httpwwww3orgTRXMLHttpRequest

JavaScript Communications for Client

W3C WAI-Aria Version 10 httpwwww3orgTRwai-aria

Accessibility Screen Reader integration

W3C WCAG 20 AA httpwwww3orgTRWCAG Accessibility

JCP JSR286 httpwwwjcporgenjsrdetailid=286

Portlet Integration

OASIS WSRP20 httpdocsoasis-openorgwsrpv2

Portlet Integration

ECMA JavaScript ECMAscript-262

httpwwwecma-internationalorgpublicationsstandardsEcma-262htm

Client processing

IETF HTTPS RFC-2828 httpstoolsietforghtmlrfc2818

Secure web traffic

IETF SSL 30 RFC-6101 httptoolsietforghtmlrfc6101

Communications on clients for UI and mail

Capabilities of Siebel CRMOpen UI Siebel when used with Open UI can meet the following general and industry specific Mandates

Common Criteria Certification Evaluation Assessment Level 2

More information can be found at httpwwwcommoncriteriaportalorgfilesepfilesst_vid3026-vrpdf

for additional information

Portal Standards

Open UI supports portal integration

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 37: Siebel Open UI Best Practices - Deployment Guide v1.34h

37

bull JSR286 Siebel Open UI is integrated as an iframe This allows it to be hosted inside the JSP portion of a JSR286 portlet In this integration style it can be addressed via the URL using Open UIrsquos component architecture for rendering components of the UI rendering hierarchy data and focus context Data is typically returned using web services

bull WSRP20 WSRP20 compliant portlets can be surfaced using native iframes generated by Siebel and as such are standards based portlets

FIPS-140-2 standard

Siebel Open UI can be implemented to meet FIPS-140-2 standard

Open Web Application Security Project (OWASP)

Oracle participates in OWASP to meet security challenges in the enterprise

Oracle Software Security Assurance (OSSA) guidelines and policies

Siebel participates in the Oracle OSSA effort

Participant

Payment Card Industry Data Security Standard (PCI-DSS)

Compliant (with configuration) httpswwwpcisecuritystandardsorgsecurity_standards

Accessibility and VPAT

WCAG 20 AA Compliant (where practical and advisable) to theW2C WCAG AA Guidelines

Section 508 compliant (where practical and advisable) to the section 508 mandate

VPAT information

As other software products Siebel Open UI contains specific quality defects both for accessible and non-

accessible users Oracle maintains a list of accessibility related defects in Open UI and can provide a

sample of the type of issues that are considered most severe at any given time to covey the level of

adoption of accessibility features Oracle will provide a VPAT for Siebel Open UI

Oracle strongly recommends use by accessibility users to meet user acceptance of accessibility features

as this is the most practical method of testing the application for accessibility and encourages customers

to make sure that the user population understands WAI aria accessibility tools prior to testing Siebel

Oracle welcomes any feedback on accessibility related features and user experiences

VPAT documenting details of WAI-ARIA and WCAG20AA compliance will be published at

httpwwworaclecomuscorporateaccessibilityvpatsvpats-siebel 162956html starting with

release 81110FP8223FP

Compliance for accessibility standards for all Oracle applications is detailed at httpwwworaclecomuscorporateaccessibilityvpatsindexhtml

EU privacy directives

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 38: Siebel Open UI Best Practices - Deployment Guide v1.34h

38

EU mandates strong rules around use of cookies

httpwwwicogovukfor_organisationsprivacy_and_electronic_communicationsthe_guidecookies

aspx Siebel uses session cookies to track the security of the established connection Siebel Open UI

requires use of cookies to function properly

Infrastructure Capabilities

IPV6

Note It is recommended that you use the host name instead of the IP when configuring Siebel

applications in environments that use IPV6 and IPv4 in a dual-IP-stack configuration

IPV6 Support for Servers

Siebel Business Applications interoperate with IPV6 for use with Siebel Server infrastructure using dual

stack combinations Siebel Server implementations may be in an IPv6-compliant network environment if

the network stack also supports an IPv4 stack IPv6 is transparent to Siebel applications if it is installed

on the web server and is only typically needed on the web server This support provides IPv6

connectivity for customer-facing web sites while also using IPv4 for communication across the DMZ to

the intranet

IPV6 Support for Clients

SI clients and Open UI clients can be implemented on a native IPV6 stack without use of IPv4 HI clients

and Siebel Remote and other client windows specific code requires IPV4 used with IPV6 in a dual stack

configuration

Lightweight Directory Access Protocol and Active Directory Services Interfaces

LDAP directories can run on a different server than the Siebel Server or the Web server The LDAP server

servers used must comply with

LDAP 30 standard and IETF Draft Password handling support

Password handling is not required (password expiry and other password-messaging features)

Vendors who provide directory server products that support the LDAP 30 standard include Oracle IBM

Microsoft and Novell

Oracle provides Active Directory support that requires the native connector shipped with the operating

systems that are supported for Siebel applications on Microsoft Windows servers Siebel Active

Directory support is limited to specific active directory connectors supported within Siebel

SAML and Single Sign-On

SAML is supported via SSO integration SSO typically requires third party products such as Oracle Access

Manager or a third party equivalent Information on such integrations can be found at

Siebel SSO Integration with Third Parties (Doc ID 15090841)

Siebel SSO Integration with OAM (Doc ID 15093381)

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 39: Siebel Open UI Best Practices - Deployment Guide v1.34h

39

Third-Party products in Open UI The following components contain third-party components For detailed information on these

components for reuse or features please go to the referenced links

Table 6 Third Parties

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Calendar Adam Shaw Full Calendar Equivalent features

Rich Text EditorHTML Editor CKEditor

Supports both HTML and Rich Text provides a series of new configurable features

Browser History historyjs Supports browser Back Forward buttons

Menu selection

John Resig httpjquerycom Aegis Accessibility

Eliminates duplicate features supports keyboard use and accessibility

Tooltips

John Resig httpjquerycom Aegis Accessibility

Used for keyboard use and accessibility

Tabs

John Resig httpjquerycom Aegis Accessibility

Supports dynamic resizing keyboard use and accessibility

Dialogs and Custom Rendered Popups

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Tree Control

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Checkbox

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Buttons

John Resig httpjquerycom Aegis Accessibility Supports keyboard and accessibility

Date picker Date features

John Resig httpjquerycom JQuery UI Supports keyboard and accessibility

Drag and Drop

John Resig httpjquerycom JQuery UI

File upload controls support drag and drop

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop

Page 40: Siebel Open UI Best Practices - Deployment Guide v1.34h

40

FeaturePurpose

Delivery Vehicle Vendor Name Package Name Supplier of Feature Components Open UI Features

Resizing Selection Sorting

John Resig httpjquerycom JQuery UI

Now supported via standards compatible with accessibility

Calculator Keith Wood httpkeith-woodnamecalculatorhtml

Supports additional features such as percentages keyboard use and accessibility

Spellcheck Native browser feature based

Now supported natively via browser (IE requires plug-ins to support spellcheck)

Zoom Native browser feature based

Zoom features are now fully supported via browser

PrintPrint Preview Native browser feature based

Print and print preview use native browser print dialog box

Browser bookmarkinghistory Native browser feature based

Browser history is fully supported with browser Forward and Back buttons enhanced features in HTML5

Charts Netcharts Same function

Grid View

Tony Tomov wwwtrirandcomblog JQuery Grid

Supports arrow key navigation tabshift tab and accessibility

Time Picker Time Features

Trent Richardson httptrentrichardsoncom JQuery UI time picker add on Supports keyboard and accessibility

File upload and download

Sebastian Tschan httpsblueimpnet JQuery File Upload Plugin Multiple file drag and drop