Running Your Web-Enabled Application › How Web Option Processes a Request

Previous Topic: Running a Web Option Session

Next Topic: Commands

How Web Option Processes a Request

When you press Enter on a Web Option HTML page, the following processing is invoked to process the request:

  1. The HTTP server receives the request from the browser and calls the Web Option router (as specified in the HTTP Configuration).
  2. The Web Option router retrieves any data entered into input fields on the HTML page, encrypts it and sends it to the Web Option server. It then waits for a response from the Web Option server, containing an HTML page to send to the HTTP server. If it does not receive a response from the Web Option server within the time interval specified in the YRTRMWT Web Option control value, it immediately returns an error page to the HTTP server and ends.
  3. The Web Option server receives the request from the Web Option router and checks if the length of time since this client session last made a request exceeds the YDFTSTO Web Option control value. If so, it immediately returns the YTIMEOUT page to the Web Option router (go to step 9).
  4. The Web Option server decrypts the data entered on the HTML page and converts it into 5250 data-stream format and sends the data to i OS. If it does not receive a response from i OS within the time specified in the YSVRMWT Web Option control value, it immediately returns the YERROR page to the Web Option router (go to step 9).
  5. i OS processes the data and passes it to the application program as if the user had entered the data into the green-screen.
  6. The application program processes the data and displays a new screen (or possibly the same screen with different data or with an error message displayed, and so on).
  7. i OS retrieves the screen data and sends it to the Web Option server.
  8. The Web Option server retrieves the screen data, identifies the screen, merges the screen data with the associated skeleton page (or builds a JIT page if the screen has not been identified), compresses the HTML page and sends the page to the Web Option router.
  9. The Web Option server returns to DEQW status, waiting for further requests from the Web Option router.
  10. The Web Option router receives the HTML page from the Web Option server, decompresses it, passes it to the HTTP server and ends.

The data is passed between the Web Option router, the Web Option server, and i OS through a number of data queues.