without authenticating to where ? you will need to authenticate into bsa....
you can use a 'file deploy job' to do this.
You can Copy from one server (in browse) and paste on another.
If this needs to be done in multiple servers from a server, you can browse that server, right click on the file and select > Add to depot. You can use a File deply job to deploy on one or more servers in a go.
I think he means without going through the app server, i.e. target to target copy. Wouldn't that be cp -M ?
Step1 >I have a Job which dose some configuration on server 'A' which will create a Folder with collection of Files and Folders.
Step 2> Now I want to create a BL job which will copy this Folder from Server 'A' to server 'B'
SO the step 2 is where I am facing problem
1> I cant create a Depot of that folder from GUI as both this process shoude be Automated and will run in sequence
2> normal cp or scp also needs authentication which is also a problem
you can create a 'file deploy job' which will copy files from server A to server B.
the problem as yanick mentions is that the copy happens 'through' the appserver - meaning if your appserver, server A and server B are all on different networks then it could be quite slow.
But has the (undocumented) -M switch of the cp command been fixed in 8.5 to allow for large files to be copied? If so, this could be his solution. It does require that the source server can resolve the hostname of the second and also access port 4750 directly, but that means it would be an agent to agent copy, just like repeaters do it.
Hi Jeet, as per your query for the Depot file, which is getting created by somejob, you can check on which server it is getting generated, Look for which job ran on that box using Audit trail ( Job option) , you can easily find that which job ran on that server.Check dependencies of that job and you will get which package/Command creating that file on fly
FileDeployJob you can use to solve your purpose.
Based on what Bill confirmed, you could try this (which is an undocumented switch):
1. Create a NSH Script Job with the following in it:
cp -M //source_target/path/to/filename //destination_target/path/to/destination/folder
The -M switch should initiate a direct agent to agent copy, without going through the application server or socks proxy. This implies that source_target has to be able to locally resolve the hostname of destination_target (add it to its hosts file if it doesn't), and that it's able to open a TCP connection to it on port 4750. You may also have to edit the exports file of the destination_target to allow for the source_target to connect to its agent.
You will need to use the latest 8.5 release for this to work however if the file is large (I think it was puking if it was above 10 or 15Mb, but per Bill that should have been fixed in 8.5).
You won't be able to do this with any other means if you don't want to use scp or another non-BSA transfer protocol.