How To Allow More JRE Client Side Memory for Loading Applets In P6 And Override The 'Maximum memory allocated to Java Applets' Variable In The P6 Configuration
Last updated on SEPTEMBER 09, 2016
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 18.104.22.168 and later
Information in this document applies to any platform.
***Checked for relevance on 02-Apr-2015***
Within the configuration used by P6, there is an application administrative setting called "Maximum memory allocated to Java Applets", which controls how much memory is allocated to the Java Runtime Environment (JRE) on a client machine when loading applets in the application. This administrative setting however applies to *all* client JREs, regardless of how much memory they actually have on their browser client. Therefore, the administrator is forced to set this to a minimum value which can be handled by the user population. The problem is that this does not allow specific users to use more memory if they actually have more on their workstation, regardless of any -Xmx heap setting parameter override that the user might want to provide locally in within the Java Control Panel.
Starting with P6 EPPM r8.2, there is now a way for users to increase their applet heap setting beyond what the P6 administrative setting (Maximum memory allocated to Java Applets) is set for and this document will walk through the steps necessary to configure this.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms