The following computers are required to run this system:
- Form design system – A typical workstation computer that is used to create the blank insurance forms.
- Application development system – A typical workstation computer that is used to create the forms application portlet.
- Forms repository – A database that stores the blank forms, submitted forms, and the data extracted from the submitted forms.
- Application servers – Two clustered application servers host the forms application. The forms application consists of WebSphere® Portal, the Webform Server portlet, and the IBM® Forms API. Using two servers (horizontal scaling) provides high performance and high availability.
- Log Server, Access Control Database, Shared File Cache – These Webform Server components are hosted on a dedicated server.
- Backend application servers – Two clustered servers host the backend application. The backend application consists of WebSphere Process Server.
- Deployment Manager system – WebSphere Deployment Manager is used to set up multiple instances of WebSphere Portal Server, the Webform Server Translator, and WebSphere Process Server. This allows system administrators to easily add new servers if the demand for the application increases.
- Load balancers – The load balancers distribute work between the members of a cluster and detect if a server becomes unavailable. A single server can perform load balancing, but for high availability applications, a hot, running backup should be in operation in case the primary load balancer becomes unavailable.
Note: If you are using a hardware load balancer, you may also need to deploy a reverse proxy.
- HTTP server – The HTTP server handles user sessions and provides security to the overall solution. A single server can be used, but for high availability applications, a hot, running backup should be in operation in case the primary server becomes unavailable.
- Firewalls – Standard corporate firewalls provide security to the overall system.
Download this architecture from the "Attachments" section located at the bottom of this article.
Other architectures are possible, for example:
- The forms repository could be a content management system instead of a database.
- The backend application could consist of any application that can be integrated with IBM Forms using IBM Forms Server – Forms Services Platform or WebSphere Integration Developer, instead of WebSphere Process Server. For example, FileNet or WebSphere Content Manager
Back to: Enterprise Scenario: Insurance forms on Internet