Firewall and a reverse deploy

Can somebody post a working config for the reverse deployment through a firewall?

I have a forward deployment working fine, but when I am trying to do a reverse deployment it fails.

Find more posts tagged with

Comments

John742

What is the error you are receiving? My first guess is that the firewall is not setup as an allowed host on the base server.

eror_stack.txt

Valentine

It turns out that the firewall guys, allowed a direct connect through the firewall, so the firewall was not being used.

John742

So are you still having the problem? If not what error is showing in the mirco log? check the micro log on the receiver also.

CRB

can you still post your deployment script, i am looking into doing a reverse deployment too. also what changes do i need to make network/firewall ways?

John742

What type of reverse deploy are you interested in? directory compare...etc. Do you have anything currently set up for reverse deployments?(ie adding the target receiver(reverse source) to the bases allowed host list). outline what you wish to do and we can mock it up. As far as the firewall goes check to see if it is doing any NAT translation. If so ,which way? you will have to add the translated ip to allowed hosts so your server knows which allowed host node set to apply when accepting a deployment. Make sense?

CRB

well i dont really have a set requirements right now. it just the dev team made put some quizes online that some agents take, and the scores are save on the live servers that host the sites. so my idea was instead of asking the admin to copy those folders over.. how about we just automatic reverse deployment that will kick off every night and bring bak to scores. so my deployment will be simple copy or cut of the files create on the live server back to the base. and the files r create dynamically each with unique names but under the same folder /records... i will get bak to this issue when i am actualyl doing the script.

John742

Use *od-home*\examples\conf-od\reverseDeploy.xml

just a few key things:
-the source is the location on the target server you want to "pull" info from
-the target is the location where the source data should be "pulled" to
-localNode host is still the odbase
-nodeRef useNode - is still the odrcvr
-remember to include an allowed host definition for the target server in odbase.xml for the locatino you are pulling the info back into

Should be ok. I think sending you one on my deployment configs will just confuse the idea, but if the above does not make sense let me know

CRB

ur last post makes sense, and very helpful, thank you!