WPS : How to increase heap size/memory for Process Server

By increasing memory we are able to resole the memory exception. Out of memory error occurs on start of WebSphere Process Server:

Increase the Java™ Virtual Machine (JVM) parameter MaxPermSize to 512M in the server.xml file of the created profile.

1. Go to <installroot>/profiles/<profileName>/config/cells/<cellname>/nodes/<nodename>/servers/ <servername>/server.xml
2. Open the file and search for "genericJvmArguments"
3. Scroll down towards the end of the file and find the "genericJvmArguments" property with in the jvmEntries attribute.
4. Add -XX:MaxPermSize=512m as the last value for the genericJvmArguments parameter.
Ex:
<jvmEntries xmi:id="...genericJvmArguments="${IBMSCMX} ${IBMGCPOLICY_GENCON} -XX:MaxPermSize=512m">

Alternatively, if the server can start successfully but then later runs out of memory, the MaxPermSize can be increased using the Administrative Console.

1. Log in to the Administration Console
2. Click Servers > Server Types > WebSphere application servers > WebSphere Process Server.
3. Under Server Infrastructure, click Java and Process Management > Process Definitions > Additional Properties > Java Virtual Machine.
4. In the Generic JVM arguments field, change the MaxPermSize value to -XX:MaxPermSize=numeric value, where numeric value is a quarter of the value entered for the Maximum Heap Size. For example, if your Maximum Heap Size is 3000 M, set MaxPermSize to 750 M. If your Maximum Heap Size is less than 2048 M, set MaxPermSize to 512 M.
5. Important: If MaxPermSize does not exist in the Generic JVM arguments field, add it to the field but do not replace existing information in the Generic JVM arguments field with the MaxPermSize information.
6. Click OK to save your changes.
7. Click Save to save your changes to the master configuration.
8. Log out of the Administration Console.
9. Restart the your server.