LPA Data Iterator not finding file

 5 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
LisaN
Veteran Member
Posts: 53
Veteran Member
    We have a flow that updates PA15 for Flu information. The file is placed on the Lawson LSF server under /opt/lawson/law/productline/work/foldername. It isn't on the Landmark server.
    The first node in the process is a 'File Access' node, it checks if the file exists. The return msg shows it exists.
    If the file exists it goes to a Data Iterator node that parses the file by line. The return msg for this node shows the file doesn't exist.

    the input method = File
    the input file name = /foldername/filename
    Parse by: = Line
    Ignore trailing delimiter is checked

    Under the 'main' configuration we have the 'File Access' config tab setup, the 'Sys Comand' tab setup, and the 'File Transfer' tab setup (this flow doesn't transfer any files).

    How do I get the Data iterator node to read the LSF server and the file?

    Thanks,
    Lisa
    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
      A work around might be to read from file (read the file) with your File Access and then use the Data Interator to parse the data instead of trying to parse the file.
      David Williams
      Woozy
      Veteran Member
      Posts: 709
      Veteran Member
        Yep, David's option is probably the best one.

        I'm guessing that you have your FileIterator pointing to the configuration that references the LSF server, but the DataIterator doesn't have that option. There are a couple of other possibilities, but they are more complicated and not really any better.
        Kelly Meade
        J. R. Simplot Company
        Boise, ID
        LisaN
        Veteran Member
        Posts: 53
        Veteran Member
          Case closed thanks to David.
          We had to add a new 'File Access' node using 'Read from file', and then updated the data iterator's input method to 'Data' and changed the input data to the outputData variable of the new 'File Access' node.
          The process is now reading the file on the LSF server, adding records to PA15 as needed, sending the email, renaming the file on the LSF server and then deleting the file.
          We also testig using the 'File Transfer' node but David's suggestion was easier.
          mthedford
          Basic Member
          Posts: 8
          Basic Member
            I'm coming across this issue as well. I did notice from my IPA training class, all references to file paths in the data iterator used the admin shares, such as C$, L$, etc. I changed mine to those and it works, BUT, what user is it accessing this share using this method, since it is not utilizing the connection information? This is a security concern. I will probably convert over to using the Read from File method so the flow design will not spart any security concerns from others eyes, but this seems to be a hole in the process.
            mikeP
            Veteran Member
            Posts: 151
            Veteran Member

              I know this thread is pretty old, but I came across this issue today, and thought I'd throw out this solution.  Initially I set up a File Access node to read a file and pass it's data to a Data Iterator.  Then I started playing around.

              We're an AMS customer, and they long ago created a share on our LSF server called LAWDIR, that's rooted at d:\lawdev\law

              I created a property in the IPA System configuration set called

              LSF_LAWDIR with a value of 

              \\lltdev.lsf.server.com\LAWDIR

               

              It can be accessed it as a variable in a process to feed a file into a Data Iterator:

              You'll need to replace the parens with GT/LT signs. The forum software did funny things when I left them as GT/LT.

               

              (!_configuration.system.LSF_LAWDIR)

               

              I tested it the node types I've worked with so far that need to access files on the LSF server: File Transfer, File Access, and Data Iterator, and it seems to work in all three.  Here's a reference to a CSV file that's read by a Data Iterator:

              (!_configuration.system.LSF_LAWDIR)\Folder\Subfolder\DataFile.txt