| Bookshelf Home | Contents | Index | PDF | |
|
Siebel System Administration Guide > Configuring Siebel Servers > About Siebel System ParametersThe 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, unless the value is overridden at a lower level. If a change is made to that parameter at the enterprise level, then this value is inherited down to the lower levels. Table 17 lists 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, then the new change does not inherit down to the lower level unless the override is deleted at that lower level. NOTE: Do not set lower-level parameters to a blank or empty value. To negate a parameter value, use the appropriate 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 that are to affect this level must be made at this level unless you delete the override. 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 by using the expression File* returns the result Siebel File System, because the parameter's alias is FileSystem. Table 17 lists the parameter-setting levels in order, from highest to lowest. Named subsystem parameters can apply to entities at different levels.
This topic contains the following information:
Related Topics |
 |
|
| Siebel System Administration Guide | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |