Before we can give an answer about data in regards to servers and CPU, it is necessary to know how the product will be used. The answers to these type of questions have more of an impact on performance than just the number of users defined to the system. The number of users is rarely the highest factor in determining performance
- Will all 500 users be logged on to the Web Viewer at the same time and downloading a 2000 page report? Probably not.
- Will the users be using the native Text to PDF conversion feature when emailing reports?
For that reason, we can only give a somewhat general configuration which can have the capability to expand, based upon the initial performance. . However, a good starting point for any Web Viewer 12.1 system should have the following configuration:
- Mainframe side
a) 2 DRAS tasks running at the same time
b) CCISSL, CA DRAS, and CA View on the same LPAR
2. Server Side
- 2 servers, load balanced.
- each server should have the performance of an Intel XeonE5-2600 processor (quad core) or better.
- Minimum 32 GB (of which 16 GB is dedicated to Tomcat), expandable to 128 GB
- The size of the disk is probably unremarkable, but should be monitored in case of increasing number of Web Viewer Audit logs, Tomcat logs, and Log4J output. Web Viewer and Tomcat requires less than 200 MB. It is Java and the operating system that requires most of the space
- If running Tomcat as a started task on the mainframe, a zIIP processor is required.
3) Database considerations
- Web Viewer 12.1 does NOT use the database intensively. It is mainly used to store and retrieve configuration data. Report data is never stored in the database.
- A remote database (Oracle, DB2 or SQL server) is recommended so that the database can backed-up/maintained by the corporate specialty department and share between the 2 servers.
4) Other considerations:
- Minimize the number of routers, bridges and switches between the Web Viewer server and the mainframe. That is, for optimal network performance, they should be on the same backbone. However, in reality, they never are. I like to see no more than 3 hops from the Web Viewer server to the mainframe.
This is a good starting point and additional tuning will likely be required.