Scribd
Upload
45 views

ITIM Study Note

ITIM uses two application servers per node, one for the application and one for the messaging engine. The regular ITIM installer sets the maximum JVM size to 1024 MB and initial size to 512 MB for the application server JVM. For 64-bit systems, the maximum JVM size can be increased to 2048 MB, and for 32-bit systems up to 1280 MB. Setting the JVM heap size larger than physical RAM can cause performance issues as the operating system may swap out the JVM to disk.

Uploaded by

hacmpaix
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
45 views

ITIM Study Note

ITIM uses two application servers per node, one for the application and one for the messaging engine. The regular ITIM installer sets the maximum JVM size to 1024 MB and initial size to 512 MB for the application server JVM. For 64-bit systems, the maximum JVM size can be increased to 2048 MB, and for 32-bit systems up to 1280 MB. Setting the JVM heap size larger than physical RAM can cause performance issues as the operating system may swap out the JVM to disk.

Uploaded by

hacmpaix
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

ITIM application ou=itim ITIM recycle ou=recyclebin, ou=itim

Do not set JVM heap sizes on 32-bit Windows platforms higher than 1280 MB even if the system has more available memory For cluster installations, IBM Tivoli Identity Manager uses two application servers per node: one for the application and one for the messaging (JMS) engine. All JVMs in this topic are used by the application, not the messaging engine. The JVM used by the messaging engine application server uses default values. The IBM Tivoli Identity Manager regular installer sets the maximum JVM size to 1024 MB and the initial size to 512 MB. These values are adequate for most small and medium systems. If your server has available RAM, increase the maximum JVM size to 2048 MB for 64-bit JVMs or 1280 MB for 32-bit JVMs. The maximum heap size on 64-bit JVMs can be much higher than 2 GB. A larger value larger can result in long delays during full garbage collections. Typically, 4 GB is an adequate maximum. Do not set the JVM heap size larger than the physical RAM. The WebSphere Application Server suffers significant performance degradation if the operating system swaps out the JVM to swap space. Setting the heap size larger than the physical RAM can cause slow user interface (UI) performance, transaction rollbacks, timeouts, and high disk utilization. Scheduled reconciliations operate via the scheduler - just like any other scheduled item in ITIM. The scheduler reads the enrole.remote_resources_recons and enrole.remote_resources_recon_queries tables.

You might also like