OPPM is designed to work with a variety of hardware and software and to integrate with existing Enterprise systems. The following figure depicts scenarios for deploying OPPM where performance tests have been conducted with the data set (see Appendix A for details):
Front-End Server: IIS server that handles HTTP requests and the presentation layer.
Primary Back-End Server: This is the primary function engine. It is responsible for analysis, rank calculation, and processing functions.
Secondary Back-End Server: This is a secondary function engine that helps process functions.
Database Server: Oracle Database server or Microsoft SQL server.
The initial or XSmall deployment configuration for OPPM is shown below:
For Small deployments, include a secondary back-end server. This is suggested as a result of testing with the data set described in Appendix A.
You can manage increasing complexity by adding additional servers (secondary back-end and front-end servers). For database servers, the number of nodes in RAC implementation must be increased, as shown in the figure below:
Note: Each back-end application server adds additional capacity to process the Action Queue. Add as many back-end application servers as necessary to process the Action Queue within the time required by business needs.
