Copy file from one folder to another with WorkFlow

Hi guys,
I have a problem, that struggling already a coupe of days Smiley Sad

May be somebody knows solution?

One of the task in my workflow is to copy a created html file from 1 folder to another. I use XCOPY to do it. My script is like this:

my $copyFrom = "\\\\XXXX01\\default\\main\\Internet\\WORKAREA\\Home\\documents\\test.html";

my $copyTo = "\\\\XXXX02\\dfsroot\\Shared\\CopyDocs\\";
my $cmd = "XCOPY $copyFrom $copyTo /Y/S/I";
system($cmd);

This script work fine in cmd and separate perl file, but when I put it in wfXXX.ipl it does not copy files at all.

Thanks in advance for your help.
Alla

Find more posts tagged with

Comments

Migrateduser

I suggest that you use "iwcp" instead of xcopy. There may be some extended attributes on that file that you want to preserve and iwcp does that.

I'm surprised to learn that including \\\\XXXX01 as part of the path on the command line actually causes it to run successfully but you may want to remove that part of the path. Then, of course, you'll need to worry about getting iwmount, but

TeamSite::Config::iwgetmount();

will do that for you. Also, whenever you execute a system command, you should try to catch any errors in your script ($! is the operator for this) and have an "else" condition if the command does not execute successfully:

system($cmd) || die "Whoops: " . $! ;

Dave

Valentine

Surprisingly the iwcp is not in the clt manual.

You can also try using iwupdate,
iwupdate $src $dest

Alla

I suggest that you use "iwcp" instead of xcopy. There may be some extended attributes on that file that you want to preserve and iwcp does that.

Thanks, Dave, for your reply. Will try this

I'm surprised to learn that including \\\\XXXX01 as part of the path on the command line actually causes it to run successfully but you may want to remove that part of the path.

Yes it works. Actually, it does not matter for me how to specify disk. I tried different ways to do it. And all variants work fine in cmd and perl but does not work in wfXXX.ipl.

Migrateduser

Surprisingly the iwcp is not in the clt manual.

Wow, you're right! I had no idea that such a basic and common command is not even documented! I think I gave a certain team of documentation people too much credit.

Well, here's the usage in all of its undocumented glory:

[HTML]
Usage: iwcp [-h] [-v] [-r] src dst
-h displays this usage information.
-v displays this command's version number.
-r copy directories recursively.
-r copy directories recursively.
-s preserve symlinks while copying.
[/HTML]

Hey, Interwoven -- this is a documentation bug! If I went through the trouble of writing a command, I'd sure want to tell people about it.

Dave

Migrateduser

It looks like you are trying to copy a file across the network to another server.

The reason it's not working is that your TeamSite installation is running under the system account which cannot access network locations ever. The reason it works from the command line is that you are running it as the user you are logged into the server as (which is not system).

I have a feeling you want to have the html file sent to another server for display purposes.

There are three ways of doing this.

Setup IIS on your other server and use the teamsite proxy server (Chapter 8 in the 6.5 admin guide) to view content by clicking on the html file in TeamSite. Multiple workareas will be able to view their modified content without affecting anyone else (recommended)

Setup IIS on your other server and create a virtual directory to the Teamsite shared directory of \\servername\default\xxxxxx location and directly view content through it's the external webserver.

Create a new directory on your teamsite server (ie c:\web). Copy your files from the Y: drive to this web folder with your workflow. Then create a new virtual directory on your external web server that points to the new \\servername\web directory on the teamsite server. You can then view content directly, but there are drawbacks if you have multiple workareas that are overwriting the files.

Alla

Thanks, guys,

Taalgaard, that is exactly what I need. Not sure that iwcp will work in this situation. Unfortunately, I can not install IIS on the target server Smiley Sad

If there is no another solution, I'll create Scheduled Task on the source server to run my copy job periodically...

Migrateduser

Make sure you scheduled task is running under a username and not system, or you'll run into the same issue.

Also, I have one more possible solution. If you have OpenDeploy you can do add a step in your workflow that calls a filelist based deployment to deploy the file(s) over during your workflow. Basically, during your workflow, step through the file(s) and add them to a txt file, then point OpenDeploy to the location of the txt file.

rodigz

Wow, you're right! I had no idea that such a basic and common command is not even documented! I think I gave a certain team of documentation people too much credit.

Well, here's the usage in all of its undocumented glory:

[HTML]
Usage: iwcp [-h] [-v] [-r] src dst
-h displays this usage information.
-v displays this command's version number.
-r copy directories recursively.
-r copy directories recursively.
-s preserve symlinks while copying.
[/HTML]

Hey, Interwoven -- this is a documentation bug! If I went through the trouble of writing a command, I'd sure want to tell people about it.

Dave

What if the directories of the source does not exist in destination?
Need to create first then copy? Is that correct?

Migrateduser

Correct, although before going through that trouble, you might want to play with this command a bit. Using the -r option might just create the directory structure for you if it doesn't already exist in the target path. With a typical Unix "cp" command, the -R option accomplishes this. If "iwcp" doesn't do this, then you will have to check for the directory structure before copying the file.

Dave

rodigz

thanks. cp -R and cp -r does not work; file or directory does not exist.

nipper

thanks. cp -R and cp -r does not work; file or directory does not exist.

Are you on Unix or DOS ? The command cp is a Unix command. Dump the command you are trying to use to a log file and double check it.