media objects, FTP and annoying names

Getting the e1 web client to use FTP for media objects is fairly easy, unless you think about it too much.  Or perhaps if you read the doco too carefully.  I’m going to help you out here.

I was getting the following in my logs after setting things up correctly (what I thought was correctly)

14 Mar 2013 15:55:13,738[SEVERE][JDE][BASE]FTPConnection: Unexpected reply 550 The system cannot find the path specified. 
14 Mar 2013 15:55:13,739[SEVERE][JDE][JAS]JDEOWDirect.saveFileFTP(): Invalid FTPConnection exeption is caught Host Name: jdedep2, User Name : anonymous, File path : /E910/MEDIAOBJ/HTMLUpload/FILE-192-168-204-120-43584667690065015-1363236908592.txt
14 Mar 2013 15:55:13,740[SEVERE][JDE][JAS]Exception occured in the JDEOWDirect.mediaObjectSaveFile(): , Source File Name :/u01/app/oracle/Oracle/Middleware/user_projects/domains/mydomain/servers/JDE91DV/stage/JDE91DV/app/webclient.war/moqueue\jdedep2\E910\MEDIAOBJ\HTMLUpload\FILE-192-168-204-120-43584667690065015-1363236908592.txt, Target File Name :\\jdedep2\E910\MEDIAOBJ\HTMLUpload\FILE-192-168-204-120-43584667690065015-1363236908592.txt java.io.IOException: FTP connection failed
14 Mar 2013 15:55:13,740[WARN][JDE][RUNTIME]FTP File upload to the server failed. Please contact your administrator.\nUpload the selected file: [BHP_PBS_ConversionScripts.txt]  \nUploaded file name: [//jdedep2/E910/MEDIAOBJ/HTMLUpload/FILE-192-168-204-120-43584667690065015-1363236908592.txt]

 

when you create the ftp site for your media objects, it does not point to the E910 dir like the doco suggests, it’s the base install dir, as below:

Note also that now the new installs use a dir like E910_1, this is a pain.  The share that is created by the install process is called E910, not E910_1.  Therefore you cannot share media objects between fat and thin unless you create another share called E910_1.

So, your P98MOQUE needs to look like:

See how I needed to change E910 to E910_1, this is because the automated FTP is a bit slow, and essentially executes a “cd” command which needs to goto a dir name, not a share name.

So, with anonymous access for ftp set up on my deployment server and the above two basic configurations – media objects are working like a peach.

Remember that we at Myriad have a solution which injects sharepoint into the iframe that holds media objects – No more dumb media object storage – we are using version controlled sharepoint.