Siebel Applications Administration Guide > State Models >

Activating State Models

This topic provides information about activating state models.

How Are State Models Activated?

A new state model is not available to users until you start a new Siebel Application Object Manager server process. By restarting the server or the AOM server components, you start new AOM processes that obtain the new state model from the refreshed state model cache.

How Are State Models Activated for Mobile Users?

For mobile users who connect through Siebel Remote, the state model is available after a user synchronizes with the database server. State models are supported on regional nodes. For more information about support for regional nodes, see Siebel Remote and Replication Manager Administration Guide.

How Are State Models Enforced?

State models are enforced on the Siebel business logic level. Thus, state models are enforced for updates that you make through Siebel Visual Basic, Siebel eScript, and workflow processes. However, state models are not enforced for updates that do not go through Siebel Application Object Managers, such as updates that you make through Enterprise Integration Manager (EIM) or workflow policy programs.

How the AOM Reads State Model Objects

The AOM reads state model objects from the run-time database, not from the compiled Siebel repository file (SRF).

NOTE:  If you distribute state models to other environments, migrate the run-time database tables for the state model (and distribute the SRF file).

This task is a step in Process of Setting Up State Models.

To activate state models

  1. Perform one of the following actions:
    • Restart the server.
    • Restart the AOM server components.
  2. Clear the browser cache.
Siebel Applications Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.