Please remember there is a security aspect to this posting!
1 Extract the zip file and upload the jar to /opt/infra/inframgr
2 Edit run.sh and update the class path with the jar name ‘fileupload.jar’
[root@CUCSD_Primary inframgr]# cat run.sh
3 Restart UCSD
4 Execute the custom-workflow ‘RegisterFileUploadInputType’.
It will register the new input type ‘file upload’. Use this type file uploading.
5 Execute the workflow ‘execute file upload’.
For UCSD 6.0 please place the fileupload.jad file into /opt/infra/inframgr/.
Then rename the file to:
mv fileupload.jar patch-fileupload.jar
Restart UCSD application (shelladmin option 3 and 4)
Run the register workflow. (there is now a check box to have the workflow execute on UCSD startup)
all patch-<filename>.jar files are picked up automatically by inframgr.
In a mulit-node environment, does the .jar file need to be added to run.sh on the service nodes as well?
No just the primary engine since the GUI is on that and this is a GUI jar file.
I've followed the procedure explained above but i'm not getting the Browse button when i execute the fileuploadtask.
I'm using UCSD6.
I've placed the fileupload.jar in the correct path and tried to copy the file with root user which didn't work as well as changing ownership of the file to ucsdu ucsdg didn't help.
Thanks it worked!
A bug has been filed on this and should be resolved in the next patch.
For UCSD 184.108.40.206 build 60440 I tried the fileupload.jar file into /opt/infra/inframgr/
I edited runprod.sh and update the class path with the jar name ‘fileupload.jar’.
Run the register workflow. (there is now a check box to have the workflow execute on UCSD startup 'Always execute during System initialization')
But then none of my workflows would start. I had to revert to the original version of runprod.sh and delete patch-fileupload.jar to get working again.
FYI..this should be all that is needed
I am about to patch to 220.127.116.11 and make sure I ftp my file as binary and re-check.
We are having issues running the task "File Upload".
We are running UCS Director 18.104.22.168 build 55534.
We installed both FileUpload.wfdx and fileupload.jar according to the directions.
After "3. Restart UCSD" (We restarted the service and did not reboot the host), we do see the "RegisterFileUploadInputType" in the "Workflows" tab. However, we do not see the "execute file upload" in the "Workflows" tab or in the "Custom Workflow Inputs" tab or in the "Custom Workflow Tasks". I do see "FileUploadTask" in the "Workflows" tab and when I run this workflow I do not see a browse button.
This issue seems very similar to what "yshtoots" reported on Oct 3.
I'm wondering if I need to perform the same fix that was presented ... or if there is another way to resolve?
Dod you do step #2?
Edit run.sh and update the class path with the jar name ‘fileupload.jar’
Just as an FYI - UCSD 6.5 Beta is coming out either today or tomorrow and this is now standard in the product :-)
Thanks for the quick reply.
That's good news regarding this feature in 6.5!
Yes, I made the edit to run.sh for fileupload.jar.
I did not run "run.sh" after the edit ... I restarted the service : 3-stop + 4-start.
Should I have executed "run.sh" after editing?
stop and start is the right thing to do .
up to UCSD 6.0 the steps 1-5 worked. In UCSD 6 the jar files get read in automatically from the directory. In 22.214.171.124 and 126.96.36.199 the file up load was broken in the GUI.
Right now we are running UCS Director 188.8.131.52 build 55534.
Does this code work in 5.5?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: