Oracle Self Service Web Applications (SSWA)

SSWA architecture

The Oracle Self-Service Web Applications, including Self-Service Expenses, Self-Service Human Resources, Internet Procurement, Internet Receivables, Self-Service Time, Web Suppliers, iStore, iPayment, iSupport, iMarketing, and eTravel from Oracle, extend the functionality of Oracle Applications by adding a browser-based, walk up and use functionality that supplements Oracle Applications

Oracle HTTP Server

SSWA can be either inquiry or transactional. Inquiry modules read but don't update the Oracle Applications database; transactional modules update the databases.

1. Webserver receives the user request for the particular port number. Web server Binds the request with the port number

2.Based on the cookie webserver serves the request by sending login page

3. The application user name and password is entered by the user(operations/welcome)

4. The application user login session is validated by connecting to Applsyspub/pub. Applsyspub contains application user session ,invalid logins,security related tables. The user & security is validated here

5. The responsibility page is displayed. User selects a particular responsibility

6. The responsibility and application name is validated by connecting to Applsys schema(fnd_Responsibility, fnd_application.......)

Note: Here we should remember the difference between applsys and apps schema. Applsys schema contains ad,fnd objects whereas apps schema is a global schema contains all application objects.

7. Once the application is validated , Connecting to apps schema to get access application tables. This is the reason why we should have apps and applsys passwords should be same

8. Once a particular form is selected the .dbc file is accessed to get the information about the GUEST username/pwdDisplaying Information Accessed from Servlets and Java Server Pages .