|Bookshelf Home | Contents | Index | PDF|
The Siebel Open UI client is an alternative to the high interactivity client or the standard interactivity client. Siebel Open UI provides a rich user interface experience, like high interactivity, yet presents many advantages over both high interactivity and standard interactivity. Recent browser versions are strongly recommended, for optimal functionality.
For new installations, you can specify the preferred client user interface, Siebel Open UI or high interactivity, for Siebel CRM applications, using the Siebel Server Configuration Wizard. A similar option is presented in the Siebel Web Client installer, for the Siebel Mobile Web Client or Developer Web Client. For more information, see Configuring the Siebel Server and Installing the Siebel Web Client.
After a new installation and initial configuration, you can change the setting for any of the applications that support both Siebel Open UI and high interactivity, as appropriate for your deployment requirements. In particular, you can do the following:
NOTE: However, Siebel Open UI is enabled after a migration from any prior release in which Siebel Open UI was not supported or was not explicitly enabled or disabled, for any of the applications that support both Siebel Open UI and high interactivity. If you want to revert these applications to high interactivity, then set EnableOpenUI to False.
You can enable Siebel Open UI for applications that currently use high interactivity. Before you do so, it is recommended that you first create corresponding Application Object Manager components that you will deploy using Siebel Open UI. For example, create the components on the same Siebel Server as existing Application Object Manager components that are enabled for high interactivity, and base the new components on the existing ones. For information about creating server components, see Siebel System Administration Guide. For more information about deploying Siebel Business Applications using Siebel Open UI, see Deploying Siebel Open UI. See also Configuring Siebel Open UI.
Check all applicable configuration settings to make sure that they meet the requirements for Siebel Open UI. For example, Siebel Open UI requires the use of session cookies and does not support cookieless mode. You might need to update the eapps.cfg file settings on the Siebel Web Server Extension so that all applications deployed using Siebel Open UI use cookie-based mode. Checking these settings is recommended in all cases, but particularly if you are enabling Siebel Open UI for existing applications, such as after performing a migration installation. For more information, see Siebel Security Guide.
NOTE: For migrated installations, you must also use the Incremental Repository Merge feature before you can run any Siebel CRM applications. For more information, see About Database Updates for the Current Release.
NOTE: User interface references in this guide assume that you are using Siebel Open UI. The Siebel application procedures in this guide assume that you do not use left-hand navigation. However, you can set up left-hand navigation. For more information about left-hand navigation and about implementing it, see Siebel Fundamentals for Siebel Open UI.
This topic is part of Preparing to Run Siebel Server Components.
To use Siebel Open UI with the Siebel Web Client, the Application Object Manager component must have the parameters EnableOpenUI and HighInteractivity set to True. To use Siebel Open UI with the Siebel Mobile Web Client or Developer Web Client, the application configuration file must have these parameters set to True. For applications that currently use high interactivity, HighInteractivity is already set to True.
Siebel Innovation Pack 2014 and later uses a rendering framework called Responsive Web Design that unifies Siebel Open UI rendering across Siebel CRM products. Note that the jQuery Mobile renderers for the Siebel Mobile applications are no longer used. As a result of these changes, after performing a migration installation, such as from Siebel Innovation Pack 2013 to Siebel Innovation Pack 2015, you must perform some configuration tasks if you want to retain any applicable customizations that you had made in the earlier release. For more information, see Configuring Siebel Open UI.
If you retain and update CSS stylesheets from an earlier release, then it is strongly recommended that you remove the Side Menu as a navigation choice for your users, because it is not supported by the earlier stylesheets. For more information, see Siebel Fundamentals for Siebel Open UI.
Where Siebel Open UI is enabled for a Siebel application, to revert to high interactivity (where applicable), you must set the parameter EnableOpenUI back to False. If you do this reversion, then the browser requirements for high interactivity apply again. The browser requirements are described in the Certifications tab on My Oracle Support and in Siebel System Administration Guide.
|Siebel Installation Guide for Microsoft Windows||Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.|