TCP IP connection settings in HCO

[Ujwol]

This is created on behalf of @SreeniKotlure1305222

 

Hi Ujwol

Thanks for your response and appreciate for your help on this.

I have few more questions regarding the HCO configurations.

We have 3 set of HCO’s in our environment and these configured long time back and no one here know  who set this values and why they are different.

In their  HCO’s we are seeing  different Maximum Sockets per port values and different Request Time outs.

Can you please let us know what are these values  and how it will impact if we make one Generic HCO to all our applications rather three different.

 

Maximum Sockets Per Port

 

200

 

Minimum Sockets Per Port

 

2

 

New Socket Step

 

2

 

Request Timeout

 

60

 

 

 

Maximum Sockets Per Port

 

50

 

Minimum Sockets Per Port

 

2

 

New Socket Step

 

2

 

Request Timeout

 

30

 

 

Appreciate for your time and help.

Thanks

Sreeni

[Ujwol]

Hi Sreeni,

 

These values need to be tuned depending upon the traffic that you expect.

Best is to start with the default values.

 

Trusted Hosts for Web Agents - CA Single Sign-On - 12.52 SP1 - CA Technologies Documentation

Several settings affect the TCP/IP connections between the trusted host and the Policy Server.

• Maximum Sockets Per Port
  Defines the maximum number of TCP/IP connections that the trusted host uses to communicate with the Policy Server. By default, this value is set to 20, which suits low- and medium-traffic web sites. Increase this number in the following situations:
  • You are managing a high-traffic web site.
  • You have defined agent identities for virtual servers.
• Minimum Sockets Per Port
  Determines the number of TCP/IP connections open for the Policy Server at startup. The default value is 2. If you are managing a high-traffic web site, increase this number.
• New Socket Step
  Specifies the number of TCP/IP connections that the Agent opens when new connections are required. The default value is 2. Increase number of sockets to add at each required at each level when you require more sockets.
• Request Time Out

Server timeout. The maximum time an agent will wait for a response from a server. If the wait time exceeds the server timeout value, the server is considered inactive, and failover to the next server occurs.

If a server timeout occurs within a cluster, and the timeout causes the cluster’s failover threshold to be exceeded, failover to the next cluster occurs.

Set through: RequestTimeout.

 

Cheers,

Ujwol