How to upload files with size greater than 100MB RTC without changing default clm admin settings
Hi,
Could any of you help me with a solution to the below problem we have please.
We need to know how to upload files with size greater than 100MB in RTC without changing any default clm admin settings
We do not wish to make any changes in the settings because its a shared server and there are many projects using the server and its just one project that is complaining this. We therefore will be interested in a workaround rather than making any changes from the server side.
Thanks
Venkatesh Prasad
Could any of you help me with a solution to the below problem we have please.
We need to know how to upload files with size greater than 100MB in RTC without changing any default clm admin settings
We do not wish to make any changes in the settings because its a shared server and there are many projects using the server and its just one project that is complaining this. We therefore will be interested in a workaround rather than making any changes from the server side.
Thanks
Venkatesh Prasad
2 answers
You cannot get around the limit.. if you need to upload more data, then all you can do is create multiple attachments, each with some part of the data, then the user must combine again.
in one of my prototypes for a prior company, I modified the product code to support links to files in a shared file system as the attachment, rather than holding the file itself. so the file size limit would not have been an issue. I set a second limit in config (CCM Web system Admin console same place normal size is configured) on automatically using links if over 1 meg, We had files files in the many gigabyte size, that I didn't want stored in the database to begin with. also we had an obligation to document that we destroyed the data no longer than 90 days after closing the ticket. (customer support). and this was prior to attachment delete support
due to browser anti-hacking security, file uploads don't come in with the ACTUAL filename, but a fake one, so I couldn't tell if the file was on the shared filesystem.. that made the darned thing not work completely.
as the RTC product is going to more and more browser based function, this limitation was seen as a real usability problem. I no longer work for the prior company
I had opened enhancement request https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=153049
wow, almost 5 yrs ago now.. last update almost 2 yrs ago
in one of my prototypes for a prior company, I modified the product code to support links to files in a shared file system as the attachment, rather than holding the file itself. so the file size limit would not have been an issue. I set a second limit in config (CCM Web system Admin console same place normal size is configured) on automatically using links if over 1 meg, We had files files in the many gigabyte size, that I didn't want stored in the database to begin with. also we had an obligation to document that we destroyed the data no longer than 90 days after closing the ticket. (customer support). and this was prior to attachment delete support
due to browser anti-hacking security, file uploads don't come in with the ACTUAL filename, but a fake one, so I couldn't tell if the file was on the shared filesystem.. that made the darned thing not work completely.
as the RTC product is going to more and more browser based function, this limitation was seen as a real usability problem. I no longer work for the prior company
I had opened enhancement request https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=153049
wow, almost 5 yrs ago now.. last update almost 2 yrs ago
Comments
Venkatesh Prasad
Jan 29 '16, 6:36 a.m.Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 29 '16, 5:23 p.m.Venkatesh Prasad
Jan 31 '16, 6:33 p.m.