| Bookshelf Home | Contents | Index | PDF | ![]() |
|
Configuring Siebel Open UI > Mapping Server Objects to Client Code > Configuring the Manifest File > Overview of the Manifest FileThe core_manifest.xml file is a file that contains rendering keys. Siebel Open UI uses these rendering keys to identify the JavaScript files that it must download to the client.The Siebel Web Engine gets the JavaScript implementation file information from the Manifest File the first time a user accesses a view or applet during a user session. To get this information, it looks up the rendering key for this view or applet. If you must customize the JavaScript files that Siebel Open UI uses to render a view or applet, then you must modify the custom_manifest.xml file. You must not modify the core_manifest.xml file unless this book directs you to do so. If you modify the core_manifest.xml file for any reason, then it is recommended that you make a back up copy of this file before you modify it. You can then use this backup to restore the Manifest File, if necessary. The core_manifest.xml, the custom_manifest.xml file, and the manifest_extensions.map file all reside in the following folders: \\release_number\ses\siebsrvr\OBJECTS\ client_root/objects/language_code C:\23013\ses\siebsrvr\OBJECTS\ For more information about rendering keys, see How Siebel Open UI Identifies the JavaScript Files It Requires to Render a View or Applet. |
![]() |
![]() |
| Configuring Siebel Open UI | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |