|Bookshelf Home | Contents | Index | PDF|
The Siebel application uses parameter values based on the level at which they are set. Parameter values at the highest levels are inherited by the same parameter at lower levels. For example, a parameter set at the enterprise level contains the same value for the same parameter at the server and component level. If a change is made to that parameter at the enterprise level, this value is inherited down to the lower levels. See Table 16 for the parameter-setting levels in order from highest to lowest.
If a parameter value is set at a lower level, and a new change is made to the same parameter at a higher level, the new change does not inherit down to the lower level unless the override is deleted at that lower level. See Deleting System Parameter Overrides for information on deleting the lower-level override functionality.
Once you set a parameter at a lower level, this value creates an entry in the siebns.dat file and, from that time on, you must maintain it at this level; that is, any further changes must be made at this level unless the override is deleted.
NOTE: Querying for a specific parameter in either the Parameter field or the Alias field returns matches from both fields. For example, querying in the Parameter field using the expression F* returns the result Siebel File System because its alias is FileSystem.
NOTE: For information on named subsystem parameters, see About Named Subsystem Parameters.
|Siebel System Administration Guide||Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.|