For the past 17 years that I have been working with Documentum, I always felt that there was not a venue to discuss design issues, enhancement requests, or just share FAQs. My vision of this blog is not to address development questions or provide product support, but rather I want to encourage the development community to share their ideas and solutions.
Great presentation! I was not able to attend your class as I had a pretty full agenda my self, but would have it I had known you were there! Keep up the great work… I have included your presentation on my http://d4d2.com Documentum 4 Dummies site.
Thanks Troy, I’m glad that you fealt my presentation was helpful. Let me know if you have any topics that I should cover as a follow-up presentation.
Based on your presentation i am just curious about your suggestion
” Disable ACS from Webtop if you don’t to plan to use it ”
Any reason why you would do that ?
Webtop’s default configuration is to check for ACS. If you dont have ACS installed on the content server, you get these these annoying error messages in Webtop.
Actually, the main reason that the error messages occur is that ACS is broken in SP4. If you are running Content Server 5.3 SP4, then ACS does not work without a bug fix. It is supposed to be fixed in SP5.
The primary, non-bug related, reason to disable it would be if the Content Server is behind a firewall. If this is the case, then you need to open a hole in the firewall our from the Content Server. Not always an option. For internal networks, ACS is a great thing. I’ve seen it increase performance even in environments where it wasn’t technically needed.
Oh, and ACS is installed as part of the Java Method Server in the 5.3 platform. It is on by default.
Pingback: Defining an Documentum Architect, An Open Letter « Word of Pie
Thanks Pie for the SP4 bug update. It never occurred to me that it was broken, since the project I was on never really used it.