Automic Workload Automation

Expand all | Collapse all

New type of file transfer requirement

  • 1.  New type of file transfer requirement

    Posted 4 days ago
    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


  • 2.  RE: New type of file transfer requirement

    Posted 4 days ago
    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
    ------------------------------



  • 3.  RE: New type of file transfer requirement

    Posted 3 days ago
    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.


  • 4.  RE: New type of file transfer requirement

    Posted 3 days ago
    We do file transfer between unix and windows as well very successfully.
    Another small hint that hopefully avoids some struggle for you: use file format "binary" by default. Then the files will be transferred as they are. With file format "text" line feeds will be translated between the operating systems and that corrupts files that have binary formats like .pdf.

    ------------------------------
    Regards, Nicole
    ------------------------------



  • 5.  RE: New type of file transfer requirement

    Posted 2 days ago
    Thanks for the insight.  I am a little confused when you speak of Agent to Agent versus FTP-Agent.  What I have found out since is that the drive that contains the files that I need to transfer from is their master storage array.  I am being told that a VM will be set up to connect to the array and that Automic will just connect to the VM.

    That being said, middleware will be setting up a FTP agent on the VM so Automic can connect.  Are you saying that it only needs an OS agent and not a FTP Agent installed? Or, are you saying the FTP-Agent is the RA File transfer agent that you are not using and are using the JobF file transfer object.

    My experience has been transferring using a Linux file server with NFS mounts.  None of our file transfers have ever been from a Windows host so I am a novice in once sense and seasoned in another sense.

    BTW, still very new here in this forum so I am struggling with my default signature.  Not looking for help, just advising that it may be a bit wonky until I get it set up correctly.


  • 6.  RE: New type of file transfer requirement

    Posted 2 days ago
    You can use the RA FTP Agent to connect to the ftp server on the vm that get´s access to the source filesystems. But that´s not the RA FTP Agent, because the agent connects to a ftp server. It isn´t a ftp server. You have to install the RA FTP Agent on the destination machine to transfer the files via ftp protocol.

    Or you let install an automic os agent on the source vm (with access to the file systems of course) and install another os agent on the destination server (with access to the destination file system ;-) and use uc4 filetransfer jobs to transfer the files. In UC4 it doesn´t belong, which os is used on the source and/or destination. All combinations from windows, linux, unix (e.g. solaris) work together. With textfile transfers you should be aware to set the binary format as mentioned from Nicole before.

    In my experience i would prefer the os agent variant with uc4 filetransfer protocol. , but i assume, that both solutions would work.

    We use two windows vm´s (two for fail over, but we using almost one at all) with one windows os agent installed on each vm. And aproximately 98% of our filetransfers with a windows file share on source and/or destination goes over this agent.
    Just give it the needed firewall rules and give the uc4 os user the needed windows ad rights for the windows directories and this is easy ;-)

    ------------------------------
    Administrator and Developer Jobautomation
    BNP Paribas S.A. Niederlassung Deutschland
    ------------------------------