I'm trying to submit jobs to Core in a JMF SubmitQueueEntry message. This works perfectly when the submitted JDF file resides on the FF Core server and is referenced in the JMF as URL="file:///<path/to/local/file.jdf>"
Doing it this way means I'll need to copy my generated JDF files onto the Freeflow Core server before submitting my JMF SubmitQueueEntry message which is not ideal, so I've been trying to submit the JMF with an absolute URL to the jdf file on the remote server. This is what I can't get to work.
When I submit URL="http://<host><remote/path/to/file.jdf>" the JMF service responds Cannot access referenced URL C:/<remote/path/to/file.jdf> and when I submit URL="http:///<host>/<remote/path/to/file.jdf>" (note the three slashes), the JMF service responds Unable to access file \<host>\<remote\path\to\file.jdf>
So I have two questions:
1. Does Freeflow Core support downloading referenced JDF files from a remote server (it should if it follows the official spec for JMF)
2. How the hell do I need to format the URL in order to make it download the JDF file?!?
Also on a somewhat related note, can I use https as well as plain http?
Solved! Go to Solution.
Anyone? Would be great to know from one of the devs if it's even a possibility, because if its not I can at least make the decision not to re-visit this issue and stick to the less-than-ideal solution of FTPing my JDF file ahead of time...
I know the PDF file URL can point to HTTP within the JDF, and after some testing you can actually use a HTTP link to a JDF as well within JMF. The link is in normal URL="http://server/path/file.jdf". However you need to make sure you have followed the optional installation procedures (chapter 3 in the install guide) so that services have correct acces to the files.
However, instead of using the URL have you tried sending the JDF as MIME within the JMF? Core supports base64 and this seems to work well.
I've had a crack at sending a MIME package before actually and it's causing Core to throw an exception. I don't suppose you'd mind having a quick look at my file if I PM it to you would you? Its just base64 encoded xml and I can't see any issues with it myself, but maybe you'll spot something...
I tried setting the logon account on the services just now as you suggested as well, but the Freeflow Core web interface reported a fatal error no matter which user account I tried, so that might be a no-go too...
I've done some fiddling about and am now hosting my JDF files elsewhere, and they're being submitted over http like a charm! The main server uses https for all endpoints except where the JDF files are served from, but for some reason this configuration was causing issues. Moving just the JDF files to another host and disabling SSL across the board now works.
Worth noting that it definitely does NOT work over SSL for us. Might just be something for people to avoid...
Thanks for your help