jvm_heapsize command

You can view and change the maximum heap size of the Java™™ virtual machine (JVM) for the Security Identity Manager WebSphere® Application Server profiles.

The JVM has heap memory, which is a runtime data area where memory for all class instances and arrays are allocated. Heap memory for either servers are created at JVM start-up with a default value that is based on the size of RAM.

If the default value is insufficient to suit the memory consumption of either servers, you can change the maximum heap size to a value that you prefer.

After you change the maximum heap size for either or all server profiles, restart the IBM® Security Identity Manager and Cluster Manager server to apply your changes.

Usage


isimvasvr > isim
isimvasvr: isim > jvm_heapsize
isimvasvr: jvm_heapsize >
reset_max_heapsize
Reset maximum heap size for ISIM DMGR, Application and Message Member to default value.
set_max_heapsize
Set maximum heap size for ISIM DMGR, Application and Message Member.
show_max_heapsize
Show maximum heap size for ISIM DMGR, Application and Message Member.

Examples

  • At the isimvasrv:jvm_heapsize prompt, enter show_max_heapsize.
    1: DMGR 
    2: APP_Member 
    3: MSG_Member Enter index: 1 
    DMGR max heap size(MB): 2048
  • Set a maximum heap size.

    At the isimvasrv:jvm_heapsize prompt, enter set_max_heapsize.

    1: DMGR 
    2: APP_Member 
    3: MSG_Member 
    Enter index: 1 
    Enter max jvm heap size(MB): 5000 
    Updating max jvm heap size for DMGR. 
    Please wait... 
    Max heap size updated successfully. 
    Restart Cluster Manager Server and IBM Security Identity Manager server.
  • Reset the maximum heap size.

    At the isimvasrv:jvm_heapsize prompt, enter reset_max_heapsize.

    1: DMGR 
    2: APP_Member 
    3: MSG_Member 
    Enter index: 1 
    Are you sure you want to reset the jvm maximum heap size? 
    Enter YES to confirm that you want to continue: YES
    Reseting max jvm heap size for DMGR. Please wait... 
    Max heap size updated successfully.
Important: Restart the Cluster Manager Server and IBM Security Identity Manager Server to apply the new settings.