Transactional Deployment through different firewall

polotoo

Hi,

The client needs a fully transactional deployment. But the problem is the three receivers are behind three different firewalls. And the firewalls are using NAT, which means the local node can only be the IP address of one firewall in the config file. Is there a way I can put the three deployments in one config file or I have to write three config files and try to find an approach to make it transactional? I am thinking about using DNR scripts, but that will be a nested DNR?

ANy suggestions?

Thanks

Adam Stoller

Hi, The client needs a fully transactional deployment. But the problem is the three receivers are behind three different firewalls. And the firewalls are using NAT, which means the local node can only be the IP address of one firewall in the config file. Is there a way I can put the three deployments in one config file or I have to write three config files and try to find an approach to make it transactional? I am thinking about using DNR scripts, but that will be a nested DNR? ANy suggestions? Thanks

It's been a while since I've had to deal with this kind of setup - but I believe you can define the localNode in the deployment configuration file anyway you want to - but you have to use the IP address of the firewall in the odrcvr.xml file to specify the allowedHost that can deploy to that receiver. If that's the case you should be fine with a fan-out deployment as long as all three receivers are configured correctly.

You might need to also play around with the strictPartnerChecking attribute of the listenerProperties element too (see the OD Admin manual for more info) - but I'd try just making sure the allowedHosts are set correctly first.