If you access a locally mounted drive on a windows (nt) host that is mapped to a drive-letter like d: then you have to use this letter in the JOBF-path on tha agent of this machine, too.
You enter the path as you would with a "dir"-command on the cmd on that host.
If you want to access a directoy on a smb-file server then you have to use \\servername\share\directory1\directory2\... . The path fields on the JOBF are just text fields there you can enter whatever path you want. And the corresponding os-agent will interpret this text as a path/filename-combination as it see´s it with the user rights mentionend in the login object.
Copy files from server win01 with directory c:\temp\testfile.txt to server linux02 with directory /tmp/testfile.txt you should enter this in the JOBF-fields:
Source-Part (upper window):
--------------------------------------
Login: login object with a windows user that has access to the local directory and read (and maybe delete) the file
File: c:\temp\testfile.txt
Destination-Part (lower window):
-------------------------------------------
Login: login object with a linux-user with access rights to write the file
File. /tmp/testfile.txt
Quick test: If you can see the file with a dir-command (on the windows host), you can access it with the same user and path on a JOBF ;-)
Sometimes it´s required to test the dir-command with a JOBS if your organisation uses fileaccess-rights on a windows (smb) share.
Best regards,
Toni
------------------------------
Administrator and Developer Jobautomation
BNP Paribas S.A. Niederlassung Deutschland
------------------------------
Original Message:
Sent: 09-18-2019 09:38 AM
From: Chismar
Subject: New type of file transfer requirement
Richard,
Thanks for the input. I actually found a NT server that I am mapped to as part of my other duties and noticed an Automic agent had been installed there for some time. I attempted to access and was able to log on but was unable to get to the folder\files for my test.
You mention it should be \\hostnames\sharename\directory\file. I do not think I have a share name. My guess is that share name = drive name (i.e., c:\ d:\, etc.)? Is this correct? And if so, where, in Automic, would you set that? Looking over the JobF object, I do not see where I can set that. I you could attach or reply with a specific working example, that would be very helpful. The Automic documentation does not go into the depth needed for someone doing this for the first time.
Thanks again,
------------------------------
Cheers,
Gary Chismar
Manager, Automic, PeopleSoft HCM/FI
Florida State University
Florida
Original Message:
Sent: 08-14-2019 10:05 AM
From: Beck
Subject: New type of file transfer requirement
Adding to the above reply. I've done the same. The agent to agent transfer is fairly robust.
I also agree that I like the agent to agent transfer rather than dealing with connection/permission/ownership hassles of NFS over a WAN connection to a multiprotocol share.
I also want to add that just because you mentioned you are picking up from 18 locations with windows shares. This doesn't mean you need a n agent on each server. You can make this work by connecting to a single windows box an using the smb \\hostnames\sharename\director...\file type path to access the shares from the single windows host.
Original Message:
Sent: 08-14-2019 04:14 AM
From: Toni Waechter
Subject: New type of file transfer requirement
Hi Gary,
we don´t use the FTP-Agent, but we use the normal filetransfer from agent to agent (windows <> unix) successfully and very often.
Another way to transfer files from a mountable (samba?!) network-share will be to mount the same network-shares on the linux-server and make a local copy from on directory (eg windows-share) to another (linux-share). But i would prefer the agent to agent solution.
Best regards,
Toni
------------------------------
Administrator and Developer Jobautomation
BNP Paribas S.A. Niederlassung Deutschland
Original Message:
Sent: 08-13-2019 11:15 PM
From: Chismar
Subject: New type of file transfer requirement
Hello All,
We are on Automic V11.2, upgrading to 12.3 in a few months. That aside, I have been asked to have Automic monitor and transfer files from a Windows server (its called Samba here) to a third party. I plan on transferring the files to our Linux file server first so they can all be zipped up. The files on the Windows server are in about 18 different locations.
I have never tried to transfer files from Windows to Linux so this is very new for me. I am experimenting using the delivered Automic FTP object now.
What I am looking for is for people who have successfully set this up in the past and can share insights as to what must be done.
I have requested our middleware team to set up an agent on the server but they want me to first test this out on an existing Windows server where an agent is already installed.
I feel blind as a bat as the FTP object does not allow you to see any of the directory structure as the RA FTP object does.
Any helpful information will be greatly appreciated. I went to file a case with Broadcom/CA but the site is down for maintenance. I have until mid September to complete the task and I feel once I get over this hurdle then the rest will fall into place.
Thank you all in advance for your help.
Cheers,
Gary Chismar