Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Configure servers with scripting

Increasing the Java virtual machine heap size using scripting

Some servers might specify a Java virtual machine (JVM) heap size greater than the default. We can increase the heap size of the JVM using the administrative console, wsadmin.sh, or a Java client.

About this task

If you are using a JVM platform that is running on a 32-bit AIX system, complete this task if the application server, dmgr, or node agent require a greater heap size.

Procedure

1. Set attributes that control the heap size for the JVM that is associated with the server.

   Use the administrative console, wsadmin.sh, or a Java client to control the heap size.

2. 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 that you can use to launch the target server.

   • Manually set the environment variables before you start the target server with the startServer, startManager, or startNode batch or shell command utilities.

     With the following settings, you 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 the AdminTask object, for example:

     ### Jython

     AdminTask.setJVMMaxHeapSize('-serverName server1 -nodeName node1 -maximumHeapSize heap_size')
     

     ### Jacl

     $AdminTask setJVMMaxHeapSize {-serverName server1 -nodeName node1 -maximumHeapSize heap_size}
     

Configure servers with scripting

Related

Server settings configuration scripts

+

Search Tips   |   Advanced Search