13.1 Configuring Identity Applications Clustering to Use TCP or UDP

You can configure the Identity Applications clustering to use TCP or UDP in local or global settings. The configuration process must be completed on each server in the cluster because the local settings are saved on the file system for each server.

To configure the Identity Applications clustering to use TCP or UDP:

  1. Log in to Identity Applications as the an administrator and go to Configuration > Caching and Cluster.

  2. In the Caching Management page that opens, click Cluster Cache Configuration.

  3. Navigate to Local Settings and perform the following actions:

    1. Enable the Enable Local and Local check boxes in the Cluster Enabled row.

    2. Enable the Enable Local check box in the Cluster Properties row and specify a value in the text field in the Local column.

      To use TCP, specify the following string:


      For example,

      TCP(bind_addr=idmapps;start_port=7818):TCPPING(initial_hosts=[7818],[7818];port_range=3):MERGE3(min_interval=10000;max_interval=30000):FD_SOCK:FD(timeout=2500;max_tries=5):VERIFY_SUSPECT(timeout=1500):BARRIER:pbcast.NAKACK2(use_mcast_xmit=false):UNICAST3:pbcast.STABLE(desired_avg_gossip=50000;max_bytes=4M):pbcast.GMS(print_local_addr=true; join_timeout=2000):MFC(max_credits=2M;min_threshold=0.4):FRAG2(frag_size=60K):pbcast.STATE_TRANSFER

      To use UDP, specify the following string:


      For example,


      For more information, see the JGroups 4.0.12 documentation.

  4. Save the changes. These changes are written to the local file system for your server. Remember to make these changes for all servers in the cluster. Any server that does not have these changes uses the global settings values.

  5. Restart the server.

NOTE:bind_port and mcast_port should be different for Permission Index Cluster Properties and Cluster Properties.