Siebel Product Configurator Server Components

Siebel 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:

Siebel Product Administration Guide
Siebel Installation Guide
Siebel System Administration Guide
Siebel Performance Tuning Guide

Remaining topics about Siebel Product Configurator in this chapter include:

Siebel Product Configurator Components

Siebel Product Configurator is supported in the Siebel Server environment by the following components:

Application Object Manager. The Siebel Product Configurator solution engine is called by the Application Object Manager, such as Call Center Object Manager (SCCObjMgr_lang, such as SCCObjMgr_fra for French) for Siebel Call Center.
Siebel Product Configuration Object Manager (alias eProdCfgObjMgr_locale). This is a special-purpose Object Manager component suitable for some Siebel Product Configurator deployments. For convenience, the component alias is generally referred to in this guide as simply eProdCfgObjMgr. This component contains the Siebel Product Configurator solution engine. It can be deployed on a separate Siebel Server from where Siebel Product Configurator sessions are invoked.
The Siebel Product Configurator server in this type of deployment is also referred to as a remote or dedicated Siebel Product Configurator, which works in coordination with the invoking Application Object Manager. See later in this topic for locale-related requirements for a remote Siebel Product Configurator component.
Siebel File System. This component stores cached object definitions for customizable product definitions in the CFGCache directory on the Siebel File System.

Locale-Related Requirements for Remote Siebel Product Configurator Components

The 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:

Change Locale Code to ENU in order to work with a remote Siebel Product Configurator component named eProdCfgObjMgr_enu.
Create a remote Siebel Product Configurator component named eProdCfgObjMgr_eng.

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.