WAS v8.5 > Script the application serving environment (wsadmin) > Configure servers with scripting
Increasing the Java virtual machine heap size using scripting
Some servers might specify a JVM heap size greater than the default. We can increase the heap size of the JVM using the dmgr console, wsadmin, or a Java client.
If we are using a JVM platform that is running on a 32-bit AIX system, complete this task if the application server requires a greater heap size.
- Set attributes that control the heap size for the JVM associated with the server.
Use the dmgr console, wsadmin, or a Java client to control the heap size.
- Increase the heap size of the JVM.
- Create a script to launch the server. Use the -script option with the command that you are using to start the target server, for example, the startServer, startManager, or startNode batch or shell command utilities. This action generates a script used to launch the target server.
- Manually set the environment variables before starting the target server with the startServer, startManager, or startNode batch or shell command utilities.
With the following settings, we can specify a maximum heap size for the JVM of 11 multiplied by 256 megabytes:
export IBM_JVM_LDR_CNTRL_NEW_VALUE=MAXDATA=0XB0000000@DSA export LDR_CNTRL=MAXDATA=0XB0000000@DSA
- Use AdminTask, for example:
-
Jython:
- AdminTask.setJVMMaxHeapSize('-serverName server1 -nodeName node1 -maximumHeapSize heap_size')
-
Jacl:
- $AdminTask setJVMMaxHeapSize {-serverName server1 -nodeName node1 -maximumHeapSize heap_size}
-
Related
Configure servers with scripting
Reference:
Server settings configuration scripts