Siebel Product Administration Guide > Siebel Configurator Web Templates >

About Customizing Configurator Templates for Open UI

The Open UI framework for Configurator uses the following architecture, as you can see in Figure 13.

Figure 13. Siebel Product Configurator Architecture

The Siebel Web Templates function as follows:

• Open UI uses <DIV> and <CLASS> tags to replace the <TABLE>, <TR>, and <TD> tags UI attributes.
• Open UI removes the inline scripts embedded with <SCRIPT> tags.

In the Object Manager (written in C++), Open UI functions as follows:

• The applet (Cfg Cx Runtime Instance Frame (JS HI)) is the only point of communication. All requests from the client (browser) are delegated through it.
• There is no longer server generated JavaScript. Necessary data is packaged into a payload so that the client model renderer can process it and generate proper scripts.

In the client (browser), Open UI functions as follows:

• ConfiguratorPM (cfgpmodel.js) is extended using the PresentationModel (pmodel.js) architecture of Open UI. It maintains the product instance changes and handles the communication between the UI and the Server.
• ConfiguratorPR (cfgrenderer.js) is extended from PhysicalRenderer (phyrenderer.js) architecture of Open UI. It handles the rendering and evaluating of UI elements from ConfiguratorPM.

Customizations of Web Templates must use libraries that have been extended to accommodate the extended PresentationModel or Renderer. These extended libraries are also compliant with Open UI's architecture.

All customizations are placed in extended libraries for easier upgrades.