Where is cfg file in siebel




















Although some sections are of importance for the server, most of the information is derived from component parameters or server parameters. This is provided from a vanilla Siebel install to the F: drive.

A string enclosed in square brackets indicates a section. Anything under that he said to be part of the same section. Although CFG is quite a long file and has made things going on in there, Siebel developers are typically interested in specific sections and details. This is the core section of the CFG file that is placed at the very beginning. It has the following important parameters. You can have as many data sources as you like, and you need to specify all of them in this section.

For database authentication, specify DB. DB is the default value for SecAdptMode. Specifies the name of the security adapter. For database authentication, specify DBSecAdpt. You must add the applicable section to the file yourself.

This parameter applies only to the Siebel Developer Web Client. It specifies the path to a configuration file that contains only parameters for a security adapter, that is, it contains parameters as they would be formatted if they were included in a section such as [LDAPSecAdpt] in an application's configuration file. Parameters in [DBSecAdpt] Section The following parameters are located in the [DBSecAdpt] section or equivalent of the application configuration file, if you are configuring the database security adapter.

Use this parameter to implement checksum validation, in order to verify that each user gains access to the database through the correct security adapter.

This parameter contains the value calculated by the checksum utility for the applicable security adapter DLL. If you leave this value empty, the system does not perform the check. If you upgrade your system, you must recalculate and replace the value in this parameter. When an administrator then adds a user or changes a password from within Siebel Business Applications, or a user changes a password or self-registers, the change is propagated to the database.

The file extension does not have to be explicitly specified. For example, sscfsadb. Specifies the data source applicable to the specified database security adapter. I hope it clarifies your confusion. Dont know exactly what do you mean by saying Recompile but while compiling you need to be sure with the path you are providing for. Although when u recompile an SRF used by open instance still there are chances that one of the instance is active in background which Siebel Compiler is unable to exit from.

As a workaround Go to Task manager and kill all Siebel. It is working, one way as u said, and the other way i removed the exixting and freshly recompiled once again. It is the cfg file which provides the location of srf file which is nothing but just the compiled version of your repository.

Enter application functionality is dependent upon the srf file but its location is specified in cfg file. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account.

We'll send a magic link to your inbox. Email Address.



0コメント

  • 1000 / 1000