Infrastructure at your Service
As described in my last post related to Momentum 16, I was excited to see the session “What’s new in Documentum 7.3″. Do not worry, I could slept last night. But are my expectations fulfilled? So yesterday I wrote about PostgreSQL which will decrease the cost of the DB licensing and then your TCO. It seems that based on benchmarks, there is still some place for small improvements to have the same performance as…
This first day at Momentum 2016 Normally I should write the second one as we started yesterday with a partner session where we got some information. One of these news was that EMC had more than 400 partners a few years ago and today this has been reduced to less than 80 and dbi services is still one of them. For us it is a good news, I hope this is also one for our…
When you have an installation with one Content Server (CS) you do not take care where the job will be running. It’s always on your single CS. But how should you configure the jobs in case you have several CS? Which jobs have to be executed and which one not? Let’s see that in this post. When you have to run your jobs in a high availability installation you have to configure some files and objects….
What is the relation between dfc.date_format and dm_LogPurge? This is the question we had to answer as we hit an issue. An issue with the dm_LogPurge job. As usual once a repository has been created we are configuring several Documentum jobs for the housekeeping. One of them is the dm_LogPurge. It is configured to run once a day with a cutoff_days of 90 days. So all ran fine until we did another change. On request of…
Documentum story. What is behind this story? Normally I should write Documentum Platform story. Indeed dbi services is involved to build and manage a worldwide Documentum Platform. Our part covers all middleware components related to the infrastructure excepting the OS, DB and applications which are managed by other teams. So we installed and manage so far: – 30+ Documentum Servers, 45+ repositories – 25+ Fulltext Servers, 50+ IndexAgent – 15+ ADTS servers – 30+ WebLogic…
So Momentum is over, Philippe Schweitzer and I finished with a 4 hours hackaton session. For Philippe the subject was “Developing an EMC Documentum application with REST, AngularJS, Bootstrap, Node.js and Socket.io=” and I choosed “From the Ground Up – Developing an EMC InforArchive Solution”. But the main subject in this post is more to thank all people we met during these four enriching days, EMC people – who hold the sessions, who made demos…
In this post I would like to relay some advices around the upgrade to Documentum 7.2 I have got in the session from Patrick Walsh about “What’s New, what’s Next: EMC Documentum Platform”. With Documentum 7.2 the processes for the upgrade is more cleaner and there are less restrictions. For instance more upgrade scenarios are documented, that can help us to define the best upgrade path to use. There was also a slide which listed…
Second day in this amazing event. There are not only general and presentation sessions you can also participate on a so called “Hands-on Lab”. The subject was the “EMC Documentum Platform Performance Tuning”. So learning by doing is also a good opportunity you can use at Momentum to enhance your skills. The session covered the performance tuning using Fiddler for the HTTP requests, the DFC trace, sql traces and how to use the related execution…
The first day of my first EMC World conferences and specially the ones from Momentum wich covers the Enterprise Content Division (ECD) products/solutions/strategies aso. The start was great, being in Las Vegas where you have the feeling you are on another planet, I had the same feel during the General Session or the ECD Keynote; each time good explanations coupled with good shows. The information I have got was interresting and some questions came in…
We planned to do our full production upgrade in a weekend – and one part was the replacement of FAST by xPlore. As we had to index more than 10 millions objects, we had to find a solution where the full repository would be indexed by Monday morning. Since we used a clone of production to validate and test our upgrade process, functions, and performance, we decided to prepare the production fulltext servers by using…
