Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Product Configurator Server ComponentsSiebel Product Configurator allows users to interactively configure customizable products when ordering or when generating a quote. Siebel Product Configurator uses a constraint-based solution engine that resides on the Siebel Server called the Constraint Engine. This engine evaluates customer choices and generates product configurations that conform to business rules. For more information about using, installing, administering, and tuning Siebel Product Configurator modules, see:
Remaining topics about Siebel Product Configurator in this chapter include: Siebel Product Configurator ComponentsSiebel Product Configurator is supported in the Siebel Server environment by the following components:
Siebel Product 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 Product Configurator parameters, and where to set them, are described, a brief overview is presented of the Siebel Product Configurator architecture and of the various services in a Siebel Product Configurator deployment. Figure 5 shows detailed Siebel Product Configurator architecture and the interaction of various services with each other during run time. The important services depicted in Figure 5 are as follows:
For more information about elements of Siebel Product Configurator's internal architecture, including the Instance Broker and the Configurator Object Broker, see Siebel Product Administration Guide. Siebel Product Configurator Architecture for Oracle Constraint Technology IntegrationAn Oracle Constraint Technology integration for Siebel Product Configurator is available as an alternative way to deploy Siebel Product Configurator. For the current release, such an integration is in developer preview status only. Deploying this type of integration requires the following modules:
NOTE: In the context of this type of integration, the Siebel Constraint Engine as discussed here is completely different than the Constraint Engine used by the traditional Siebel Product Configurator offering. (Most of the information about Siebel Product Configurator in this guide pertains to the traditional offering.) For information about installing and configuring the Siebel Enterprise Cache and the Siebel Constraint Engine, see Siebel Installation Guide for the operating system you are using. See also Article ID 2112562.1 on My Oracle Support. For more information about using Siebel Product Configurator, see Siebel Product Administration Guide. Locale-Related Requirements for Remote Siebel Product 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 Product 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 Product 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 Product 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 Product 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 © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |