Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Understanding Domains
  3. Managing Your Account
  4. Using Informatica Administrator
  5. Using the Domain View
  6. Domain Management
  7. Nodes
  8. High Availability
  9. Connections
  10. Connection Properties
  11. Domain Object Export and Import
  12. License Management
  13. Monitoring
  14. Log Management
  15. Domain Reports
  16. Understanding Globalization
  17. Appendix A: Code Pages
  18. Appendix B: Custom Roles
  19. Appendix C: Informatica Platform Connectivity
  20. Appendix D: Configure the Web Browser

Administrator Guide

Administrator Guide

Example Resilience Timeout Configuration

Example Resilience Timeout Configuration

Some resilience timeout values are default and others can be configured or overwritten.
You can use the resilience timeout and limit on resilience timeout configured for the domain for
CDI-PC
application services if you do not set it for the application service. Command line programs use the service resilience timeout. If the service limit on resilience timeout is smaller than the resilience timeout for the connecting client, the client uses the services limit as the resilience timeout.
The following table describes the resilience timeout and the limits shown in the figure above:
Connect From
Connect To
Description
A
CDI-PC Integration Service
CDI-PC Repository Service
The
CDI-PC Integration Service
can spend up to 30 seconds to connect to the
CDI-PC Repository Service
, based on the domain resilience timeout. It is not bound by the
CDI-PC Repository Service
limit on resilience timeout of 60 seconds.
B
pmcmd
CDI-PC Integration Service
pmcmd
is bound by the
CDI-PC Integration Service
limit on resilience timeout of 180 seconds, and it cannot use the 200 second resilience timeout configured in INFA_CLIENT_RESILIENCE_TIMEOUT
.
C
CDI-PC Client
CDI-PC Repository Service
The
CDI-PC Client
is bound by the
CDI-PC Repository Service
limit on resilience timeout of 60 seconds. It cannot use the default resilience timeout of 180 seconds.
D
Node A
Node B
Node A can spend up to 90 seconds to connect to Node B. The Service Managers on Node A and Node B use the default node resilience timeout of 90 seconds.

0 COMMENTS

We’d like to hear from you!