The file rwserver.conf for your reports server contains configuration information where you can change different settings of the rwEng such as the reports engine settings. The following information provides some recommended settings for your reports engine. NOTE: Depending on the number of reports being run along with the number of users running reports simultaneously, the settings might need to be modified especially for a production environment.
minEngine=0
maxEngine=# of CPU cores x2 (A single core machine should be 2, dual core should be 4, quad core should be 8 but can be 16)
engLife=10 (5 or 1 can also work depending on the environment)
maxIdle=30
jvmOptions=”-Xms512m -Xmx512m”
Job retries=3
Also, set:
maxConnections=# of end users (200 is a safe number for development servers)
KeepConnection=no
Example in rwserver.conf:
Settings in Enterprise Manager Basic Configuration:
Settings in Enterprise Manager Advanced Configuration:
NOTE: All changes to rwserver.conf will require a reports server restart. If your report server is a standalone report server (RptSvr_SERVER-NAME_asinst_1), restarting the server in OPMN will need to be done. If your report server is an in-process report server (rep_wls_reports_SERVER-NAME_asinst_1), WLS_REPORTS will need to be restarted.
NOTE: Reports server engine settings can also be edited using Enterprise Manager Fusion Middleware Control. When logged into Enterprise Manager, right-click on your Reports server and select Basic Configuration to configure minEngine, maxEngine, engLife, maxIdle, and jvmOptions and select Advanced Configuration to update maxConnections and retry (Job Retries).
