Folks
Currently, our application running on a Unix machine will generate XML file into a Unix Folder
The Unix Folder is ‘exposed’ to our Window 2000 Server (running webMethods I.S.) via Simba
Our webMethods Integration Server (running on Windows 2000 Server) is
running as a Window Services using an LAN id/password not authorized to access the Unix Folder directly.
What I have done
- Map the Unix Folder via Window Exploer (using another user id / password)
- Create a Window Command File that move all the XML files from
the Unix Folder to local folder (e.g. move *.xml from folder A to
folder B) - In my webMethods flow services, I will use a java service (which
run RunTime.exec(commandFile) to invoke the command file to move the
XML files to a local folder, then list all the files in the local
folder, process each XML, convert to EDI (X12 4010 204), post to TN,
then use webMethods Primary FTP delivery service to FTP to trading
partner
Issues:
- If I use Process.waitFor(commandFile) to wait for the move to complete, webMethods just hang there and not moving any files
- If I do not use Process.waitFor(), each call the command file just move the 1st couples (actually 5) XML, which the command file should
move every XML files (over 30+) - When I use the Primary FTP Delivery Service, webMethods uses the task id as the filename.edi. Anyways that I can do to change it.
Please advise
Thanks a lot
Stephen Chung