Applications Administration Guide > State Models >

Activating State Models

How Are State Models Activated?

Your new state model does not become available to users until a new Application Object Manager (AOM) server process is created. By restarting the server or the Application Object Manager (AOM) server components, you start new AOM processes that obtain your 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 enforced once a user has synchronized with the database server. State models are supported on regional nodes. For more information about support for regional nodes, see the section about restricting mobile client routing in the Siebel Business Process Designer Administration Guide and 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 made through Siebel Visual Basic, Siebel eScript, and workflow processes. However, state models are not enforced for updates made through Enterprise Integration Manager (EIM) or workflow policy programs because these do not go through the Siebel Object Managers.

How the AOM Reads State Model Objects

State model objects are read from the run-time database, not from the compiled Siebel repository file (SRF).

NOTE:  If you are distributing state models to other environments, you need to migrate the run-time database tables for the state model (as well as distributing the SRF file).


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

To activate state models

  • Do one of the following:
    • Restart the server.
    • Restart the Application Object Manager (AOM) server components.
Applications Administration Guide