A few weeks ago, we finished a Documentum upgrade at a customer site. Now, after having analyzed and made a status point (we do that after each upgrade project to optimize our procedures and skills) it is time to share our experiences. In this post and in the ones that will follow we will describe which issues we were confronted with, which bugs we discovered, and how we proceed to go forward to have a running environment at the end – and of course, a satisfied and happy customer!<\/p>\n
We had to upgrade four environments; development, test, clone, and prod. We had to upgrade or do new installations for the following components: Content Server from 6.5SP3 to 6.7SP2, D2 3.0 to D2 3.1SP1, DTS 6.5SP3 to ADTS 6.7SP2, DA 6.5SP3 to DA6.7SP2, DFS6.7SP2, xPlore 1.4<\/p>\n
We first started with the Dev environment to define our processes. Then, we built a clone of the production repositories to validate the upgrade process, to do the test, and to validate the xPlore high availability installation. The xPlore HA has been covered with the installation of two xPlore instances on different physical servers, and the use of a DSearch URL configured in F5 (master-slave and not in load balancing mode) for the search. With all that, not only has the xPlore installation been validated, but the upgrade process could also be run faster as we had to index only a gap of objects on the day we did the production upgrade. But let’s wait for a future blog where this will be described.<\/p>\n
So first of all, I will summarize the issues\/bugs we had to deal with. The details will be published in the next blogs.<\/p>\n
On the content server side:
\n– We discovered a bug when we moved to the summer time; for instance a job that had to run at 4:00 AM started indeed at four o’clock but it also started every two minutes until 5 AM.
\n– D2EventSenderMailMethod does not work anymore since we installed the patch 12 for the Content Server 6.7SP2.<\/p>\n
On ADTS:
\n– Some ADTS processes randomly stopped working using a domain user as the installation owner.<\/p>\n
On DA:
\n– Documents could not be downloaded.<\/p>\n
On the D2-Client:
\n– Facets are configured in xPlore, but date attributes cannot be listed by date.
\n– We had some difficulties to implement the SSO based on NTLM. As we use D2 3.1SP1 which is in my point of view a 4.x version, we did not know exactly which documentation to use. Even the EMC support had to investigate to find some information.
\n– The ActiveX for D2 3.1SP1 could not be installed.
\n– SSO and D2DFS.
\n– Some icons where missing in D2-Client.<\/p>\n
So let’s see what will be posted in the next days\/weeks, which I hope will help people in their upgrade projects.<\/p>\n
The title of the related blogs will begin with “Documentum upgrade project”.<\/p>\n
Enjoy the reading!<\/p>\n","protected":false},"excerpt":{"rendered":"
A few weeks ago, we finished a Documentum upgrade at a customer site. Now, after having analyzed and made a status point (we do that after each upgrade project to optimize our procedures and skills) it is time to share our experiences. In this post and in the ones that will follow we will describe […]<\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[443,129,219],"type_dbi":[],"class_list":["post-3934","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","tag-d2","tag-documentum","tag-upgrade"],"acf":[],"yoast_head":"\n