In this scenario, an insurance company wants to put their insurance forms online. This includes an insurance application form, an accident reporting form, and so on. End-users go to the Web site, select the form they want to complete, fill it out online, and submit it.
These forms are large, complex, and important, so the system is set up for high performance and high availability. Furthermore, it is expected that there will be multiple concurrent users. It is expected that 20% of users will have the Viewer installed on their system, while 80% of users will not.
This system hosts 5 forms with an average size of 500 KB and 5 pages. The largest form is 1 MB and uses 20 MB of RAM. This may increase to 30 MB when attachments are added to the form. This form has 10 pages and 6,000 items, including thousands of binds and multiple computes.
It is expected that this system will receive 500 to 1,000 submissions per hour, with 250 to 300 concurrent users at any one time. Heaviest load is expected between 8 am and 9 pm, EST. However, if demand increases, additional servers will be required. Deployment Manager is available to ease and speed deployment of additional servers.
In addition, this system will allow users to print the forms. As printing using Webform Server requires extra processing capacity, we will need a total of 8 CPUs for the application servers.
To meet high availability demands, there are multiple instances of each server. The load balancers have a hot running backup that can take over if the primary load balancer shuts down. Multiple translators and application servers also help meet high performance requirements.
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.