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. Schedules
  12. Domain Object Export and Import
  13. License Management
  14. Monitoring
  15. Log Management
  16. Domain Reports
  17. Node Diagnostics
  18. Understanding Globalization
  19. Managing Distribution Packages
  20. Appendix A: Code Pages
  21. Appendix B: Custom Roles
  22. Appendix C: Informatica Platform Connectivity
  23. Appendix D: Configure the Web Browser

Administrator Guide

Administrator Guide

Application Service Restart and Failover

Application Service Restart and Failover

If an application service process becomes unavailable, the Service Manager can restart the application service or fail it over to a back-up node. When the Service Manager fails over an application service, it starts the service on another node that the service is configured to run on.
The following situations describe how the Service Manager restarts or fails over an application service:
  • If the primary node running the service process becomes unavailable, the service fails over to a back-up node. The primary node might be unavailable if it shuts down or if the connection to the node becomes unavailable.
  • If the primary node running the service process is available, the domain tries to restart the process based on the restart options configured in the domain properties. If the process does not restart, the Service Manager may mark the process as failed. The service then fails over to a back-up node and starts another process. If the Service Manager marks the process as failed, the administrator must enable the process after addressing any configuration problem.
If a service process fails over to a back-up node, it does not fail back to the primary node when the node becomes available. You can disable the service process on the back-up node to cause it to fail back to the primary node.
The following image shows how you can configure primary and back-up nodes for an application service:
The high availability domain has three nodes. Node 1 is the master gateway node. Node 2 is a gateway node. Node 3 is a worker node. The primary node for the Integration Service is Node 1, and the back-up nodes are Nodes 2 and 3. The primary node for the Repository Service is Node 2, and the back-up node is Node 3.

0 COMMENTS

We’d like to hear from you!