Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Configurator Server ComponentsSiebel Configurator allows users to interactively configure customizable products when ordering or generating a quote. Siebel Configurator uses a constraint-based solution engine that resides on the Siebel Server. This engine evaluates customer choices and generates product configurations that conform to business rules. For more information about tuning Siebel Configurator, see:
Remaining topics about Siebel Configurator in this chapter include: Siebel Configurator ComponentsSiebel Configurator is supported in the Siebel Server environment by the following components:
Siebel Configurator ArchitectureBecause product configuration can sometimes be computationally expensive, the configuration infrastructure provides flexible deployment options to suit different business needs. Topics in this section discuss considerations for choosing among different deployment options. Before the Siebel Configurator parameters are described, and where to set them, a brief overview is presented of the Siebel Configurator architecture and of the various services in a Siebel Configurator deployment. Figure 6 shows detailed Siebel Configurator architecture and the interaction of various services with each other during run time. The important services depicted in Figure 6 are as follows:
For more information about elements of Siebel Configurator's internal architecture, including the Instance Broker and the Object Broker, see Siebel Product Administration Guide. Locale-Related Requirements for Remote Siebel Configurator ComponentsThe three-letter extension to the alias of the Siebel Product Configuration Object Manager component (jpn in the example of eProdCfgObjMgr_jpn) corresponds to the value for the Locale Code parameter (alias LocaleCode) associated with the invoking Application Object Manager. For a remote Siebel Configurator component that you intend to invoke, the name of the component must follow this pattern. The reason for this requirement is that data passed between the invoking Application Object Manager and the remote Siebel Configurator component is in a locale-specific format. If Locale Code on the invoking Application Object Manager is set to a value that does not correspond to a language supported for Siebel applications, then you must either change the Locale Code on the invoking Application Object Manager or create a new remote Siebel Configurator component with the required name. For example, assume the invoking Application Object Manager is SCCObjMgr_enu, but Locale Code is set to ENG rather than ENU. In this case, you must do one of the following:
In addition, note that the Language and Locale Code parameter settings for the remote Siebel Configurator component must match the parameter settings for the invoking Application Object Manager component. For more information about the Language and Locale Code parameters, see Siebel Global Deployment Guide. For more information about creating and configuring server components, see Siebel System Administration Guide. |
Siebel Deployment Planning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |