Going to start categorizing my Tips/Documentum advice into a separate group. I want these things easier to find. Their relevance doesn’t really fade, so hopefully this will help keep them around.
I just helped someone install Content Server. I sometimes don’t even think about many of the details of an installation. I’ve installed it so many times that I just do it by instinct. I decided to put down some tips into this to help those starting the process.
This is the simplest of oversights. When you are trying to determine what platforms are supported for a particular release, say 5.3 sp5, you have to check six different release notes. That is correct, SIX. This is because any platform supported for one release of 5.3 is supported for ALL platforms, unless stated otherwise. Each set of release notes lists only the additional platforms that the new service was certified against, but all previous certifications on the version still hold.
What does this mean? Simple, if you want to see if the 5.3sp5 version of Content Server is supported on Oracle 220.127.116.11 on Windows 2003 sp1, you have to look in the 5.3 sp2 release notes. Ugh! What are the odds that you check those release notes first?
Expect this to continue for D6. While they have, in the past, posted a complete list of supported versions on their support site, it was never regarded as the definitive list. In fact, looking anywhere else other than their release notes can lead you into trouble. I would love for this to change one day.
Precreate your SQL Server Database
When using SQL Server, always try and create your database in advance. This gives you a few advantages. One of which is to provide a better check of your database connectivity before beginning the installation procedure.
Another advantage is that you can install SQL Server with its default sort order and specifically assign the Case Sensitive sort order to the Documentum database. This allows you to install both eRoom and Content Server on the same database server.
The recommended steps for doing this are:
- Create a new SQL Server account to own the repository. Make the account a System Administrator.
- Connect to SQL Server as the new account and create the database.
- Create your ODBC connection on your new Content Server. Do NOT put a space in the ODBC connection name. Microsoft may accept it, but not Documentum. Be sure to test the connection using the account that was used to create the database.
From here it should be clear sailing, as long as you have already installed the proper SQL Server database client on your Content Server.
Pick the Correct Sort Order
The default sort order for SQL Server is SQL_Latin1_General_CP1_CI_AS. The CI represents the Case Insensitive. So, when it is time to pick your sort order, just toggle the case. This will give you SQL_Latin1_General_CP1_CS_AS. Good money says that is the only sort order that EMC tests against. This means that it should be the only sort order you use without a defined business reason.
In SQL Server 2000, you have to set the sort order upon database creation. In SQL Server 2005, you can change the order after creation if you forget to do so ahead of time.
If anyone else has any other tips, or contrary experience, please share them with everyone here.