| Siebel CRM Deploying Siebel Open UI Siebel Innovation Pack 2017, Rev. A E54321_01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM Deploying Siebel Open UI Siebel Innovation Pack 2017, Rev. A E54321_01 |
|
Previous |
Next |
View PDF |
This topic describes some of the characteristics of the server environment in a Siebel Open UI deployment. It contains the following information:
Siebel Open UI is the most secure Siebel CRM client to date, with the following characteristics:
Limited attack surface. Siebel Open UI uses only three technologies to render the client code: HTML, CSS, and JavaScript. Because of the small set of underlying technologies that are used to render the client and the absence of third-party plug-ins such as ActiveX and Java, Siebel Open UI provides the smallest possible attack surface.
Transparent technology. Because the Siebel Open UI client is built entirely on standards, a variety of modern inspection tools can be used to validate the security compliance of your implementations.
Compatibility with Data Execution Prevention features and virtualization. Because the Siebel Open UI client is a scripted client, it is fully compatible with Data Execution Prevention features for software or hardware, and compatible with virtualization features. The Siebel Open UI client supports a variety of techniques for implementing secure environments.
Secure sessions and limited concurrency. The Siebel CRM server environment provides sophisticated session security for a secure user experience. To protect data integrity and system security, concurrent browser sessions are not supported for Siebel CRM applications. When this condition is detected, the application provides options for how to proceed.
FIPS-140-2. Siebel Open UI supports the FIPS-140-2 standard, with applicable configuration.
Common Criteria Certification. The Siebel CRM applications meet Common Criteria Certification, to Evaluation Assessment Level 2. For more information, see the following:
http://www.commoncriteriaportal.org/files/epfiles/st_vid3026-vr.pdf
Oracle tests JavaScript controls from third parties according to the same rigorous standards as those for testing Oracle code. Because all of the client code is standards-based and well-understood by inspection tools, thorough testing is simplified. Oracle uses industry-leading Web application security assessment solutions to validate that the Siebel Open UI client is secure. Oracle also validates security through its security-architecture teams and its internal oversight organizations and works with the ethical hacking community to put code to the practical test of security.
Oracle takes part in Open Web Application Security Project (OWASP). Developer training provided by Oracle Software Security Assurance (OSSA) is in line with the guidelines and recommendations provided by OWASP documentation. All Oracle product development teams are mandated to follow OWASP guidelines, policies, and secure coding standards.
This topic is part of "Siebel Open UI Server Deployment Characteristics".
Related Topics
"Implementation Differences Related to Browsers"
Related Books
Siebel Security Guide
Siebel Security Hardening Guide
When deploying Siebel Business Applications across a firewall, make sure that the firewall supports the HTTP 1.1 protocol. Using HTTP 1.0, although it is supported, results in reduced performance. If the firewall or proxy server does not fully support HTTP 1.1, then make sure of the following:
HTTP compression is disabled.
The firewall proxy is able to handle cookie wrapping or other proxy-specific features that enable cookie handling and forwarding.
Headers passed to the Siebel Application Interface do not contain HTTP 1.1 protocol content. You can automate this by setting the proxy server to strip out HTTP 1.1 header content.
This topic is part of "Siebel Open UI Server Deployment Characteristics".
Related Books
Siebel Installation Guide for the operating system you are using
Siebel Security Hardening Guide
In support of reduced network traffic, the Siebel Open UI client supports the following new features:
Partial refresh. This feature allows only distinct regions of the UI to be refreshed, rather than the entire screen. This feature saves network bandwidth.
Push notifications. This feature eliminates polling for Siebel Communications Server messages, such as for computer telephony integration (CTI) and other types of messages.
These features improve bandwidth requirements and in some cases reduce power consumption on mobile devices, by reducing chattiness. Siebel CRM can run on modern wired or wireless networks, and it supports use over low-bandwidth connections.
This topic is part of "Siebel Open UI Server Deployment Characteristics".
Related Books
Siebel CTI Administration Guide
The Siebel Open UI client uses interpreted JavaScript to render the client, which performs extremely well on modern browsers. Features such as partial refresh supporting greater granularity and efficient updating of user interface regions, and improved asynchronous operation, improve performance characteristics in specific use cases of the client.
In order to work on a variety of platforms, Siebel Open UI runs on code that is interpreted or JIT (just-in-time) compiled in the browser. Differences in performance depend on customization of the interface when you run cross-platform code that is inherent to Siebel Open UI.
This topic is part of "Siebel Open UI Server Deployment Characteristics".
Related Topics
A Web application can render content beyond the limits of the data displayed on the screen, effectively increasing the amount of work done to render content without any user benefit. It is recommended to build user interfaces that render only content in the visible area of the user interface. Large rendered surfaces, the interpreted nature of the application, and the ability to adjust application functionality can compound and reduce the performance and response times of the user interface. It is recommended that you review the deployment with a focus on optimized content.
In light of these considerations, review the following recommendations:
Minimize the number of applets in a view. It is recommended both from a performance and usability perspective not to add more applets to a screen than the typical user can view or work with without scrolling. Scrolling interrupts work and does not work well on some mobile devices, and the content that is not displayed still must be rendered when the screen is refreshed.
Minimize the number of displayed columns in a list view. Consider limiting and setting reasonable defaults for the number of columns available for list views. For most computer desktops, no more than seven columns should be displayed by default, as a rule of thumb. Even hidden components have to be processed by the rendering engine.
This topic is part of "Siebel Open UI Server Deployment Characteristics".
Related Books
Siebel Performance Tuning Guide
Siebel Open UI tries to hide specific differences in rendering between browsers within the user interface, but some browser-specific differences exist. Customers are encouraged to identify differences in rendering and to choose browsers based on the best usability offered. Examples are provided in this topic.
This topic is part of "Siebel Open UI Server Deployment Characteristics".
Use of Popup Blockers
Siebel Open UI is compatible with popup blocker use. Make sure that Siebel application servers and third-party iFrames are whitelisted or excluded from blocking by popup blockers. For more information about configuring Siebel Business Applications for popup blocker compatibility, see the Siebel Installation Guide for the operating system you are using.
Impact of Browser Dynamic Patching of Browsers
Two basic strategies exist for managing your browser version:
Lock browsers to specific versions. Although locking your browser version mitigates the risks of introducing regressive interactions into the Siebel CRM environment, this approach introduces the risks of not patching imperfect browser code and does not help in addressing functional and security fixes in browsers.
Dynamically update browsers. It is strongly recommended to mitigate browser-related functional and security risks by allowing browsers to update dynamically. If regressive interactions occur, then Oracle and the browser vendors are committed to addressing these in a timely manner.
Validation Services for Standards Compliance
To validate Siebel application pages and the browser you are using against W3C standards, you can use any of several validation services, including the following:
W3C markup validation:
HTML 5 validation:
CSS validation:
Lint, JSLint and derivative programs:
Tabbed Browsing
Tabbed browsing is supported with Siebel Business Applications for one active session. Multiple Web pages can be opened using tabbed browsing. However, only one tab can have a live connection to a Siebel application at a given time. Using multiple browser tabs uses more resources and therefore can affect client performance.
Language Support
In general, language support for Siebel Open UI is similar to language support provided in previous versions on the traditional clients. For Siebel language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support. See also Siebel Global Deployment Guide and Siebel Installation Guide for the operating system you are using.
This topic is part of "Siebel Open UI Server Deployment Characteristics".
