Product Administration Guide > Siebel Configurator Technical Reference >

Siebel Configurator Architecture

The key components of the Siebel Configurator architecture are as follows:

• Object Manager. All services that run within a Siebel application are bound by the Object Manager they are running within. The same applies to all caches as well. Therefore services cannot be shared across object managers and neither can cached objects.
• UI Business Service. The UI Business service is used by Siebel Configurator to render the UI. The UI business service binds the structure of the customizable product to the Web templates and submits them to the Siebel Web Engine for rendering to the client browser. The UI service is the means by which the user interacts with Siebel Configurator. A unique instance of the UI service is required for each user.
• Instance Broker. The Instance Broker is a service that interacts with the UI Business Service. The Instance Broker maintains all the information about the current instance of the customizable product that the user is configuring. The Instance Broker interacts with other services in response to user requests during a configuration session.
• Object Broker. The Object Broker is a service that extracts the customizable product definition from the database for use by other Siebel Configurator services.
• Config Services. Config Services consists of factories.
• Factory. A factory is a service that translates the customizable product definition retrieved by the Object broker into a format the worker can understand.
• Constraint Engine. The Constraint engine is also called the worker. It is also referred to as the Siebel Configurator engine.
• Worker. The worker is a service that computes solutions and enforces all the constraints associated with the configuration. This includes the declarative portion of the customizable product plus constraints added by the user (user picks).