Attachments Library - Revision history

Gityerfix: /* See Also */

2008-09-01T16:44:53Z

‎See Also

Gityerfix at 16:44, 1 September 2008

2008-09-01T16:44:41Z

Gityerfix at 03:19, 27 July 2008

2008-07-27T03:19:32Z

Gityerfix at 06:31, 26 July 2008

2008-07-26T06:31:11Z

Zjz: /* Tips */

2008-07-18T15:52:40Z

‎Tips

Gityerfix at 15:28, 18 July 2008

2008-07-18T15:28:31Z

Gityerfix at 13:04, 5 July 2008

2008-07-05T13:04:30Z

Gityerfix at 16:29, 7 March 2008

2008-03-07T16:29:02Z

Gityerfix at 16:15, 7 March 2008

2008-03-07T16:15:07Z

Gityerfix: New page: 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. == ...

2008-03-07T16:05:25Z

New page: 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. == ...

New page

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.

Knowledge Tools and Service Desk utilize the same attachments mechanism, but have their own distinct requirements. In particular, ever Knowledge Repository must contain a folder, while the Service Desk Repository does not. [[Image:r11_default_repositories.jpg|thumb|r11 Default Repositories Screenshot]]

== Tips ==

Ensure your default Tomcat port (usually 8080) has firewall access of users outside of the firewall. Just because they have Service Desk access, which is usually the default port 80 used by IIS and Apache in most default installs, do not assume they have access to attachments.

@@ Line 25: / Line 25: @@
 == 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]]

← Older revision		Revision as of 16:44, 1 September 2008
Line 26:		Line 26:
	== See Also ==		== See Also ==
	[[Configure Java Client to Use Web Client for Uploading Attachments]]		[[Configure Java Client to Use Web Client for Uploading Attachments]]
		+	[[Unable to View pdf Attachments]]

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Configuration]]
-<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+{{Global Header}}
-To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
+{{Global Announcement}}
 == Overview ==

@@ Line 1: / Line 1: @@
 [[Category:Configuration]]
 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 ==
@@ Line 7: / Line 11: @@
 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
@@ Line 28: / Line 25: @@
 == See Also ==
 [[Configure Java Client to Use Web Client for Uploading Attachments]]

@@ Line 22: / Line 22: @@
-If directing users outside the firewall to a Secondary Server, ensure they have access to the Primary Server tomcat port.
+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).
 == See Also ==

← Older revision		Revision as of 15:28, 18 July 2008
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>

← Older revision		Revision as of 13:04, 5 July 2008
Line 1:		Line 1:
		+	[[Category:Configuration]]
	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.		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.

Line 24:		Line 25:


−	The Java Client (aka Admin Client, FAT Client) can be configured to utilize the web client for uploading attachments. This can be a good workaround for issues with uploading attachments via the Java Client. When this modification is implemented, a web generated pop-up will appear in place of the java client window. The integration is seamless. [[Configure Java Client to Use Web Client for Uploading Attachments]]	+
		+	== See Also ==
		+
		+	[[Configure Java Client to Use Web Client for Uploading Attachments]]