What would happen if the smhost.conf file variable called request time out is changed from "60 seconds" (Legacy_Onyx KB Id: 158639)

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Risk Analytics
• CA Secure Cloud SaaS - Arcot A-OK (WebFort)
• CLOUDMINDER ADVANCED AUTHENTICATION
• CA Secure Cloud SaaS - Advanced Authentication
• CA Secure Cloud SaaS - Identity Management
• CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

smhost.conf file variable called request time out is set at "60 seconds", what would happen if this is lowered.

Environment

Release:
Component: IDMIND

Resolution

1) If the value is the same or lower than the time it takes the Policy Server to respond, or the network slows down then there is a potential to continue to mark policy servers as not available, and never stay with a policy server long enough to get a response. So changing this value must be used with caution.

2) Netegrity does not make recommendations on what this value should be other than the defualt value we install, this is specific to the customer's environment.

3) Best Approach would be to do load testing in a staging environment to determine what would be the best value to set the "request time out".