Applies to:Product Release: V7 (Enterprise)
Version: 126.96.36.199  Fin Svcs
Database: IBM DB2 8.1 FixPack 3
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1188294952.
1. Is it possible to use a LogDirectory in eapps.cfg which is not under install directory? If yes, are there changes other than in eapps.cfg that need to be made? When we change the parameter and restart the web server, the log still goes to the install directory/log location.
2. How do we separate the public\enu location from under SWE install directory, so that the software location is different from logs and public\enu files?
The Customer was looking for more information surrounding the possible re-location of the Siebel Version 7.5.3.x SIA (Industry Apps - Financial Services) Web Server Extension (SWEApps) '*.log' files ? The Customer had specifically changed some entries in the [SWE] Section of eApps.cfg Configuration File, for example previously LogDirectory = d:\sea752\siebsrvr\sweapp\log folder - now the LogDirectory = /app01/apoinfamw/log. However, this had no affect and the SWEApp '*.log' files were still being written to the <Siebel_Server_Root>\SWEApp\Log directory ?
Following on from my research and investigation, I discovered that the Customer had encountered known defective product error behavior for which Change Request Number 12-DMK3DZ has been raised to address. For more information, please see Service Request Number 38-822934860 available out on SupportWeb. This Change Request has been targeted for the Siebel Version 7.7.x product release. The Customer also asked if these SWEApp '*.log' files could be separated out from the SWEApp\Public (ENU) folder containing the products Binaries (BIN) and HTML Web Applet Template files ?
I have raised Product Enhancement Change Request Number 12-JPIX4O to address this requirement.
Keywords: SWEApps, log, files, changing, directory, structure, Web, Applet, Templates, Binaries