SIEBEL USER REQUEST FLOW

Siebel Web Client (thin client) High Level overview:

1) Request from client goes to Web sever 
2) Web server will send the request to SWSE 
3) SWSE will refer to eapps.cfg for particular application 
4) example: application emedical_enu will have connect string details in eapps.cfg 
5) Connect string will be used to connect to Siebel Server based on load balancing used. there are two options for load balancing 1) Siebel native load balancing(lbconfig.txt) 2) third party load balancing 
6) SCbroker component will receive the request in siebel server from Web Server. 
7) SCbroker will send the request to AOM component 
8) Based on Authentication mode used. AOM will decide to whom the request should be sent 
9) example: if Authentication mode is Database then request will be sent to Database. 
10) database will authenticate the user if authentication mode is database and based on the position and responsibility of the user. user will be given access to data and application views.