Monday, 1 April 2013

Different Files and their usage in Siebel

There are number of files that we come across in Siebel and we don't have idea about their usage and role in our application.
Here in this post we will discuss about all the important files.
  • Siebel_sia.srf
  • eapps.cfg
  • eapps_sia.cfg
  • gateway.cfg
  • diccache.dat
  • Enterprise_server.shm file
  • application.cfg
  • lbconfig.txt
  • Siebns.dat
Siebel_sia.srf
Siebel SRF file also known as Siebel Repository File (SRF) is a compressed, read only file that contains compiled version of Siebel repository. So all the object definitions and scripts that are defined in Siebel Tools are compiled into one single file which is will be used by Siebel Application at run time.
This SRF file is normally at "\root\siebsrvr\objects\enu” with the file extension srf. It is very important that the active Siebel Repository should always be in sync with the SRF.

Please do not get confuse between Siebel repository and Srf file.
The main difference between Repository and SRF is that Repository is the collection of all Siebel Object Definitions in a user readable/editable form. It is stored as database records in one or more Repository tables (S_Repository). Now when these object definitions are compiled through Siebel Tools, the resultant file is the SRF.Now this also contains all the object definitions but as a flat file which will be read at run time.
 eApps.cfg
eapps.cfg is one of the most important file used in Siebel Application.Here we discuss different section contained in eapps.cfg file and what effect they can make in siebel application.
The eapps.cfg file is located in SWSE_ROOT\bin, where SWSE_ROOT is the SWSE installation directory.

[swe]

Language      = ENU
Log           = errors
LogDirectory  = E:\sba81\SWEApp\log
ClientRootDir = E:\sba81\SWEApp
SessionMonitor  = False
AllowStats      = true
LogSegmentSize  = 0
LogMaxSegments  = 0
DisableNagle    = False

Log

Log parameter defines the detail in which we can generate log related to swe error.It can have other values such as Details.e.g. Log = Detail.
LogDirectory
This parameter defines the location of the log directory, whose default location is \SWEApp\LOG (WINDOWS)
ClientRootDirectory
This is the location of SWSE plug-in installation, whose default location is SWEAPP_ROOT.
SessionMonitor
Use this parameter to determine whether to gather statistics on all current sessions and report them in the SWSE stats page. To enable session monitoring, set SessionMonitor to TRUE.
We can view stats page in url by appending _stats.swe
http://url/app_enu/_stats.swe
LogSegmentSize
This parameter determines how large a segment of the log file is in kilobytes. If you set this parameter to 5, the log segment will be 5 KB in size. A value of 0 turns off segmentation.

[ConnMgmt]

EnableVirtualHosts = true
VirtualHostsFile   = E:\sba81\SWEApp\admin\lbconfig.txt

Enable Virtual Hosts = True makes load balancing true for the application.

VirtualHostsFile describes the location of the lbconfig.txt file which have the configuration of load balanced servers.

[defaults]
EncryptedPassword = True
AnonUserName  = GUESTERM
AnonPassword  = #######################
StatsPage     = _stats.swe
HTTPPort      = 80
HTTPSPort     = 443
EnableFQDN          = TRUE
FQDN                = ################################
TrustToken          = 
DoCompression       = true
GuestSessionTimeout = 300
SessionTimeout      = 3420

This section is most important section of this file.

EncryptedPassword 
If the parameter is TRUE, then the password parameter values must be encrypted, and if the parameter is FALSE, then the passwords must not be encrypted.
if the EncryptedPassword parameter does not exist in the eapps.cfg file, then the default behavior is the same as if EncryptedPassword is set to FALSE.
encryptstring.exe utility is use to encrypt the plain text which is available at /siebsrvr/bin.
AnonUserName
This parameter specifies the user name required for anonymous browsing and initial access to the login pages. The user name selected should have access to views intended for anonymous browsing.
AnonPassword 
This parameter specifies the user name password required for anonymous browsing and initial access to the login pages. 
When user first enters the URL of siebel Application,Login page comes only after the authentication of AnonUserName otherwise Server busy error will come.
HTTPPort 
The HTTP port used for Web browser communications. The default setting is the standard port of the Web server in use (80).
HTTPSPort
The HTTPS port used for secure Web browser connections. The default setting is the standard port of the Web server in use (443).
FQDN
Stands for Fully Qualified Domain Name. An example of a fully qualified domain name would be http://oradev.oracle.com.If the Web server receives a request for a URL that does not contain the full domain name, the FQDN setting causes the browser to reissue the request and to add the domain name.
For example,If we hit the URL with IP name http://10.1X.XXX.XX9/app_enu and Enable FQDN =True then it will convert URL to one specified with FQDN parameter.
DoCompression
Specifies whether the SWSE will compress HTTP traffic.Compressing HTTP traffic, where it is feasible to do so, substantially reduces bandwidth consumption.
GuestSessionTimeout
The time, in seconds, that a connection open for anonymous browsing can remain idle before it times out. The default is 300 seconds (5 minutes).Guest sessions are used for anonymous browsing. They permit users to navigate portions of the site without logging in. In contrast to anonymous sessions, guest sessions are associated with an individual Siebel Web Client. These sessions are opened when an unregistered user starts navigating the site, and they remain open until the Web client logs out or times out due to inactivity.
SessionTimeout
The time, in seconds, from the user's last browser request until the user's connection times out. The default is 900 seconds (15 minutes).Standard sessions are those where users log in using their registered user name and password.
eApps_sia.cfg

The file eapps_sia.cfg is included by eapps.cfg, and extends its functionality by specifying connectivity information for AOMs.

[/app_enu]
ConnectString = siebel.transport.encryption.compression:\\server:server_port\enterprise\AppObjMgr
WebPublicRootDir = E:\sba81\SWEApp\public\enu
SiebEntSecToken = P94################
where ConnectString has format


transport = Networking transport protocol such as TCPIP
encryption = Encryption type such as RSA
compression = Data compression method.
server = IP address or hostname of the Siebel Server (or in the load-balanced case, the virtual IP address as VirtualServer).
server_port = Port number on which the Siebel Connection Broker component (alias SCBroker) runs.By Default it is 2321.


SiebEntSecToken
This is the password used by the Siebel Administrator to refresh application images from the Siebel Server on the Web server without restarting.
gateway.cfg

The gateway.cfg file contains the configuration parameters that determine how access to the
Gateway Name Server is authenticated.

[DataSources]

ServerDataSrc       = ServerServerDataSrc(The data source used when database authentication is enabled)
LDAPSecAdpt        = LDAP(The data source used when LDAP authentication is enabled)

[ServerDataSrc]
Docked                   = TRUE
ConnectString            = Enterprise_DSN
TableOwner               = SIEBEL
DLL                      = sscdo90
SqlStyle                 = OracleCBO
MaxCachedCursors         = 16
MaxCachedDataSets        = 16
ReverseFillThreshold     = 100
FileSystem               = /siebelfs
GatewayAddress           = ############
EnterpriseServer         = Enterprise Name














3 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. Hi, I need help in finding out the configuration files for each and every component of Siebel. Can you please help me?
    Thank You!
    Regards,
    Hari.

    ReplyDelete
  3. All info for component related will be present in siebns.dat file take a copy of this file locally and you can see config parameters of each component.
    Or can go to Admin server configuration -- > Component definition screen can check through UI as well.

    ReplyDelete