Did this thing ever come into ur mind that why we stop SAS(Siebel Analytics Server) & SAW(Siebel Web Server) in a defined order???
Well it came into my mind… And here is the reason why..
Well it came into my mind… And here is the reason why..
Well first lets talk of whts the order of starting and stopping the SAS & SAW Servers…
Start
SAS -> SAW
Stop
SAW-> SAS
Now, the SAS is started before SAW because if u start SAW and SAS is not started then u wont b able to login into the aplication as the authentication is done through the SAS only. So SAS needs to be started before SAW.
While stopping, SAW is stopped before SAS because, if SAS is stopped before SAW then
1) Users wont be able to query anything or run any report.
2) When we make use of Microsoft IIS Web Server for SAW, in that case the IIS Web Server creates temporary files for its web caching capabilities in the location specified by the Microsoft IIS installation. Now if the SAS is stopped before SAW these temp files remain consuming the disc space.
3) The SAW save backups of the Web Catalog file while the session is running and changes are made in the Web Catalog. As a Shut down process of SAW, the backup file is merged with the Web Catalog and changes are synchd with the original Web Catalog file but when we shut down SAS before SAW then there is a chance that some changes can get missed out.
Start
SAS -> SAW
Stop
SAW-> SAS
Now, the SAS is started before SAW because if u start SAW and SAS is not started then u wont b able to login into the aplication as the authentication is done through the SAS only. So SAS needs to be started before SAW.
While stopping, SAW is stopped before SAS because, if SAS is stopped before SAW then
1) Users wont be able to query anything or run any report.
2) When we make use of Microsoft IIS Web Server for SAW, in that case the IIS Web Server creates temporary files for its web caching capabilities in the location specified by the Microsoft IIS installation. Now if the SAS is stopped before SAW these temp files remain consuming the disc space.
3) The SAW save backups of the Web Catalog file while the session is running and changes are made in the Web Catalog. As a Shut down process of SAW, the backup file is merged with the Web Catalog and changes are synchd with the original Web Catalog file but when we shut down SAS before SAW then there is a chance that some changes can get missed out.
What do u think can there be some other reasons also??
Posts
