Difference between revisions of "Attachments Library"
m |
m (→See Also) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 25: | Line 25: | ||
== See Also == | == See Also == | ||
| − | [[Configure Java Client to Use Web Client for Uploading Attachments]] | + | [[Configure Java Client to Use Web Client for Uploading Attachments]]<br> |
| + | [[Unable to View pdf Attachments]] | ||
Latest revision as of 16:44, 1 September 2008
To discuss or ask questions about this article, select the discussion tab above.
Overview
On a fresh install of r11, the attachment repositories of Knowledge and Service Desk are already configured and operational. Additional work is required when performing a migration.
Facts
The attachment functionality uses Tomcat exclusively.
The attachment functionality resides on the Primary Server exclusively, even though the Repositories can exist anywhere.
Knowledge Tools and Service Desk utilize the same attachment mechanism, but have their own distinct requirements. In particular, every Knowledge Repository must contain a folder, while the Service Desk Repository does not.
Tips
Ensure your default Tomcat port (usually 8080) has firewall access for users outside of the firewall. Just because they have Service Desk access, which is usually the default port 80 used by IIS and Apache, do not assume they have access to attachments.
If directing users outside the firewall to a Secondary Server, ensure they have access to the Primary Server tomcat port or Add a repository deamon to your secondary server using pdm_edit and change your repositories to point to the secondary server (recommanded solution for external users as no additional port need to be open on the firewall). Note that the physical folders for the repositories need to located on the secondary server too.
See Also
Configure Java Client to Use Web Client for Uploading Attachments
Unable to View pdf Attachments
