Hi,

in case Node01 goes down for any reason the whole domain will go down as all Administrative Tasks (Informatica Administrator, Log Manager etc.) can only be executed on a Gateway Node.

So, if you want to have a backup for failover  both of you nodes need to be Gatewaynodes.

Hope that helps

Kind regards,

-Sven

Hi,

The gateway nodes can run management services for the domain, and they are also the ones that communicate with the domain database. The worker node can run application services, but cannot communicate with the domain database.

A worker node runs a Service Manager process, and it can run application services. The worker node cannot run the extra management processes, nor does it communicate with the domain database. This can be good, because it does not require the extra resources for management, but it cannot take over as a master gateway node.

In simple words a worker node is designed to spread the work load between your nodes in the domain.

Regards,

-Sven

Yes, this is correct.

In a domain with one gateway node and one worker node, if the lone gateway node goes down, so does the worker node and any application services. If the worker node goes down, then the gateway node will continue running.

Hello Kittu Babu,

node02 (worker node) being a worker node will not be able to hold the domain and the domain will go down.

Thanks

Hi Kittu,

In a domain with just one gateway node and one worker node, the domain will crash or go down if the gateway node goes down.

Thus, it is always a good idea to include atleast 2 gateway nodes such that if the first gateway node was to go down, the domain can be "failed-over" to the second gateway node.

Worker nodes can run services and workflows but the gateway node can connect to the database and as a master gateway node, can manage the services on the domain. Thus, the domain can not "fail-over" to a worker node in case the gateway node goes down.

Thanks,

Sai