i have done script to upload photos to public resources from JS activity within workflow. You can add list of files and loop below script
var file = new File("path_to_file\\mont.jpg");
logError ("File '" + file.fullName + "' does not exists.");
var extension = /[^.]+$/.exec(file.name);
var md5 = HMACStr(file.name,"UTF-8","MD5");
if (!file.copyTo("path_to_adobe\\Adobe Campaign v6\\var\\res\\bootcamp\\" + md5 + "." + extension))
logError ("File '" + file.fullName + "' was not copied");
var xmlString = '<fileRes alt="" codepage="0" height="0" name="owl.jpg" nature="" publish="0" storageType="5" useMd5AsFilename="1" userContentType="0" version="" width="0" xtkschema="xtk:fileRes"/>'
var fileRes = xtk.fileRes.create( new XML(xmlString));
fileRes.label = "some_label"
fileRes.md5 = md5;
fileRes.fileName = "path_to_adobe\\Adobe\\Adobe Campaign v6\\bin\\..\\var\\res\\bootcamp\\" + md5 + "." + extension;
fileRes.originalName = "path_to_file\\Downloads\\mont.jpg";
We inherited a system which included a workflow, build by an Adobe engineer, to import images from a shared folder on the Campaign server as xtk:fileRes. There's a fundamental problem with trying to do this within Campaign itself, that it's not possible (as far as I can see in the docs, and confirmed by someone from Adobe Support) to calculate the md5 hash of a file - and thus the xtk:fileRes record you end up with is not the same as that which would have been created by uploading the same image in the UI. We don't know what the consequences of this are, but it certainly has potential for things to break.
I ended up writing a .NET app through which images (along with their md5 hash!) can be uploaded to a custom SOAP endpoint, which then creates the xtk:fileRes records - see the github project. The treatment of folders could still do with a bit of work - it doesn't create folders, or change the folder if the image already exists in a different one. But it works for our purposes, and may work for yours; or at least give you some useful ideas.
Your solution will work if there is only one frontal server.
If there are two servers, wfserver process will only run on the first one.
So, if you save it to file resources, the record wil get updated in the database but the actual file will only be published on the first server.
The second server will not receive it.
In a load balanced scenario, if this image is used in email, it will render on occasion if the GET call is sent to the first server. WHen it goes to second HTTP 404 will occur.
Please correct me if my understanding is wrong.
yes thats good question you will need to publish images to all frontal servers as it would be done automatically when you are uploading resource via adobe. Thank you for pointing this out.
I think the one who wants this to be automated will figure it out somehow or I suppose it can be done differently at all.
When I am running this code I could see that the File object from which we are trying to create a File Resource, should be placed in a path in server("/usr/local/neolane/nl6/var/partners/"). I am unable to find any activity to copy/upload the file to server path. If this understanding is correct can you please mention any suggestion to upload a file/image from local drive to the server.