Difference between revisions of "Attachments Library"
m |
m |
||
| Line 29: | Line 29: | ||
[[Configure Java Client to Use Web Client for Uploading Attachments]] | [[Configure Java Client to Use Web Client for Uploading Attachments]] | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ---- | ||
| + | <div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br> | ||
| + | To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div> | ||
Revision as of 15:28, 18 July 2008
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.
See Also
Configure Java Client to Use Web Client for Uploading Attachments
To discuss or ask questions about this article, select the discussion tab above.
