Configuration files for Siebel Gateway and Siebel Server

8/04/2012 No Comment

Which configuration files are required for the Siebel Gateway and Siebel Server to start properly?

Generally speaking it is a good idea to secure the entire /gtwysrvr, /siebsrvr, and /SWEAPP/bin directory trees. In addition to true configuration files, there are a number of utility programs and other files that users should not be messing with. When securing these make sure that the account the Siebel services / daemons run under is included in the necessary permissions.

The specific files that are used depends on which application object managers and functionalities you are using. Pretty much any file with a .cfg extension should not be changed without an understanding of what you are doing. The config files primarily reside in the /siebsrvr/bin/[lang] directories. For example, for American English they would be in /siebsrvr/bin/ENU.

A second set of important config files are the eapps.cfg, eapps_fins.cfg, and eapps_sia.cfg files. These are located in /SWE/bin or /SWEAPP/bin. These files control the behavior of the Siebel Web Server Extensions and while they will not prevent the Gateway or Siebel Server from starting, they will prevent connectivity through the web thin client if the settings are incorrect.

Two additional files that can never be edited directly by any use are the siebns.dat file and the .srf file (usually siebel.srf). If these files are corrupted, restoration of the system is very difficult without good backups. The siebns.dat file lives in /gtwysrvr/admin and the .srf file resides in /siebsrvr/objects/[lang].

Finally, there are system or third party files that could cause problems if they are edited inappropriately. These include the vpd.properties file, the odbc.ini file, and any other configuration files specific to your database or webserver being used.
Related Posts


No comments :

 

Aired | The content is copyrighted and may not be reproduced on other websites. | Copyright © 2009-2016 | All Rights Reserved 2016

Contact Us | About Us | Privacy Policy and Disclaimer