Hi, The support told me to switch back from advanced mode, to the regular mode (until 8.1.3 will be released)
Also repeaters routing rules been set up
Yes, there is a know issue with advacned file server.
The repeater functionality should work for all deploy jobs, provided the repeater rules have been setup and are valid.
The idea of repeater is exactly what you are tryign to achieve, to get the payload from designated server called repeater instead of appseever/fileserver and is best suited to wan deployment or segmented networks.
Check if this config is setup in blasadmin
show RoutingConfig EvaluateRepeaterRules - This should be setup to 'true'.
The issue w/ the ARS is resolved in 8.2 btw.
Hi Rohit – the RoutingConfig EvaluateRepeaterRules - set to 'true'.
But as I asked , is there an option to copy blpackage that already on the remote-site to other agent on the remote-site –> directly.
This is what the repeater functionality does – it deploys to the repeater, then directly from the repeater to the remote target. is that not what you are trying to do ?
Hi Bill, NO. it's not what we trying to do, because the package already there in the remote-site, is there any options to deploy the package directly from the remote-site to remote-targets?
For Depot Software objects and not BlPackages, there is a ‘network deploy’ option where the target will directly mount the source location and run the install from there – via smb/cifs or nfs.
Hi Bill, OK, So Is it possible to save a directory as a depot-software-object? and not BLPackage
1 of 1 people found this helpful
You do not save a directory as an object. you create a new depot software object, and when it asks for the source, you choose the option ‘agent mount’ and specify the nfs or smb url to the source.
On the install command I modify it to : copy ??SOURCE?? c:\Install\
The problem is if we don't have on the target path c:\install
Then the copy failed,
I try copy command or cp or dsync with parameters like –ArP (to create directories, and copy recursively)
But it failed
Thanks a lot,
the purpose of the repeaters is to make sure that you don't need to do this. If you deploy the package using the app server and have the stage indirect configured and the correct repeater rules, it will check to see whether the package is on the repeater and copy it from the repeater to the endpoint for installation.
As far as I can see this is your end objective.
If you really want to achieve the copy via an SMB share on the repeater, then you will need to ensure that the SMB drive is mounted on the target server and run a job on the target server to copy the files from the mounted SMB drive to a local drive.
in the depot software install box, you are working in DOS, so cp, dsync are not available unless nsh happens to be installed on the target. even then you will have permission issues.
you should use copy or xcopy and lookup the syntax of those commands to perform the copy in the way you want.
if c:\install does not exist on your target already, you need to make that directory in the install command of the depot software. You can run whatever you want in the ‘install command’ box, as long as those command are present on the target server.
Hi Bill / Paul,
Finally it's works for me with the command : Xcopy ??SOURCE?? C:\myfolder /I /E /C /Y
The strange thing was that this xcopy job copy (from the smb share) a directory with about 120 m"b from remote-site server, to remote-site targets - in four minutes!!!
And the deploy job (with BLpackage) that copy the same folder (again it's 120 m"b) via indirect repeater (rules been set) – took more than a hour…
Do you recommend to check again the work / configuration of the Repeater?