8.13 Configuring Reports Managed Server

By default, the Oracle Reports application is deployed on a Managed Server.

You can modify the start-up properties of a Reports Managed Server through the SetDomainEnv.sh file or the WebLogic Server Administration Console. However, some properties like -Xmx and -Xms, which are already defined in the setDomainEnv.sh file would take precedence and the changes made through the WebLogic Server Administration Console do not take effect. Also, the start-up properties of WLS_REPORTS that are modified using the WebLogic Server Administration Console do not take effect when WLS_REPORTS is started using startManagedServer.sh. Hence it is recommended that you use SetDomainEnv.sh (for UNIX) or SetDomainEnv.bat (for Windows) to modify the start-up properties for Managed Servers.

You can modify the system or runtime properties for a Managed Server using the SetDomainEnv.sh (for UNIX) or SetDomainEnv.bat (for Windows) which is located in $DOMAIN_HOME/bin.

You can modify the runtime properties using the EXTRA_JAVA_PROPERTIES variable inside the [ "${SERVER_NAME}" = "WLS_REPORTS" ] block.

You must add any new environment variable for WLS_REPORTS Managed Server inside the if[ "${SERVER_NAME}" = "WLS_REPORTS" ] block in the SetDomainEnv.sh script.

As the default setting is done for all components that use setDomainEnv.sh, the -Xmx and -Xms settings are added multiple times to the command line of a Managed Server. Hence you must add the -Xmx and -Xms settings at the end of EXTRA_JAVA_PROPERTIES variable in the [ "${SERVER_NAME}" = "WLS_REPORTS" ] block.

WLS_REPORTS is the name of the Managed Server where the Reports application is deployed during installation. For expand cluster cases, Managed Servers can be named as WLS_REPORTS1, WLS_REPORTS2, and so on.

Scripting on this page enhances content navigation, but does not change the content in any way.