This section provides information about updating your Tomcat environment after you install the identity applications.
NetIQ ships convenience bundle of Apache Tomcat, which auto-starts after successful installation and configuration of Integrated Installation program. If you installed your own Tomcat program, consider the following issues:
You can modify the Tomcat service to perform more effectively. For more information, see So You Want High Performance.
You might want to add support for logging events. For more information, see Section 26.6, Using the Apache Log4j Service to Log Sign-on and Password Events.
For more information see, Section 33.2, Configuring the User Application Driver for Clustering.
The identity applications use JGroups for the caching implementation. In some configurations, JGroups requires that the preferIPv4Stack property be set to true to ensure that the mcast_addr binding is successful.
Without this option, the following error might occur:
[10/1/09 16:11:22:147 EDT] 0000000d UDP W org.jgroups.util.Util createMulticastSocket could not bind to /228.8.8.8 (IPv4 address); make sure your mcast_addr is of the same type as the IP stack (IPv4 or IPv6).
You might also see this error:
[3/21/12 10:04:32:470 EDT] 00000024 UDP E org.jgroups.protocols.TP down
failed sending message to null (131 bytes)
java.lang.Exception: dest=/228.8.8.8:45654 (134 bytes)
at org.jgroups.protocols.UDP._send(UDP.java:353)
The parameter java.net.preferIPv4Stack=true is a system property that can be set in the same manner as other system properties such as extend.local.config.dir. For instructions on setting system properties, see Section 32.6.2, Adding User Application Configuration Files and JVM System Properties.
Most loadbalancers provide a healthcheck feature for determining whether an HTTP server is up and listening. The User Application contains a URL that can be used for configuring HTTP healthchecks on your loadbalancer. The URL is:
http://<NodeIP>:port/IDMProv/jsps/healthcheck.jsp