In this scenario, a business or department of approximately 50 people wants to move their timesheet system onto their local intranet. This is a very simple application. A user opens a timesheet form on their desktop or from the Web server, completes their weekly time sheet information, including comments, and submits it. The form returns to the server, is processed, and the data and form are stored in a database.
The timesheet form is a simple form, approximately 75 KB in size and approximately 8 MB when stored in memory. It contains one page and 25 items, including a timesheet table that users can add additional rows to. Users are encouraged to access it every day to input their data; however, it is most frequently accessed on Friday afternoons and Monday mornings. Some users have the Viewer installed on their system, and some users do not.
This system has no wireless access and everything is done onsite. The Designer is used to design the blank form. The form is stored on an application server, which also provides a Web page that allows users to access the form. When a user accesses the Web page, Webform Server determines whether the Viewer is installed on the user‘s computer. If the Viewer is installed, Webform Server provides the XFDL form. If the Viewer is not installed, Webform Server translates the form to HTML and JavaScript™. The API and Forms Services Platform process the submitted forms and transfer the data to the database using WebSphere® Transformation Extender.
Note: In this scenario, some users have the Viewer installed on their system and some do not. This scenario could be modified so that no users have the Viewer installed on their system or all users have the Viewer installed on their system.