Fujitsu V6.0 manual Setting the Heap Size in the Java Execution Environment

Page 91

Notes on Portal Component

Notes on Using Administrative Console

•In the setting example of definition in the server that is displayed on the scenario registration window or the USP addition window, Windows NT® server is used.

Example: file:/temp/scenario/scenario.jar

Make the actual settings in accordance with the syntax for the Solaris™ Operating Environment system.

•If only a host name is specified to start the Administrative console, an error may occur when the operation control function is used because of the DNS settings.

Example: http://hostA/portalworks/PWAdminSystem

In such cases, specify FQDN as shown in the following example. In addition, when the URL is specified for adding USP, be sure to specify FQDN.

Example: http://hostA.domain.com/portalworks/PWAdminSystem

Setting the Heap Size in the Java Execution Environment

It is recommended to set the heap size in the Java execution environment to 256 MB or more. The procedure for changing the heap size is as follows:

(1)Start the Interstage Management Console.

(2)Select [System], [WorkUnit], and then [PortalServer].

(3)Add the following options to [JavaVM option]:

-XX:NewSize=64m, -XX:MaxNewSize=64m, -Xms256m, -Xmx256m

(4)Restart [PortalServer] WorkUnit.

Select the [Operation] tab and restart [PortalServer].

Change the values for -XX:NewSize, -XX:MaxNewSize, -Xms, and -Xmx according to the environment of the machine on which the Portal component is installed and the scope of using the Portal component.

-Xmsn

Specify the number of bytes for the initial size (n) of the memory allocation pool.

The value to be specified must be a multiple of 1024 that is greater than 2 megabytes. To specify the value in kilobytes, suffix the value with character k or K.

To specify the value in megabytes, suffix the value with character m or M. The default is 64 megabytes.

-Xmxn

Specify the number of bytes for the maximum size (n) of the memory allocation pool. Specify the same value as the size specified for the -Xms option. -XX:NewSize=64m, -XX:MaxNewSize=64m

When specifying 256 MB or more for the maximum size of the memory allocation pool, specify also these three Java execution options.

3-39

Image 91

Contents Product Notes Interstage Application Server V6.0Unix TrademarksWho Should Read this Document? Purpose of this DocumentFunctions that are not Supported by the Linux Version Organization of this DocumentTable of Contents Product Notes Table of Contents Page Index Chapter Supported Software J2EE Exclude Security Software Products Required for Application DevelopmentFunction Name Product Name Version Security Products Required for Application Development SecurityOperation / Administration Other Functions FrameworkFramework Products Required for Application Development Function Name Product Name Version Software Products Required for Application Execution Security Products Required for Application Execution Page Framework Products Required for Application Execution Portal ComponentOther Functions J2EE Exclude Security Security Interstage Apworks Chapter Restrictions Restrictions on Interstage Http Server Restrictions on Interstage Http ServerRestriction Remarks Date Removal Restrictions on InfoProvider Pro Restrictions on InfoProvider ProRestrictions on the J2EE Service Restrictions on the J2EE ServiceRestrictions on the Servlet Service Restrictions on the Servlet ServiceRestrictions on the EJB Service Restrictions on the EJB ServiceRestrictions on the EJB Service Restriction Remarks Date Removal Restriction Remarks Date Removal Page Restrictions on the Soap Service Restrictions on the Soap ServiceRestrictions Restriction Alternative Method Date Removal Restrictions on the Corba ServiceRestrictions on IDL Definitions Restrictions on IDL DefinitionsRestriction Alternative Method Date Removal Example Restriction Alternative Method Date Removal Restriction Alternative Date Method Removal Restrictions on IDL CompilationRestrictions on C and C++ Programming Restrictions on IDL Compilation10 Restrictions on Java Programming Restrictions on the Naming Service11 Restrictions on the Naming Service Restrictions on Java Programming12 Restrictions on the Corba Service Restrictions on the Corba Service13 Restrictions on the Event Service Restrictions on the Event Service14 Restrictions on the Component Transaction Service Restrictions on the Component Transaction ServiceRestrictions on the Locale of Languages Restrictions on the Database Linkage Service15 Restrictions on the Locale of Languages Restrictions on the Jndi Restrictions on the InfoDirectory Administration Tool16 Restrictions on the InfoDirectory Administration Tool Restrictions on InfoDirectory18 Restrictions on JDK/JRE Restrictions on JDK/JRERestrictions on the Portal Component Restrictions on Scripts in Contents20 Restrictions on the Alternative Logon Function Restrictions on the Alternative Logon Function21 Restrictions on the Load Distribution Environment Restrictions on Using Netscape 4.6/4.722 Restrictions on Using Netscape 4.6/4.7 Restrictions on the Load Distribution Environment24 Access from PC to Secure Site Https Access from PC to Secure Site HttpsRestrictions on Using the Brick Automatic Update Function 23 Restrictions on Using Web USP26 Restrictions on Other Functions Restrictions on Other FunctionsRestrictions Chapter Common Notes for Interstage About the Cross-Site Scripting ProblemAbout Netscape Countermeasures Using the Jsse FunctionSecurity Information InfoDirectory Monitor Screen ColorsApplicable Functions J2EE common resourcesServices/Functions for Which Port Numbers are Set Setting Port Numbers Used for Individual ServicesService Name Port Number Setting Location Function Name Service Name Port Number Setting Location Function Name Service Name Port Number Setting Location Function Name Service Name Port Number Setting Location Function Name Version Level of Each Service Performing the Operation Starting and Stopping Services Dealing with Abnormal Command TerminationPage Authority to Use the Interstage Http Server J2EE Application Operation When operating the J2EE application clientJava VM heap area size calculation Use of the J2EE Management Tool or J2EE Deployment Tool V6.0 Servlet Service Servlet Service Execution EnvironmentExecution Environment of Earlier Version Servlet Service Session Management Cookie of Servlet ServiceVersion of Java Development Kit/Java Runtime Environment Page When Operating with WorkUnits When Interstage Jdbc Driver is Used API when datetime Type is Used Stored ProcedureUnsupported API Page About the EJB Application Process Starting EJB ApplicationsWhen Session Recovery Function of Servlet Service is Used When Encryption Communication by SSL is UsedWhen J2EE Management Tool or J2EE Deployment Tool is Used Uninstalling Setting Up the EnvironmentStopping Page Page Page Port Number Host NameMonitoring during Interstage Operation About Corba Service Termination using the isstop CommandInstallation of Oracle8i8.1.6 Using Oracle8Use of Oracle Database by Java Server Application Corba Server Application is Operated using Multi Thread Sample Provided with Database Linkage ServiceMaximum Number of Resources for One Transaction Error Messages in the Event Log Page Page Start Programs Accessories Command prompt Share folder name Directory Start Programs Command promptProcessing when No response from service Occurs Processing when Network Error503 OccursModification Method Modification Method Setting the Heap Size in the Java Execution Environment Redistributable Files Security on the InternetIndex Jndi Page USP