Restart and Failover
To maximize operation time in the event of a failure, the Informatica domain can restart or fail over processes to another node.
The Service Manager on the master gateway node accepts application service request and manages the domain. If a master gateway node is not available, the domain shuts down. Configure the domain to failover to another node by configuring multiple gateway nodes.
Based on your license, you can also configure backup nodes for application services. The Service Manager can restart or failover the following application services if a failure occurs:
- •Data Integration Service
- •Model Repository Service
- •PowerCenter Integration Service
- •PowerCenter Repository Service
- •PowerExchange Listener Service
- •PowerExchange Logger Service
- •Resource Manager Service
Domain Failover
The Service Manager on the master gateway node accepts service requests and manages the domain and services in the domain. The domain can failover to another node when the domain has multiple gateway nodes. Configure multiple gateway nodes to prevent domain shutdown when the master gateway node is unavailable.
The master gateway node maintains a connection to the domain configuration repository. If the domain configuration repository becomes unavailable, the master gateway node tries to reconnect when a user performs an operation. If the master gateway node cannot connect to the domain configuration repository, the master gateway node may shut down.
If the domain has multiple gateway nodes and the master gateway node becomes unavailable, the Service Managers on the other gateway nodes elect another master gateway node. The domain tries to connect to the domain configuration repository with each gateway node. If none of the gateway nodes can connect, the domain shuts down and all domain operations fail. When a master gateway fails over, the client tools retrieve information about the alternate domain gateways from the domains.infa file.
Note: Application services running on the master gateway node will not fail over when another master gateway node is elected unless the application service has a backup node configured.
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:
